UiPath advanced dev

Question 1

State Machine

Answer 1

exception handling
recovery abilities
effective logging
reporting functionality
high maintainability and extensibility
reusability
ease of development

Question 2

Framework template states

Answer 2

Init - config, init app, add queue
Get Set - get transaction data
Process - execute transaction
End

Transaction status - success, rule exception, error, no data

Exception Handling - try catch of each state

Question 3

Init

Answer 3

Init config
- setting for business data - URL, queue names
- constants stores technical details necessary for developers, (e.g. program delay time. max retry for applications or system exceptions)
- assets for data to be retrieved from Orchestrator
Init apps (kills and start)

Question 4

Robotic enterprise framework

Answer 4

Built on top of Transactional Business Process template
Uses State Machine layout for the phases of automation project
Offers high level logging, exception handling and recovery
Keeps external settings in Config.xlsx file and Orchestrator assets
Pulls credentials from Orchestrator assets and Windows Credential Manager
Gets transaction data from Orchestrator queue and updates back status
Takes screenshots in case of system exceptions

Question 5

Sequences

Answer 5

Sequences have a simple linear representation that flows from top to bottom and are best suited for simple scenarios when activities follow each other.

Question 6

Flowcharts

Answer 6

Flowcharts offer more flexibility for connecting activities and tend to lay out a workflow in a plain two-dimensional manner. The most important aspect of flowcharts is that, unlike sequences, they present multiple branching logical operators, that enable you to create complex business processes and connect activities in multiple ways.

Flowcharts tend to be used for workflows which contain multiple decision points.

Question 7

State machine

Answer 7

Some processes are better expressed as interconnected states which are executed again and again whenever necessary. A set of activities are performed in each state and then a condition is evaluated to determine what state to transition to next.

Question 8

Global Exception Handler

Answer 8

The Exception Handler is designed to be used in both small and large automation projects, for identifying execution errors and most importantly, determining the workflow behavior when such an error occurs. If an execution error is encountered during debugging, the Global Exception Handler may be set to step in and allow you to check the workflow’s behavior in accordance to the options previously set in the Exception Handler.

Question 9

variable Naming Conventions

Answer 9

Snake case: First1_Name2, first_name2,
Upper or lower Camel case: FirstName, lastName,
Pascal case: First1Name2, First1Name,
Kebab case: First-Name, First-Name1.

Argument names should have a prefix stating the argument type, such as in_DefaultTimeout, in_FileName, out_TextResult, io_RetryNumber.

Activity names should concisely reflect the action taken, such as Click the Save Button. Keep the part of the title that describes the action (Click, Type Into, Element Exists, etc.).

Question 10

State machine states and transitions

Answer 10

Transitions are created when you link a State to another State or to a Final State, within a State Machine container. Transitions should be defined in a way that only transition can be true!

You can only create one initial state, yet it is possible to have more than one Final State. All state machines must contain an initial state and at least one final state.

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.

Question 11

Design principles

Answer 11

Breaking the process in smaller workflows is paramount to good project design. Dedicated workflows allow independent testing of components while encouraging team collaboration by developing working on separate files.

Choose the layout type wisely (flowcharts and sequences). Normally the logic of the process stays in flowcharts while the navigation and data processing is in sequences.

By developing complex logic within a sequence, you will end up with a labyrinth of containers and decisional blocks, very difficult to follow and update.

No credentials should be stored in the workflow directly, but rather loaded from safer places like local Windows Credential Store or Orchestrator assets. You can use them in workflows via the GetCredential activity.

Keep clean Remove unreferenced variables.
Delete temporary Write Line outputs.
Delete disabled code. Make sure the naming is meaningful and unique. Remove unnecessary containers (Right-click > Remove Sequence).