The document outlines an enhanced request-response framework (Enhanced REFramework) that improves upon a basic REFramework. The Enhanced REFramework allows for complex scenarios involving multiple subprocesses, with exception handling, retry mechanisms, and audit logging at each subprocess level. It combines dispatcher and performer workflows into a single framework and introduces the concept of "workblocks" to help with effective logging and exception handling across parent and child processes. Key features of the Enhanced REFramework include init state retries, configurable error handling, flexible configuration options, and support for migrating from a basic REFramework.

1. Enhanced
REFramework

2. 2
1. Framework Definition
2. REFramework Overview
3. Where it lacked
4. Enhanced REFramework Overview
5. REFramework Vs Enhanced REFramework
6. When to use Enhanced REFramework?
7. Layers of Enhanced REFramework
8. Transaction Flow in Enhanced REFramework
9. Concept of Workblock
10.Features over REFramework
11.Best Practices to be followed
12.Use Case Demo
Agenda Slide

3. 3
As per wiki –
• In computer programming, software framework is an abstraction in which software,
providing generic functionality, can be selectively changed by additional user-
written code, thus providing application-specific software.
• It provides a standard way to build and deploy applications and is a universal,
reusable software environment that provides particular functionality as part of a
larger software platform to facilitate the development of software applications,
products and solutions.
• A software framework has the following key features –
• Reusability
• Extensibility
• Structure
Framework - Definition

4. 4
• UiPath Studio template built using State
Machines
• Includes -
• Robust exception handling/logging
mechanism
• Contains States/Containers for –
• Initializing all applications
• Fetching Input transaction
• Processing transaction
• Ending the process
REFramework – Overview

5. 5
Where it lacked?
• Init State Retry
• Dispatcher & Performer
• When there are multiple line items to be processed under a single transaction item
• Exception Handling of individual Sub-processes (if any)
• Retry mechanism in case of exception at sub-process level
• Audit logging at sub-process level

6. 6
A Quiz to test your skills!!
1. Go to https://www.menti.com/
2. Type the code : 4766923
OR
Scan the QR code below :

7. 7
Enhanced REFramework - Overview
• Top level view of Enhanced
REFramework.
• Invokes multiple child REFrameworks
inside a parent REFramework instead of
simple workflows.
• Based on State Machines

8. 8
REFramework Vs Enhanced REFramework

9. 9
When to use Enhanced REFramework?
• Complex scenarios involving multiple sub-
processes
• Exception Handling/Retry Mechanism/Audit
tracking is required for each sub-process level
• Example -
• Read attachments from Email
• Classify Email based on attachments
(Invoice/PO) –
• Invoice Posting in SAP
• PO Data Entry in Oracle

10. 10
Layers of Enhanced REFramework
Data Layer
Config file and Input data files are placed here for the Framework Layer to
read/write data.
Framework Layer
• Config file settings are read from Config
• Checks are performed to ensure all the pre-requisites for starting the
process are in place
Process Layer
• All application or process specific workflows should be added here
• Clean and prep activities, initialization of application and business logic
code is implemented using reusable workflows
Services Layer
• Contains the child REFrameworks or Tasks –
• FirstRun – Invoked only once at Init state (Dispatcher Logic)
• GetData – Can be invoked once at program start up OR once for
each unique transaction. Used to get data from an Application,
website or Resource that might fail.
• Task1/Task2 – Process specific tasks. More tasks can be added
as per requirement.
• Each of the tasks can be enabled/disabled based on Task setting in
Config file

11. 11
Concept of Work block
• Entire Framework is a work block – a parent
work block with many child work blocks.
• Figure on the right shows a work block
template inside Workblock Snippet folder.
• For effective logging, logs are displayed during
the startup and successful completion of the
work block.
• Exceptions are re-thrown to the parent work
block (if any).

12. 12
Transaction Flow in Enhanced REFramework
Io_TransactionData : List < Data row >
Success
Business Exception
Success
Business Exception
Retry in case of System Exception
Retry in case of System Exception
Dispatcher Logic
FirstRun Task
Retry in case of System Exception
Get data from any
application
GetData Task
Task1
Task2
Io_TransactionData : List < Data row >
In_TransactionItem
Success
Business Exception
Io_TransactionData : List < Data row >
Io_TransactionData : List < Data row >
In_TransactionItem
In_TransactionItem

13. 13
Features over REFramework
• Init State Retry
• Abort on max consecutive errors for each of
the states – Init and ProcessTransaction.
• Workblock concept helps in effective logging
and exception handling.
• More options to read the config settings from a
json file and also validate the json file.
• Combines Dispatcher, Performer workflows
into a single framework
• Introduction of fixed “system reserved”
variables.
• Allows easy migration/integration from
REFramework
• Catches Exception at End Process State of
each tasks under Services Layer

14. 14
Best Practices to be followed
• Workblock template should be used for building any standalone workflows.
• Login workflows for Task1 specific applications should be kept inside
Task1ProcessLayerInitAllApplications.xaml.
• Assets/Credentials relevant for a particular task should be stored inside
DataConfig file inside Services Layer of that Task folder.
• All standalone workflows for a particular process/application should be
maintained inside Process Layer of main workblock.
• Always invoke Main.xaml workflow to invoke the tasks from the Services Layer.

15. Use Case Demo

16. 16
Use Case Steps
 Login into the website (http://challenge.rpabotsworld.com/)
 Check the Email of the Customer.
 Navigate to Customers List.
 For the Customer Name in Invoice Data, lookup Customers Email from Customer Detail sheet
 Search Customer Email id in Application
 If Customer Email NOT present –
o Create a user with the details from Customer Details excel.
 Create an Invoice for that customer based on data supplied in excel.
 Attached Excel Contains Product Description, Price, Quantity and Status. Your workflow should Calculate Tax
(18% GST), Billing Date Should be System Date and Due Date should be T + 45 Days
 Extract Invoice Number, Total Amount
 Generate an output report and email the same at the end of process

17. Q&A Session