cancel
Showing results for 
Search instead for 
Did you mean: 
Workflow Hero

State Machine advice

Jump to solution

Hi!

I'm tying myself up in knots trying to figure out the best way to deal with a secondary approval cycle.

Firstly - is it ok to add a state machine within an existing state machine branch, or is there a better way?  Here is a snapshot of what I have so far:

State Machine

At the moment I've inserted a Switch action to show the different branches which consist of: Live; On Hold; Cancelled; Closed.  There is potential for the status of the item to switch between Live and On Hold multiple times until it is either Cancelled or Closed.  To achieve this, would be it best to add another State Machine, or use Looping?  I tend not to use Looping where possible, but am open to it if advised.

Thank you for your time

Labels: (1)
Reply
1 Reply
Workflow Hero

Re: State Machine advice

Jump to solution

I found this thread and believe that it gives me a good understanding of using a secondary/sub state machine so will use this to help with my query:

 

Thank you!

Reply