What is the meaning behind the logic of state activity of state machine?

In the state activity,

  1. the entry actions are performed first,
  2. then trigger actions,
  3. then the exit actions
  4. then the transition conditions are evaluated,
  5. then the actions inside transition conditions
  6. and then transitioned to different state

What’s the meaning behind such logic? Can someone give a real life example and a workflow utilizing all these states?

I’m looking for a detailed explanation. I’ve seen multiple UiPath forum links where they gave an explanation of these actions but none of them gave a real life example of the workflow which utilises these states. Some of them attached workflows but there’s nothing in the exit section, trigger actions. Even I see that ReFramework doesn’t utilize state machine properly. ReFramework doesn’t have any activities in exit section and trigger actions by default. User has to define activities inside them if needed.

I know this doesn’t answer your question, but in my opinion this stuff is overkill for most automations, and REFramework is very poorly designed. I built my own template to use instead of REFramework and mine is much simpler, more logical, and saves a ton of coding and testing time.

1 Like