on 06-01-2017 11:58 AM
Hi,
My WF triggers for BUS2012.RELEASESTEPCREATED which is maintained.
SWETYPV has this one entry only.
PO has multiple approvers. My WF is built where same instance will loop for multiple approvers.
So now when PO created, ReleaseStepCreated triggers once, workitem goes to first approver. First approver approves it, same instance of WF sends workitem to second approver. On top of that, another instance of WF is also triggered for ReleaseStepCreated and workitem sent to approver-2.
So Approver-2 and above gets 2 workitems, one from the main WF that got triggered and one from WF which triggers after first approver actions it.
Strange, I have built so many PO WF, such issue never occurred. Also I checked SWEL and I could see ReleaseStepCreated event and Released event.
Though Released event has no receiver type.
Aditya V
Hi,
You can use conditions on your workflow to only trigger for the first approval release code. Or you can change the release code in define release procedure to not trigger an event (just remove the 1 or the 9 in the workflow field)
Kind regards, Rob Dielemans
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This sounds exactly right. Between config and workflow, only one can manage the release procedure. Using both will cause duplicates.
By tying your WF to the releasestepcreated event you are using config as the driver and thus shouldn't manage the release steps in your WF. Each release will have it's own WF instance. This is the SAP-delivered scenario.
Alternatively if the release procedure should be managed by WF, you would need a custom event to trigger a WF.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If after every approval ,release code is approved ,then releasestepcreated event is triggered.
Check in event trace how many times the event is triggered .
Post that you can write custom check FM to not start any new workflow if a previous workflow instance is already in process for the same object key.
Or else you can raise event and complete previous workflow instances.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rob,
yes I had thought of modifying it with just single release and not loop the Release Code.
Lets see have proposed the same.
Thanks,
Aditya V
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.