Workflow Organization: Sequence, Flowchart, State Machine, Invoke Workflow

1. Machina Automation Fast-Track UiPath Developer Module 3: Workflow Organization

2. 3 – Workflow Organization • Overview: This module introduces the Sequence, Flowchart, and State Machine containers and the Invoke Workflow File activity. These elements are used to organize your automated workflows and keep them operating as efficiently as possible. • Organization: This module is organized into the following sections: • 3.1: Sequence vs Flowchart • 3.2: State Machine • 3.3: Invoke Workflow File

3. 3.1 – Sequence vs Flowchart • Sequences are the smallest type of project, and they are used for linear processes that do not have to branch and loop back on themselves • Flowcharts are capable of handling more complex processes that branch and connect in multiple ways • Sequences can be used inside of other Sequences and inside of Flowcharts • Flowcharts can be used inside of other Flowcharts and inside of Sequences • Rules of thumb: • if you find yourself using nested If activities in a Sequence, use a Flowchart instead • if you are automating a process that repeats or loops back to prior steps, use a Flowchart instead of a Sequence

4. 3.1 – Sequence vs Flowchart Instead of this... Do this...

5. 3.1 – Sequence vs Flowchart Complete Exercise 3.1

6. 3.2 – State Machine • A state machine is a type of automation that uses a finite number of states in its execution. It can go into a state when it is triggered by an activity, and it exits that state when another activity is triggered. • Another important aspect of state machines are transitions, as they also enable you to add conditions based on which to jump from one state to another. These are represented by arrows or branches between states. • There are two activities found under Workflow > State Machine that are specific to state machines: • State • Final State

7. 3.2 – State Machine • The State activity contains three sections, Entry, Exit and Transition(s), while the Final State only contains one section, Entry. Both of these activities can be expanded by double-clicking them, to view more information and edit them. • The Entry and Exit sections enable you to add entry and exit triggers for the selected state, while the Transition(s) section displays all the transitions linked to the selected state.

8. 3.2 – State Machine

9. 3.2 – State Machine • You will learn more about State Machine later when we cover the Robotic Enterprise Framework.

10. 3.3 – Invoke Workflow File • Use the Invoke Workflow File activity when you want to run a process that is contained in another .xaml file from within the current automated workflow process • This allows developers to develop and use reusable component workflows while keeping their automated workflow processes efficient and well-organized • Use Arguments to pass values into and out of invoked workflow files • Right-clicking and selecting “Extract as Workflow” will turn the element clicked on into an external .xaml file and insert an Invoke Workflow activity linked to the new .xaml file in the place where the original element was in the current workflow Complete Exercise 3.2