Scribd
Upload
92 views

UI Path

The UiPath RE Framework is a recommended framework for building robust robotic processes using best practices. It includes features like clean starts and exits, automated recoveries, retries, status management, logging, and clean coding. The framework uses a state machine with three states - initializing, processing, and end. It also includes error handling capabilities and provides benefits like low code signature, separation of concerns, reusability, maintainability, exception recovery and retry capabilities, and audit logging.

Uploaded by

Pallavi Basutkar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
92 views

UI Path

The UiPath RE Framework is a recommended framework for building robust robotic processes using best practices. It includes features like clean starts and exits, automated recoveries, retries, status management, logging, and clean coding. The framework uses a state machine with three states - initializing, processing, and end. It also includes error handling capabilities and provides benefits like low code signature, separation of concerns, reusability, maintainability, exception recovery and retry capabilities, and audit logging.

Uploaded by

Pallavi Basutkar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Robotic Enterprise Framework

UiPath

Globant Proprietary | Confidential Information


RE Framework
RE-Framework is a framework recommended by UiPath
to help developers build processes with best industry
practice principles. This gives us the fundamental code to
create more robust processes. This involves…

❏ Clean starts and exists


❏ Automated recoveries
❏ Retries
❏ Status management
❏ Logging
❏ Clean coding

Globant Proprietary | Confidential Information


RE Framework - State Diagram

Globant Proprietary | Confidential Information


Concept of RE Framework
The framework is built on a State Machine which allows
us to control the state the robot is working on. The state
machine is setting the robot a path, given the state of
the robot that is based on conditionals. There are three
states

❏ Initializing State
❏ Processing State
❏ End State

Globant Proprietary | Confidential Information


Concept of RE Framework

Initializing State
The initializing state will start up applications and set up
static variables that are needed for the process, but also
cleaning the work environment so that the robot can
perform the process on a desktop without interruptions.
The major responsibilities of this state machine is

❏ Read Global config file


❏ Initialize all necessary applications
❏ Recover the environment from system error
for Robot by closing and initializing the all.

Globant Proprietary | Confidential Information


Concept of RE Framework

Processing State
The processing states are inside the happy path loop.
After every successful transaction the robot goes to
fetch the next. When there are no transactions left, the
robot will transit to the end state.

The RE-Framework has two processing states.

1. Get Transaction Data


2. Process Transaction

Globant Proprietary | Confidential Information


Concept of RE Framework

End State
The end state, unlike the initialization state and
processing state, has no transitions. It is the last state in
the process. At this point the robot will go ahead and log
out of the applications and try to close what it has been
working on during its run. In the case of failure, it will
force a shutdown of the applications by sending a “kill
application” command.

Globant Proprietary | Confidential Information


Concept of RE Framework

Error Handling
REFramework gives us a high-level error handling
process so that the state of the robot can change
depending on what sort of error it is. It keeps track on
two different errors.

1. Business exception
2. Application exception

We can adjust for more error types in the framework. A


Business exception will be thrown when the error
depends on the information given to the robot.
Application exception is when an application is not
functioning as it is supposed to, when there is no
internet connection for example. This error will execute
the retry process as opposed to the Business exception,
because it might work the second time.

Globant Proprietary | Confidential Information


Benefits
★ Low code signature: A handful of clearly written,
commented reusable functions that anyone can
understand and a clearly commented Main.xaml
bringing structure to the process design
architecture

★ Separation of concerns: We keep framework


implementation separate from business logic
code, allowing developers and SMEs alike to focus
on building processes

★ Reusability: Works for any type of process,


Independent of Data sources (Queue-Items, local
excel files, Database data, API retrieved data),
Independent of process linearity

Globant Proprietary | Confidential Information


Benefits
★ Maintain, extend and upgrade: Easy to maintain,
thanks to code lightness and SOC. Extend to
achieve process behavior by editing 6 empty
workflows that connect to the Main.xaml in a
standard way. Upgrade or extend framework
independently of business code, by editing only
one file, the Main.xaml

★ Exception recovery and retry: If all recovery


options are exhausted, closing and restarting the
application environment while remembering data
is what humans do too. Top-level exception
recovery is managed by the framework layer with
Retry rules you can easily configure

★ Audit: Keep track of the robot's work, with as


much detail and privacy as you choose with the
new Workblock concept; Add business
information of your choosing to the published log

Globant Proprietary | Confidential Information

You might also like