Workflows are not Terminating

Hi Kirk Satoh,

All of our customer base is running on Sugar 13 and the ones using SugarBPM haven't had any issues like this of which I am aware.

Can you share some more detail about the design of the BPM definitions not terminating as expected? A screenshot of each design canvas would be helpful along with explanations of what is happening versus what is expected to happen in the design.

Chris

Hi Chris,

When a quote is created or updated a 3 day wait event starts. Once the 3 days is up and email notification is sent unless the WF is terminated. If the WF is not terminated then the process starts over again for a 2^nd and possibly a 3^rd time. After the 3^rd time the WF ends. In this example the WF made it to wait event #2 but should have terminated before the email was sent because one of the terminate criteria was met, the quote was placed on hold.

I have attached screenshots from the process management showing the WF and the history. I also included a screenshot of the audit log showing when the hold was placed and finally my terminate criteria. Link to File

Hi Kirk Satoh,

Thanks for sharing! You are using the 'Terminate Process' criteria for the entire process definition which is a feature I typically avoid using since it is not apparent to other users looking at the design that they may exist. I also do not find it intuitive to find those criteria, so I aim to have the entire process designed on the canvas to have better clarity on what logic goes into a process potentially ending. If you want to continue using 'Terminate Process' criteria, I recommend opening a support case with Sugar as it sounds like there is a defect based on all the evidence you shared. I agree that it should have ended when you expected.

Something to consider is the more visual approach to your design which should operate as you expect. I would use the start event and event-based gateways to accomplish the same use case you are with the Terminate Process criteria:

Your start event would rule out any quotes where Quote Team Approval or Quote Hold Status equals one of the restricted values. It then goes to evaluate the related Opportunity to ensure it is not in a closed won or lost status. Assuming those checks pass, it goes to the first event-based gateway where it routes based on whichever happens first:

1. 3 days elapse
2. The quote or related opportunity update to a restricted status (thus ending the process)

This gives you a clear indicator as to which route it will follow and each subsequent event-based gateway can leverage that same logic to determine whether it should proceed with sending an email alert or ending the process.

I hope this helps!

Chris

Thanks Chris Raffle  this is very helpful. I will redesign the WF but in the mean time I will open a ticket with Sugar because I have a few WF that I use the terminate process.

Thanks Chris Raffle  this is very helpful. I will redesign the WF but in the mean time I will open a ticket with Sugar because I have a few WF that I use the terminate process.

There is a bug with Sugar and a fix has been placed under consideration.

Issue #92423 Updated to Under Consideration

We are writing to update you on Issue #92423, BPM Terminate process condition is not working as expected.
https://portal.sugarondemand.com/#supp_Bugs/92423

The Issue status has been updated to Under Consideration

Issues in this status are not targeted for resolution within the next several releases but will be considered during future release planning activities.