Washington-adi
Scholar

Preventing users from changing the Phase

Jump to solution

I've created automated emails to customers based on the project state they are in. 

State = 1) Approvals 2) initiate 3) Execution 4) Closure.

 

Using a switch to verify state value and executing certain steps. (like sending Sr. Exexs for approvals or sending emails to customers that project is initiated, sending vendors to start the project work.)

 

One of my customer, accidentall changed Closure state to Approvals. That triggered emails to Sr. Execs to approve a completed project. 

 

How to prevent this accidentally change. 

0 Kudos
Reply
1 Reply
SimonMuntz
Nintex Employee
Nintex Employee

Re: Preventing users from changing the Phase

Jump to solution
Use a state machine that allocates tasks and the state only changes based on the task completion.

View solution in original post

0 Kudos
Reply