Wait for Event: Workflow and Subworkflow

[Kjetil Kilhavn]

When two workitems/workflows are listening for the same event they will
both receive it, so you have to either use two different events or re-model
your workflow.
 
If it is true that your main workflow should not be active after the
deadline then the step that waits for the event should be obsoleted first.
Alternatively you could perhaps introduce a loop and set a container
element when the deadline passes and check that to see if the mail should
be sent. Your mail step must then be placed before the action step. On the
first iteration no mail is sent, on the second iteration an e-mail is sent
because you have set the indicator. That also saves maintenance as you
don't need two almost identical workflows.
 
Perhaps you can even be fancy and check the current time against the
workflow creation time instead of checking an indicator. Saves you one
container element. Not sure how well such a comparison, if (syst-datum -
workflow.createddate) > 5, is handled in workflow though. Creating an
indicator is probably a lot simpler, and who cares about a few more bytes
of storage anyway :-)
--
Kjetil Kilhavn
 
 
 
 
                    Chenna Kiran Kumar
                    <chenna.kiran at wipro.        To:     SAP-WUG at MITVMA.MIT.EDU
                    com>                        cc:     (bcc: Kjetil Kilhavn)
                    Sent by: SAP                Subject:     Wait for Event: Workflow and  Subworkflow
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    29.09.2004 06:53
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
 
Hi,
 
       We have a deadline monitoring for our workflow. If a workitem is not
processed in 5 days then Subworkflow is called.The subworkflow is a replica
of the main workflow with just an addition of one more send mail step.I
have got a same wait for Event( Approved) in both main and sub workflows.
This event is triggerred from an RFC FM based on the decision taken .
Now the problem is when the dead line monitoring becomes active (no action
taken for 5 days). then the subworkflow is called and then event approved
is triggerred from RFC FM.but then, even the main workflow resumes its
course as well as subworkflow. I have tried very much to stop the main
workflow getting resumed, but in vain. is there any possible way to handle
this.As a last effort  i am thinking of having 2 separate events rather
than single 'Approved' for main and sub workflow and trigger them using a
condition in RFC. is this a better alternative to this?
 
thanks & regards,
Chenna
 
 
 
Confidentiality Notice
 
The information contained in this electronic message and any attachments to
this message are intended
for the exclusive use of the addressee(s) and may contain confidential or
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
Mailadmin at wipro.com immediately
and destroy all copies of this message and any attachments.
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.