Workflow instances problem

My problem is that in workflow i am sending workitem for manager approval.If manager rejects the workitem it goes to employee back for correction and resubmission.But what is happening once workitem is send to employee for correction the current workflow instance is completed and when user changes the report and resubmits it a new workflow instance will be created.This all increases load on the working system.
Can we keep the same workflow instance working till report is rejected or accepeted and then only workflow instance is completed.

I think you can make use of Function module
SAP_WAPI_WORKITEMS_TO_OBJECT
in a virtual attribute that will check whether any existing wflow is already triggered for it. If yes set the Flag(Virtual attribute) value as X. Make use of this attribute in th Start ciondition of the wflow in SWB_COND Tcode.
Now in your workflow the approval step should be inside a loop that loops until the request is approved. Inside the loop the approval step should be in fork with 2 parallel branch and 1 necessary. In 1 branch put approval step and in other branch put the Wait for event step.
Thanks
Arghadip

Similar Messages

  • Cannot create process to handle workflow instance conversation

    <Nov 18, 2002 1:04:30 PM IST> <Error> <B2B> <000000> <<Process>
    Hi,
    Iam getting following error when iam trying to invoke
    subworkflow.
    can anyone help me in solving this problem.
    regards
    Ananth
    ERROR: Cannot cr
    eate process null.>
    <Nov 18, 2002 1:04:30 PM IST> <Error> <B2B> <000000> <<B2B-BPM-Plugin> ERROR:
    Cannot create process to handle workflow instance conversation
    com.bea.b2b.protocol.ProcessManager$CreateException: ERROR: Cannot create proces
    s null.

    Hi Ajaz,
    Error description is not detailed enough to provide the solution. You need to post the error message what you got in the server log files. This should contain specific details about the issue.
    Not sure but issue may be related to JVM settings. if it is so, server log file will provide the error description.

  • Change Workflow-Instance-Container values

    Hi Experts,
    I would like to ask you how to change a value in a container of a Workflow-"Instance".
    For e.g.:
    I have a workflow-instance which contains a (bor-) Object "Switchdocument". This switchdocument contains also a (Bor-) Object "serviceprovider". And I would like to change the value of the parameter of "serviceprovider".
    How is the relationship between the "father"-object and the "child"-object and where are the relationship saved?
    I know the table "sww_cont" and "sww_contob". But these tables are not enough, aren't?
    Because in the mentioned tables (sww_cont) I see the elements with their values of the container of the workflow-instance. I don't the elements with their values of the object (father-object) contained in the workflow-instance-container and also not the elements with their values of the object (child-object) in the father-object.
    or (explanation as a list)
    Workflow-Instance-Container:
    1.element
    2.element
    3. Switchdocument (object)  (father-object)
    3.1 element of switchdocument
    3.2 .....
    3.3 Serviceprovider (object) (child-object)
    3.3.1 element of serviceprovider  <--- here I would like to change the value
    I hope I explained the situation in a detail way
    I apologize if I don't use the right terms!
    If anyone has a hint or a way to get to the "child-object" I would be very thankfull.
    Thanks a lot for your answers in advance!!!
    with lovely regards.

    Hi all,
    at first I thank you all for your answers!!!
    As I understand the values are permanently saved in the subobjects. Like I said the subobject (Distributor) with the attribute, e.g. Serviceprovider in Own System = 'X' is contained in the Object Switchdocument.
    That means for me that I have to retrieve the attribute of the subobject via a method for the special instance and change it, e.g. to set it blank.
    I have forgotten to say that I am developing a report (se38) to change all attributes of workflow-instances with object/subobject.
    As I said above in a condition step it is asked whether a "serviceprovider is in own system". if yes (means = "X") then the process has another way. And I have to change the "X" to "blank", so the workflow goes always the, in my case, second way.
    For the next time, I will explain my problem in a more detail way
    Thanks again.
    with kind regards!

  • Remove Workflow Instance From Queue

    Hi Experts,
    We encounter a problem in UCM workflow. Somehow the content of some workflow instances is no longer exists in the system (Don't know why), but the workflow instances are still active. This cause the cps portlet fails to render the approval portlet.
    We have tried login as the workflow instance owner in UCM Admin page (http://host:16200/cs), and go to My Content Server > My Workflow Assignments, remove the offending workflow instance manually.
    However we don't know how much workflow instances are affected, we would like to remove all offending workflow instances by a single administrative account i.e. "weblogic", but we found that we are not able to do this as the Content Items In Workflow "workflow_name" does not include the offending workflow.
    Is there any SQL update to the data in the OCS schema to batch remove the workflow instances?
    Ziho

    Hi Jiri,
    Thanks for the suggestions, below are some more information on the issue.
    if you can afford that, the easiest way how to get rid of running workflow instances is to disable an re-enable the criteria workflow(s) that contain it. Be aware that you will lose all workflow statuses of the disabled workflows.We can't afford that as it is a production system
    Workflows, however, store workflow statuses on filesystem, so I'm not sure if database operations will be enough.I think so, we tried login as workflow owner, there is a function to "Remove workflow from queue" for specified workflow instance under All Active Workflows --> My Workflow Assignments. However after the removal of the workflow instances, we can't find any data modification in the OCS schema, related tables include WORKFLOWDOCUMENTS, WORKFLOWDOCATTRIBUTES, DOCUMENTS, DOCMETA, REVISIONS and REVCLASSES
    by doing so, the admin should see the items - not in My Workflow Assignment, though. You will need to click the name of the wokflow and then, you should see all the items in the particular workflowYes, the admin i.e. "weblogic" can view all active workflow instances WITH content associated with it, but offending workflow instances (i.e. the one WITHOUT content somehow) do not show up.
    We believe, if no things go wrong, that all active workflow instances can be found by running the following sql statement "select * from WORKFLOWDOCUMENTS;". However, in our case, workflow instances without content can be found using the same sql, but do not show up in UCM web UI login as "weblogic".
    Last, but not least, you should analyse how come an item in a workflow could be deleted.We encountered this during high load (Generated by Stress Test Tool), without login UCM web UI as admin role to delete content.
    the admin deleted the item in Repository Manager whilst it routed in a workflow.We tried using admin role to delete content in Repository Manager, it popup error when we tried to delete content which are in active workflow. We had to either Approve or Reject it before we can delete it (which I think the workflow maybe not in active state anymore, i don't know..)
    See if any other suggestion I can get. Thanks for the input.
    Thanks,
    Ziho

  • Getting WLI  Workflow Instance getting NULL.

    Hi All WLI Users,
    I am getting following problem while executing WLI workflow. After work
    flow gets triggered by an XML event and instantiated, after some time workflow
    instance becomes null.
    and the execution is aborted. Kindly give me a solution to this problem.
    Thanks
    Kiran

    Hi tony
    It won't be possible for us to send us the workflow, beacuse it has
    lots of interfaces
    like MQ series and TCP/IP adpater.
    But I can explain u in brief the workflow.
    Workflow sends message to HOST1 after getting successfull response
    from HOST1 it sends
    another request to HOST2 and waits for the response.
    Now this can iterate for say 200-500 times (depends on response
    from HOST1).
    Each message length is aroung 5000 bytes.During this iteration the
    instance somehow sets to NULL.
    I hope you can simulate the same at your end.
    Also note we also do XML transformation before sending the request.
    Thanks
    "tony lodge" <[email protected]> wrote in message
    news:[email protected]...
    Hi
    I recommend given this level of detail you open a case, what I amseeing
    looks like a valid bug. Please provide the sample workflow if possible
    Tony
    "Saurabh" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    The Versio ni am using is wlisp2.1 (service pack 2.1)
    and Exception Stack trace is as follows,
    <Mar 30, 2002 1:53:55 AM GMT-05:00> <Error> <T3Services> <Workflowtrace:Template=28003
    Template Definition=31003
    Instance=null>
    Workflow warning: com.bea.wlpi.common.WorkflowException: The system
    could
    not
    find the specified workflow instance: null.
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
    nce(WorkflowProcessorBean.java:537)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
    nceData(WorkflowProcessorBean.java:551
    atcom.bea.wlpi.server.workflow.Variable.setValue(Variable.java:92)
    atcom.bea.wlpi.server.workflow.Workflow.setVariable(Workflow.java:833)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.setVariableValue
    (WorkflowProcessorBean.java:1017)
    at
    com.bea.wlaiplugin.server.WLAIServiceImpl.execute(WLAIServiceImpl.java:211)
    atcom.bea.wlpi.server.workflow.action.ActionPlugin.execute(ActionPlugin.java:1
    23)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
    at
    com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
    va:50)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
    orkflowProcessorBean.java:1194)
    at
    com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
    at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
    rs(WorkflowProcessorBean.java:1344)
    at com.bea.wlpi.server.workflow.Start.activate(Start.java:168)
    at
    com.bea.wlpi.server.workflow.Workflow.start(Workflow.java:657)
    atcom.bea.wlpi.server.workflow.Workflow.instantiate(Workflow.java:617)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Workflo
    wProcessorBean.java:713)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithError
    Handling(WorkflowProcessorBean.java:11
    32)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Work
    flowProcessorBean.java:709)
    at
    com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.in
    stantiate(WorkflowProcessorBean_h7kt4j
    _EOImpl.java:78)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(EventProcesso
    r.java:358)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
    a:244)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
    ean.java:130)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    <Mar 30, 2002 1:53:55 AM GMT-05:00> <Notice> <EJB> <Error markingtransaction
    for rollback: java.lang.IllegalStateException:
    Cannot mark the transaction for rollback. xid=4883:97fdb06e981bb8b8,status=Rolled
    back. [Reason=weblogic.transaction.interna
    l.TimedOutException: Transaction timed out after 89 seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    java.lang.IllegalStateException: Cannot mark the transaction for
    rollback.
    xid=4883:97fdb06e981bb8b8,
    status=Rolled back. [Re
    ason=weblogic.transaction.internal.TimedOutException: Transaction timedout after
    89 seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    at
    weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
    nsactionImpl.java:1486)
    at
    weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
    l.java:466)
    at
    weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
    ava:255)
    at
    weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
    5)
    at
    weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
    er.java:371)
    at
    weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
    java:756)
    at
    weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
    move(WorkflowProcessorBean_h7kt4j_EOIm
    pl.java:856)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
    cessor.java:510)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
    a:284)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
    ean.java:130)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    >
    javax.transaction.TransactionRolledbackException: EJB Exception: :weblogic.transaction.internal.TimedOutException:
    Transacti
    on timed out after 89 seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    at
    weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
    Impl.java:1122)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
    ansactions(ServerTransactionManagerImp
    l.java:441)
    at
    weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
    erImpl.java:1581)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
    sactionManagerImpl.java:404)
    at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
    rImpl.java:1547)
    at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 89seconds
    >
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out
    after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    at
    weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
    tionImpl.java:1475)
    at
    weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
    ServerTransactionImpl.java:435)
    at
    weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
    at
    weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
    0)
    at
    weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
    er.java:371)
    at
    weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
    java:756)
    at
    weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
    atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
    move(WorkflowProcessorBean_h7kt4j_EOIm
    pl.java:856)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
    cessor.java:510)
    at
    com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
    a:284)
    at
    com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
    ean.java:130)
    at
    weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
    atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
    at
    weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    ; nested exception is:
    weblogic.transaction.RollbackException: Transaction timed outafter 89
    seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out
    after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    weblogic.transaction.internal.TimedOutException: Transaction timed outafter 89
    seconds
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    at
    weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
    Impl.java:1122)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
    ansactions(ServerTransactionManagerImp
    l.java:441)
    at
    weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
    erImpl.java:1581)
    at
    weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
    sactionManagerImpl.java:404)
    at
    weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
    rImpl.java:1547)
    at java.lang.Thread.run(Thread.java:484)
    --------------- nested within: ------------------
    weblogic.transaction.RollbackException: Transaction timed out after 89seconds
    >
    Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
    sOwedOthers=0,seconds
    since begin=89,seconds left
    =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
    Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
    - with nested exception:
    [weblogic.transaction.internal.TimedOutException: Transaction timed out
    after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
    gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
    er]=(state=active),properties=({weblogic.jdbc=t3:
    >
    file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
    torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
    7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
    at
    weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
    tionImpl.java:1475)
    at
    weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
    ServerTransactionImpl.java:435)
    at
    weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
    at
    weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
    0)
    at
    weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
    er.java:371)
    at
    weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
    java:756)
    at
    weblo

  • OWB / Workflow integration problem

    We have a OWB 11g installation running on Windows 2003 64-bit Server.
    We have 2 OWB databases, one design repository and one runtime repository.
    Workflow is installed and configured on the runtime database.
    Oracle Workflow Location is set to the runtime repository, and checks out ok.
    OWF_MGR user is also created in the OWB Design Center, although Oracle documentation is very unclear on this; only stating that
    +"6. Create a Workflow Proxy User.+
    +When the Workflow instance is remote from the database hosting the Warehouse+
    +Builder repository, you need to create a proxy-user.+
    +Within the database hosting the repository, use SQL Plus to create a user and grant+
    +it the OWB_USER role as a default. This enables the remote OWF instance to+
    +connect to the services provided by the Control Center."+
    We're able to deploy Process Flows from the design repository to the runtime rep, but when we try to execute them through workflow, the warehouse builder browser reports the following 3 errors:
    R+PE-02075: Oracle Workflow failed to process the execution request for Activity LOAD_FP_INDEX:START1. This may be because dependent objects have not yet been deployed.+
    ORA-20002: Failed to call "PFFPVSL_WB_RTI_WORKFLOW_UTIL".initialize. Please check that "EXECUTE ANY PROCEDURE" privilege is set and that the OWB Runtime is available. ORA-20009: User OWF_MGR does not have access to the workspace with name:OWBRTREP and owner:OWBRTREP. OWF_MGR must be registered to access the workspace by the administrator or owner of the workspace
    WB_RT_WORKFLOW_UTIL_11G.Execute_Start(PFFPVSL, WB_IK_20090213_135803_19093, 366, RUN) Wf_Engine_Util.Function_Call(WB_RT_WORKFLOW_UTIL_11G.EXECUTE_START, PFFPVSL, WB_IK_20090213_135803_19093, 366, RUN)
    We've done the EXECUTE ANY PROCEDURE on the OWF_MGR user. The OWF service_doctor.sql script reports that "There are errors in one or more PL/SQL packages and functions", but fails to say anything else - everything is loaded and seeded correctly.
    But what we notice when comparing with our working 10g installation, is that the runtime repository target user (OWBRTREP) is totally empty of tables, views, procedures etc on the new runtime database, whereas it has about 250 tables and lots of other objects on the 10g installation. This user is created through the OWB 11g design center, so why is there such a difference? Has something gone wrong when creating the runtime workspace?
    (It was created with the Repository Assistant, which we had some trouble with on the 64-bit server, but after some work it now seems to run ok, exiting with success message after creating workspace user.)
    Regards,
    -Haakon-

    Haakon,
    Lets assume you have two databases with OWB Repository A installed on database A and OWB repository B installed on database B.
    Repository A - your Design repository
    Repository B - your Runtime repository (this is your target schema / database)
    I hope you have control centre service running under Repository B and you have installed OWF schema (usually OWF_MGR) under repository B.
    I hope in your repository A you have created a new configuration and new control centre to point to repository B and that configuration is active.
    Now logon to repository B using repository owner login and add OWF_MGR and other target databases as your target user under SECURITY/USERS.
    Create similar users under repository A.
    It works for us in OWB 10g but i dont know about 11G might be something related to WORKSPACE concept.
    Hope this helps.
    Thanks,
    Sam.

  • Unhandled exception occurred during the execution of the workflow instance

    I had a workflow and library working with no issues, but had to move the library and export the workflow to another subsite (though on the same web site/collection).  I followed these how-tos:
    http://msdn.microsoft.com/en-us/library/office/jj819316%28v=office.15%29.aspx
    http://technet.microsoft.com/en-us/library/ee428301%28v=office.15%29.aspx
    Anyway, I've stripped all actions from the workflow and only have an Assign Task, but get this below:
    An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentException: ContentTypeId at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
    instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
    To troubleshoot, I removed all library columns, removed then re-added the Custom Content type the New Document uses, and still the same error - with the workflow going into Suspended mode.
    I also tried the removal of the file from /Relationships%20List/allitems.aspx and de-activating then re-activating the SharePoint Publishing feature, also that didn't work.
    I've gone into ULS, but unable to find anything definitive, so not sure what to try next?
    Thank you,
    Chad

    Hi Chad,
    Glad to hear the issue is resolved. Content types could be used for multiple lists in SharePoint site at the same time.
    However, I'm not quite sure why you said the resolution is for a "bug". I read the article per your link:
    http://www.andrewconnell.com/blog/SP2013-Workflow-Custom-Task-Outcomes
    The article is showing how to create custom outcomes buttons in task forms. As I understand, the issue you encountered is that workflow migrated from the other site shows the suspended status.
    Please be more specific on the issue if assistance is needed. If this is the second question, I’d recommend you open another thread in the relevant forum and provide specific information about the issue. In order to avoid confusion and keep track of troubleshooting
    steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently.
    Thanks for the understanding.
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • Custom Workflow generates a thousand of Workflow Instances and EREs

    Hi everyone,
    I developed a Custom Workflow that complete user attributes information when a user select a value from a drop down list. I tested this workflow with a Request MPR  with an Action Type "Create" and the workflow Works perfectly. But now, I
    have to use this workflow in an Action Type "Modify" , when I changed it, the workflow Works fine but generates  a thousand of Workflow Instances and in consequence a thousand of EREs.
    Can you help me please?
    Thanks in advance,

    Make sure that the change invoked by your workflow is not used as button to run another workflow - described scenario looks like you have created a loop.
    If you found my post helpful, please give it a Helpful vote. If it answered your question, remember to mark it as an Answer.

  • Error while creating concurrent workflow instances with dynamic participant

    Hi All,
    I have a workflow which has 3 interactive activites. The second interactive activity has requires approval of atleast 3 users to proceed. The participants are also not known in advance and are created dynamically by creating the directory session. The workflow is instantiated using an external trigger. The approval for interactive activities is also provided by an external trigger (API call).
    Now, there is a scenario where i have 1000 requests coming in to ALBPM and workflow instance should be created for each of them. But only one instance is created and for the rest i get the following exception. This also happens with just 2 requests. I also tried calling the API in a synchronized way but didnt help.
    Is anybody aware why is this error encountered anf how it can be resolved?
    java.lang.IllegalStateException: Cannot set the directory Connector Service while connector service is started
    at fuego.connector.CompositeConnectorService.setDirectoryConnectorService(CompositeConnectorService.java:97)
    at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:52)
    at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:265)
    at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:217)
    at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:199)
    at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
    at fuego.directory.Directory.fillPassport(Directory.java:122)
    at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:274)

    Hi Dan,
    Thanks for replying and giving attention. I have the following scenario :-
    1. I am getting a list of identifiers(some number) from a third party application along with the users/participants who are liable to approve the workflow instance.
    2. I create a workflow instance using this identifier through PAPI using process service session and also create the user/participant through PAPI by using the following code. Please note that i dont create participant in ALBPM instead i do it programatically in java using the PAPI :-
    DirectorySession directorysession = null;
    if (userVO != null && userVO.getUserId() != null && !userVO.getUserId().trim().equals(""))
    +{+
    +     directorysession = this.createFDISession();+
    +     List<RoleAssignment> roleAssignmentList = new ArrayList<RoleAssignment>();+
    +     try {+
    DirOrganizationalRole[] dirOrganizationalRoleArray = DirOrganizationalRole.fetchAll(directorysession);
    for(int i=0; dirOrganizationalRoleArray!=null && i<dirOrganizationalRoleArray.length; i+) {+
    +DirOrganizationalRole role = dirOrganizationalRoleArray;+
    +}+
    int permissions = -1;
    permissions
    += 0 |+
    DirHumanParticipant.getPermissionValue("X") |
    DirHumanParticipant.getPermissionValue("R") |
    DirHumanParticipant.getPermissionValue("S") |
    DirHumanParticipant.getPermissionValue("A") |
    DirHumanParticipant.getPermissionValue("D") |
    DirHumanParticipant.getPermissionValue("E") |
    +0;+
    +String[] whichRoles = new String[]{+
    +"Approver",+
    +"Requestor",+
    +};+
    +DirHumanParticipant.RoleAssignment[] roleAssignments = new DirHumanParticipant.RoleAssignment[whichRoles.length];+
    for(int i=0; i<whichRoles.length; i+) {+
    +roleAssignments[i] = new DirHumanParticipant.RoleAssignment(whichRoles[i], permissions, DirOrganizationalRole.fetch(directorysession, whichRoles[i]).getIn());+
    +}+
    +     String organizationUnit = configuration.getProperty("ORGANIZATION_UNIT");//fuegoFileProperties.getProperty(BVIDConstants.FUEGO_CONNECTIVITY_KEY_ORGANIZATION_UNIT);+
    +     String newUserPwd = configuration.getProperty("FUEGO_FDI_NEW_USER_PASSWORD");//fuegoFileProperties.getProperty(BVIDConstants.FUEGO_CONNECTIVITY_KEY_FDI_PWD);+
    +     DirOrganizationalUnit orgUnit = DirOrganizationalUnit.fetch(directorysession,organizationUnit);+
    +     DirHumanParticipant user = DirHumanParticipant.create(directorysession, userVO.getUserId(), userVO.getFirstName(), userVO.getLastName(),+
    +                              userVO.getFirstName(), userVO.getEmail(), userVO.getPhone(), "",+
    +                              newUserPwd, orgUnit,roleAssignments, true);+
    +     user.update();+
    +     }+
    +     finally+
    +     {+
    +               log.info("diconnecting the directory session created for creating participant");+
    +               directorysession.disconnect();+
    +     }+
    +}+
    3. The workflow instance then waits at interactive activity to get the next trigger with the same identifier to move the workflow ahead.
    4. Now the case is that i can get 1000 such identifiers at a time in a file which i ll read for which i need to create 1000 workflow instances parallely. During this process i get the following exception : -
    java.lang.IllegalStateException: Cannot set the directory Connector Service while connector service is started
    at fuego.connector.CompositeConnectorService.setDirectoryConnectorService(CompositeConnectorService.java:97)
    at fuego.connector.CompositeConnectorService.restartDirectoryConnectorService(CompositeConnectorService.java:52)
    at fuego.directory.DirectoryConfigurationManager.loadDirectoryConfiguration(DirectoryConfigurationManager.java:265)
    at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:217)
    at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:199)
    at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
    at fuego.directory.Directory.fillPassport(Directory.java:122)
    at fuego.directory.DirectoryPassport.fillPassport(DirectoryPassport.java:274)
    Please let me know if you need any more information. awaiting your help
    Thanks,
    Anand

  • Any restrictions on # of Workflow / Instances that ALBPM can handle?

    Is there any restrictions on No of workflow/ instances that ALBPM 5.7 can handle in production. I'm not worrying about handling number of simultaneous request but actual number of workflow / instances it can handle in due course.
    Thanks,
    Bharat

    9 pages max

  • Web Dynpro ABAP Workflow Attachment Problem in UWL

    Hi,
    I am writing a custom application.
    A workflow is supposed to start by a Web Dynpro ABAP Application.
    The user can attach files to it.
    A superior is supposed to review the files and either approve or reject the request.
    I tried the following in Web Ddynpro ABAP: 
    CALL FUNCTION 'EWW_WORKFLOW_START'
        EXPORTING
          X_TASK                       = 'WS90000074'
        IMPORTING
          Y_WORKFLOW_ID       = lv_WF_ID
        TABLES
          X_CONTAINER               = lv_IT_CONTAINER
        EXCEPTIONS
    then followed  by:
    CALL FUNCTION 'SAP_WAPI_ATTACHMENT_ADD'
      EXPORTING
        WORKITEM_ID                 = lv_wf_id
        ATT_HEADER                   = lv_swr_att_header
        ATT_BIN                           = Item_FILENAMEATTACHED
        DOCUMENT_OWNER       = SY-UNAME
        LANGUAGE                     = SY-LANGU
    IMPORTING
        ATT_ID                              = lv_swr_att_id
    The Workflow has onlay one user decision step and one notification Step.
    In the user decision step, there is a binding from ATTACHOBJECTS to the task.
    But, in the log, you can see the attachment in the Workflow Container of the workflow instance, but you don't see it in the task (neither Inbox nor UWL)
    Anyone has a suggestion?

    You need to update all task items one by one with the attachment - you need to identify all tasks and attach it to each one

  • No Workflow Instance

    Hi,
    We are using a batch program to trigger workflows for appraisal. Initially we tried for 3 users and the workflows were triggered properly. Then we ran the program for chunks of 50 users and when I checked the Event Trace, it says "Receiver started correctly", but the RFC status says "User is locked. Please notify the person responsib". I cannot see any workflow instance for these users in SWI1. Now even when I run the workflow trigger program for one user the status says "User is locked. Please notify the person responsib". I checked the logged on user and it is not locked. What could be the error? Pls help
    Event trace details
    EVENT DATA:
    Event Instance ID    2419876
    Object Type          APPR_DOC
    Object Key           01DDB4883F197144F18C480015600EB0690000
    Event                START_TARGET_SETTING
    Event Creator        US SSOPER         SAP
    Creation Time        26.11.2008 12:01:54 UTC+8
    RECEIVER DATA
    Receiver Type        WS99800015
    Object Key
    Receiver FM          SWW_WI_CREATE_VIA_EVENT_IBF
    RFC Destination      WORKFLOW_LOCAL_800
    Check FM
    Receiver Type FM
    TRACE DATA
    Trace Date/Time      26.11.2008 12:01:54 UTC+8
    User Name            SSOPER         SAP
    Main Program         RHHAP_APP_DOCUMENT_ADMIN_PA
    Action               Receiver started correctly
    RFC Status           User is locked. Please notify the person responsib
    Regds
    Thiru

    Hi,
    the workflow background user is configured here as SSOPER SAP. This user is locked. Please correct this via transaction SU01.
    The configuration of the user and logical destination can also be maintained with transaction SWU3.
    Have fun,
       Florin

  • PO Create - Workflow - Mail Problem

    Hi experts,
    I have an workflow that trigers after PO creation.(BUS2012). Then it sends a mail. But, mail does not work correctly. In SBWP , if i run the workflow, mail comes to inbox. I want it works directly.
    Waiting for helps.
    Regards,
    Orhan

    Hi,
    Can I know which event and method you are using to send mail after the PO creation.
    Is the workflow instance is created or not on the PO creation.
    Regards,
    Aditya

  • [q] change workflow instance id

    hI All,
    How can I change a WLI2.0 workflow ID after the workflow has started ?
    The workflow is initialized via the WLI2.0 queue with an XML. I then call a
    business operation
    that give me the value that I need to put in the workflow ID. How do I do
    that ?
    Thanxs,
    Ronen Yaari

    I have the same question, and I would like to be able to get to
    the actual "label" as opposed to setting up a new process
    variable. It is not accessible in the dialog box.
    Thanks
    John
    "Kara Moscoe" <[email protected]> wrote:
    When you say "workflow ID", do you mean the system-generated instance
    ID, or
    do you mean the template definition ID -- or "label" -- that you define
    in
    the Template Definition properties dialog? (There is some confusion around
    these, for which a CR has been opened.)
    If it's the latter, you should simply be able to specify a workflow variable
    name, and specify that variable as the return variable in the Perform
    Business Operation action for the business operation in question. If
    you
    want to manually intervene during a running workflow to change a variable
    value, you can also use the Update variables function in the Workflow
    Variables dialog box, accessed from the Workflow Instances dialog.
    Kara
    Ronen Yaari <[email protected]> wrote in message
    news:[email protected]..
    hI All,
    How can I change a WLI2.0 workflow ID after the workflow has started?
    The workflow is initialized via the WLI2.0 queue with an XML. I thencall
    a
    business operation
    that give me the value that I need to put in the workflow ID. How doI do
    that ?
    Thanxs,
    Ronen Yaari

  • Assigning a workflow instance ID

    Hi,
    I just want to know if it's possible to assign my own instance ID when instantiating
    a workflow.
    Thanks.

    I have the same question, and I would like to be able to get to
    the actual "label" as opposed to setting up a new process
    variable. It is not accessible in the dialog box.
    Thanks
    John
    "Kara Moscoe" <[email protected]> wrote:
    When you say "workflow ID", do you mean the system-generated instance
    ID, or
    do you mean the template definition ID -- or "label" -- that you define
    in
    the Template Definition properties dialog? (There is some confusion around
    these, for which a CR has been opened.)
    If it's the latter, you should simply be able to specify a workflow variable
    name, and specify that variable as the return variable in the Perform
    Business Operation action for the business operation in question. If
    you
    want to manually intervene during a running workflow to change a variable
    value, you can also use the Update variables function in the Workflow
    Variables dialog box, accessed from the Workflow Instances dialog.
    Kara
    Ronen Yaari <[email protected]> wrote in message
    news:[email protected]..
    hI All,
    How can I change a WLI2.0 workflow ID after the workflow has started?
    The workflow is initialized via the WLI2.0 queue with an XML. I thencall
    a
    business operation
    that give me the value that I need to put in the workflow ID. How doI do
    that ?
    Thanxs,
    Ronen Yaari

Maybe you are looking for

  • Hiding fields in phtmlb:formLayout (new thread)

    Original Thread: hiding fields in a bsp... What Kevin is talking about, is some special development we did for HR eRecruitement. Well, let us turn it around. They helped us, and we returned the favour. And yes, this is actually some of the more inter

  • Rogue implicit SELECT FOR UPDATE statement in forms 9i  9.0.4.0.19

    all, out of 200 production forms, one form occasionally and incorrectly "selects for update" an entire 3 million row table, during an update transaction. this creates 100+ archive logs. we cannot repeat the event via testing. but the rogue select sta

  • Installing Windows XP without Boot Camp

    Ok, so i started with a small Windows XP partition, and i wanted to resize it so i could install Call of Duty 4, well i deleted the partition, then tried to make a new larger partition, well it wouldn't work i kept getting an error in Boot Camp Assis

  • Java.sql.SQLException: ORA-08103: object no longer exists

    hi, Everyone: i want to insert one colume to a temp table, so i did the following 1: drop the table 2: recreate the table with the new colume in it. we i run my application, there is a "java sql exception ORA-08103: object no longer exists ". looks l

  • Uploading a project.  Help?!?!

    I had premiere elements 9 on my old computer.  Just got a new one and have elements 11 now.  Can I load a saved project from 9 into 11?  when I try to open the project in 11 it says " this type of file is not supported, or the required codec is not i