You are viewing limited content. For full access, please sign in.

Question

Question

Validation detected errors: Default Outflow Path

asked on July 15, 2021 Show version history

Hi, first time posting in the LF Answers so hopefully I'm in the right place but this error message started popping up after the recent Cloud update warning us that it was possible for this process could fail because there isn't a default outflow path. 

There are only two conditions for this task - the form is either approved or rejected so things are working correctly. I want to do this the correct way though and wondering if what I need to do is keep the first condition (approved) and then set the second condition (rejected) as the default? If I do that, does it look for approval first and follow that flow and only send it on the rejection path if the form was rejected by the task owner? 

Thanks for any help. I don't want to blow up a process we recently launched to the public. :) 

Screenshot 2021-07-15 133052.jpg
0 0

Answer

SELECTED ANSWER
replied on July 15, 2021 Show version history

Hi Melanie,

In the Business Process Modeler a conditional gateway with multiple outflows should always have at least one Default path to follow, especially in the event something goes wrong.

There are a few options,

  • Make "Approved" the default so it only takes the other path if the ="Reject" condition is met
  • Make "Rejected" the default so it only takes the other path if the ="Approve" condition is met
  • Add a third default path that ends the process or sends notification or something

 

Typically, I default my outflows to "fail closed" meaning the default path is the one that would create the least amount of issues (i.e., if someone changed your Reject button to Deny and neglected to update the gateways, then you wouldn't want it to suspend, or worse yet, treat that as as an approval).

For example, in your case, I would remove the Rejected path's condition and check the box to make that the default, which would basically make the process "fail closed" if the condition is not approved and something unexpected happens.

Long story short, always include at least one outflow path with Default checked so your process always has a path to follow even when something unexpected happens with your conditions.

3 0
replied on August 11, 2021

I apologize for the delayed response. This answer helped me tremendously, thank you! I set the default to rejected for now but might go back to create a third condition that captures and manages any other odd scenarios. 

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.