Clarity PPM

Expand all | Collapse all

How to avoid process trigger by system action from another process?

Jump to Best Answer
  • 1.  How to avoid process trigger by system action from another process?

    Posted 01-21-2019 05:53 AM

    Dear All,

     

    We have one specific issue related to process trigger on update action.

     

    We have a ProcessA (even = Project Create) which contains couple of system actions to set attributes value.

     

    Another ProcessB (even = Project Update, no start condition) which should sent list of attributes to another tool after each project update (not create). 

     

    Problem is that each system action from ProcessA trigger ProcessB so "Organizer - Initated Processes" after project create looks like:

    ProcessB 

    ProcessB 

    ProcessB 

    ProcessB 

    ProcessA 

     

    do you have any idea how to avoid ProcessB trigger by system action from ProcessA . 

     

    Many thanks and best regards,
    Marian.



  • 2.  Re: How to avoid process trigger by system action from another process?

    Posted 01-21-2019 08:12 PM

    Create two additional attribute 'Ready to send data to other application' and 'Date to send data to other application

    Either manually set this flag, or have it set as part of Process A - last step.  Set 'Date to send data to other application' as being TODAY + 1

    Set Process B to only run when 'Ready to send data to other application' is TRUE, and 'Date to send data to other application' < TODAY

     

    Haven't checked to see if above is possible, so just a suggestion.



  • 3.  Re: How to avoid process trigger by system action from another process?

    Posted 01-22-2019 04:30 AM

    Hello Roland,

    Thanks for quick reply. Meantime I've got this advice from CA support:

    1. Create a Boolean attribute on the Project object. Enable it for Audit 2. In the Create process set this Boolean attribute to 0 before any other action is taken. Set it back to 1 when the process is about to complete.
    2. In the Update process, set the Start Condition as:
    3. Boolean attribute value = 1 and
    4. Boolean attribute previous value != 0

     

    this works in simple case but it doesn't worth in out configuration because there are more process with create even, and project is created by process (which is invoked by XOG) so It requires modification in many places.

     

    I'm going to use condition last_updated_date > created_date + 5 min in script. Better it would be in process start condition but I did not find the way how to use it there (not possible use date function even calculated field in process start condition )

     

    Marian.



  • 4.  Re: How to avoid process trigger by system action from another process?

    Posted 01-22-2019 11:43 PM

    Marian, please consider also how Process A is updating the attributes, potentially these are undertaken by individual updates, as this may explain why you are seeing Process B starting off X times.  If you modified the update to be one XOG update on the Project, Process B should only fire once.  In addition, make sure 'Do not start a new process if one is already running' has been 'ticked' on Process B.



  • 5.  Re: How to avoid process trigger by system action from another process?

    Posted 01-23-2019 02:22 AM

    with this example its more easier to use our solution just don't give rights to system account under which you are sending webservice message (XOG) to initiate the Process B



  • 6.  Re: How to avoid process trigger by system action from another process?
    Best Answer

    Posted 01-23-2019 02:18 AM

    Hello Marian,

    we have facing similar problem and we solve it with Process A (on create) invokes Process C (ad hoc) under system account which provide all updates and this system account doesn't have rights to start Process B (on update).

    Vit



  • 7.  Re: How to avoid process trigger by system action from another process?

    Posted 02-07-2019 01:07 PM

    Thanks to all for suggestions.

     

    The solution from Vit works very well for my case.

    Actually I only removed execute rights (for Process B - on update) for "PPM Administrator", which is doing all changes during project create (by process) phase. During the next project life is "Process B" required only after "save" so not PPM Administrator relevant.

     

    BR,

    Marian.