Skip to main content
Nintex Community Menu Bar
Solved

Change by stage inquiry

  • July 16, 2024
  • 2 replies
  • 29 views
  • Translate

Forum|alt.badge.img+7

Hi - I have a question re subsequent actions after a change in stage action is implemented. As shown in the screenshot, is the “Legal approval notification” sent out if the next stage is Legal final review? Or does it skip this notification and move to Legal final review directly? If the latter, should I add a Branch by value action to make sure the Legal approval notification email is sent out regardless of the outcome of the Legal initial review? Thanks.

 

Best answer by brent_read

Hi @mjliu 

The notification should send in all cases for the legal initial review, including “No Material Discrepancies” branch where you have put the option to exit.  Branch by stage actions continue to the end of their logical loop before evaluating which branch to go to next.  Because of this, its generally easier to make sure the last action before the end of a branch is a change stage action.  This ensures that the branches are easily navigable and prevents the possibility of infinite loops being generated.

You can also think of the branch by stage action working as a loop with a branch by value action inside it.  the loop and the branch by stage both evaluate a “stage” variable at the end of each loop to determine if it should 1) exit the loop and 2) go to a specific stage and execute that branch.  the change stage actions are effectively setting that variable, not doing the evaluation of it.

 

Hope that helps!

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+9
  • Nintex Employee
  • 69 replies
  • Answer
  • July 16, 2024

Hi @mjliu 

The notification should send in all cases for the legal initial review, including “No Material Discrepancies” branch where you have put the option to exit.  Branch by stage actions continue to the end of their logical loop before evaluating which branch to go to next.  Because of this, its generally easier to make sure the last action before the end of a branch is a change stage action.  This ensures that the branches are easily navigable and prevents the possibility of infinite loops being generated.

You can also think of the branch by stage action working as a loop with a branch by value action inside it.  the loop and the branch by stage both evaluate a “stage” variable at the end of each loop to determine if it should 1) exit the loop and 2) go to a specific stage and execute that branch.  the change stage actions are effectively setting that variable, not doing the evaluation of it.

 

Hope that helps!

Translate

Forum|alt.badge.img+7
  • Author
  • Scholar
  • 58 replies
  • July 16, 2024

Thanks!!

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings