Wait for significantly changed event not working

[Former Member]

I have a PO release strategy workflow where i am using fork,in which one branch contains a significantly changed event,the other contains the approval process.

The approval process is splitted into two.If purchasing group is not 600,we are not using deadline monitoring.If PO group is 600,then we are making use of deadline monitoring.Here once the first approver doesnot respond for 1 day,it will go to second approver and wait in his inbox.

If the PO is changed in the mean time,the workitem in the second approvers inbox is not disappearing.

But we need the new PO workitem to be in the first approvers inbox & the second approvers workitem to disappear.

If the deadline is not missed,if the workitem is in the first approvers inbox & PO is changed,the new changed PO workitem will come to the first approvers inbox.Means Wait for significantly changed event is working here.

Is it like once a workitem has missed its deadline,Wait for significantly changed event will not effect?

Or does it depends on the release strategy?because the PO amount is changed ,it triggers the same release strategy for the first approver.

Thanks.

[Former Member · Accepted solution]

Significantly Changed event is getting triggered only when release strategy is changed.

Changed event is getting triggered even if the amount is changed for the same release strategy.

Can i use Changed event instead of Significantly Changed Event?

[Former Member · Accepted solution]

Use the Change Event not as a Terminating event of the task but in a Wait for Change Event step which is put in 1 branch of a fork and the approval step in another. I think you should put the Wait for event step in a loop to filter whether the changes is for amount because this event gets triggered for unimportant changes which is not relevant to your requirment. Make use of CDHDR amd CDPOS table entries to filter the changes.

Thanks

Arghadip

[imthiaz_ahmed · Accepted solution]

Significantly changed event happens based on your release strategy set up. Your characteristic set up. Plus the tolerance of changes. But I think you don't want the Release process to re-initiate for all the changes. If yes, you should not use "Change" event. Customize you release strategy as per your need.Then the "Sginificantly change" event will get triggered.

Regards, IA