Skip to Content
author's profile photo Former Member
Former Member

Wait for significantly changed event not working

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.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

5 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 03, 2008 at 07:36 AM

    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?

    Add a comment
    10|10000 characters needed characters exceeded

    • 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

  • author's profile photo Former Member
    Former Member
    Posted on Jun 27, 2008 at 01:19 PM

    It depends completely on your Release Strtaegy configuration you have done in SPRO. You need to change your configuration in SPRO. If you are not able to make then you can make use of Change Event of BUS2012. You can filter the changes whether it is relevant or not by creating a Virtual attribute and coding the relevant changes according to change document involving table CDHDR and CDPOS.

    Thanks

    Arghadip

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 27, 2008 at 04:42 PM

    I think you are using modeled deadline, then escalating the things. Check whether the escalated task has a terminating event "SignficantlyChanged".

    Note: I don't know why are you using a fork, when the standard already has a terminating event. If it is not there just add to the approval step.

    Regards, IA.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2008 at 12:04 PM

    You mean i need to add the terminating event to the user decision step?

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 30, 2008 at 12:08 PM

    I added terminating event "Significantly Changed" to the user decison step.Its not working.

    Requirement is : Once the workitem for a Purchase Order is escalated,If the PO is changed by someone for the same release strategy.The workitem should get disappear from the inbox & should appear in first approvers inbox.

    Thanks.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Check whether the SIGNIFICANTLYCHANGED event is getting triggered from SWEL. I think it is not and that is the reason your Workflow is not working as expécted. Please check the SPRO configuration for SIgnificantlYChanged configuration(RElease Srategy).

      Thanks

      Arghadip

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.