on 06-18-2008 9:54 PM
How can I shutdown a parent workflow from a subworkflow? If I use the Process control (Cancel workflow including all callers), then it puts the main workflow in error?
Thanks in advance. Will award points
Thanks to all who responded. Actually the way I resolved the problem was to raise the Rejected event of FIPP not through the a raise event step of the workflow, but though a custom method in ZFIPP (subtype of FIPP. I could then see the event in SWEL (event trace). That way all sub workflows listening for the rejected event in a fork could shutdown.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks a lot to all that have answered. I have tried your suggestions. However my scenario, which I will try to do a better job this time of detailing is as follows
I have a parent workflow which will spawn of multiple parallel sub workflows.
Now, on rejection of any one of the sub workflows, I need to cancel all the parallel subworkflows and have the parent workflow proceed with it's own logic.
I tried achieving this with local events on the sub-workflow which I would trigger on rejection and listen to in a fork for shutting it down.
I also tried this with Business Object events like the REJECTED event of FIPP.
However this only works for that particular sub workflow and not the other parallel subworkflows.
The only step that shuts down all parallel subworkflows is the Process control step (Cancel workflow including all callers). The main problem is that this shuts down the parent workflow also which is not acceptable.
So summarizing, I am looking for some advice where all parallel sub worklflows can be shut down from any one of the sub workflows, without shutting down the parent workflow.
Thanks a lot in advance. I will award points
Edited by: Amlan Bardhan on Jun 26, 2008 12:00 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What you are trying to achieve here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you can use
Version Dependent Data by going to Workflow Builder
PFTC->GOTO Basic Data->Version Dependent->Events->Receiver Type use accordingly as Martin said to trigger an event from Subworkflow.
Thanks
Arghadip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If a process control step doesn't work (I couldn't tell you at this moment), you can always use a terminating event. Depending on how you want the workflow to be ended you can set it in a paralel branch in the main workflow or at the header of the workflow. Then in the subflow you raise the event.
Regards,
Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
use process as workflow complete
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.