Can you change states based on the last task respondent

[#1]

I am working on a state machine workflow for change management. I have 10 different states. I am trying to figure out a way to minimize going through every state each time the request is rejected. If one state rejects the change request, I am bouncing it back to the initiator for cancelation or resubmission. If the initiator resubmits, I'd like to change the state back to the one who rejected it for review instead of going through all the states one by one.

[fhunth · Accepted solution]

I use to use a workflow variable named varLastState to save the lastState.

Then, after the initiator 's response, change state to a state named regretingDenier where you decide what state you must change based on varLastState. I suggest you not to base your decision on the last respondent because you could have a person covering different roles.

[#3]

Thank you. What action are you using to get the last state?

[fhunth]

I use a Nintex Workflow variable and set it on each state

[#5]

Fernando's on track

[#6]

To save the last state, are you querying the list to get that information?

[fhunth]

I'm setting a kind of my own internal states.

I set them on a string variable as needed