DispatchTask_ProcessDocumentation

1. Project Details
The Project will be developed with UiPath Re-Framework and has separate workflows based on the requirements

● Main Workflow

● Login Module

● Search_Task

● Assigned_Task

● Dispatch_Task

● LogOut_Module

Input Path: TBD

Output Path: TBD

Main Workflow

The Main Workflow contains the State Machine flows with various states with the required condition in the transitions in
which all the workflows are to be invoked

▪ Initialization

▪ Get Transaction Data

▪ Process Transaction

▪ End Process

Login_Module(Library)

This workflow contains the activities of processing the login into the Web portal.

⮚ Credentials and URLs are stored in the orchestrator asset.

⮚ Access the Link and Log on to AAL portal using credentials.

Search-Task

This workflow contains the activities of processing of Read the csv file and Search Task inside the portal to find out the task is found or not
and Task is Assigned or not

⮚ Check the Task Id Number is available inside the portal.

⮚ If the Task Id number is available, then find out the task is assigned for the task Id

Assigned_task

This workflow contains the activities of processing the assign the task for not assigned task id number .
Dispatch_Task

This workflow contains the activities to dispatch the assign task to the team unit member.

LogOut_Module

This This workflow contains the activities to dispatch the assign task to the team unit member.

2. Library
A library in UiPath is a collection of activities that can be reused in other automation projects. Libraries are saved as .nupkg files
and can be installed as dependencies from the Package Manager.Libraries can be added as dependencies to automation processes.

In this project we have created the library for Login Module and Logout Module. For the purpose of reuse the Login and Logout
steps often in the project and for using in other projects.
3. Flow Diagram
4. The process can be started from
❖ UiPath

❖ Uipath Assistant and Orchestrator

5. Exception Handling
The types of exceptions identifiable in the automation process can be classified according to the table below.

Area Known Unknown/New

Business Previously encountered situation. A possible scenario is defined, and A situation never encountered before. It can be caused by external
clear actions and workarounds are provided for each case. factors.

5.1. Known Exception

The known exceptions in the process will be handled like

Exception # Exception Details The step where the exception is Parameters Action to be taken
encountered

1 Lack of any/No Input files First Step Data row count=0 Stop the process

5.2. Unknown Exceptions/New Exceptions

The Unknown exceptions can be added in the Development phase/ Testing Phase

Exception # Exception Details The step where the exception is Parameters Action to be taken
encountered

1 Login credentials Login step Credentials is wrong Stop the process

6. Error Mapping and Handling

The errors identified in the automation process can be classified according to the table below.

Area Known Unknown/New

Selector Previously encountered situation - action plan or workaround A situation never encountered before or may happen independently
available. of the applications used in the process.

CSV File Previously encountered situation - action plan or workaround This Will occurs based on the file availability and hyperlink.
available.

6.1. Known Error

The Known Error will be handled like

Error # Error Details The step where the error is Parameters Action to be taken
encountered
1 RPC Server unavailable Excel Steps - Kill the Process and Add a delay time.

2 Selector Any step - Make selectors more dynamic and use

a try-catch block

3 Application unresponsive / page not Any step No response / blank page Retry 2 times. Close application and run
loading the sequence again

6.2. Unknown Errors/New Errors

The Unknown Error will be handled in the development phase/ testing phase.

Error # Error Name The step where the error is Parameters Action to be taken
encountered

1 Authentication Failed or User is Blocked Login Steps Service unreachable/ Send Email
Authentication failed appear in Website

7. Application Details

# Application Name System Lang Login Model Interface Environment/Access Comments

Method

1 Excel ENG Desktop Desktop Excel 2016

2 AAL Web Web Chrome

3 Postgres DataBase Desktop Desktop Database Connection

8. Data Used in the Process

The table includes a comprehensive list of all the Variables and argument inside the workflow.

8.1 Workflow Name :

Initialization State :

S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 TransactionItem Queue Item Variable - This variable can be changed to

match the transaction type in the
process. For example, when
processing data from a
spreadsheet that is read into a
DataTable, this type can be
changed to DataRow.

2 SystemException Exception Variable - This variable is used during

transitions between states to
represent exceptions other than
business exceptions.

3 BusinessException Business Rule Exception Variable - This variable is used during

transitions between states and
represents a situation that does
not conform to the rules of the
process being automated.
4 TransactionNumber Int32 Variable - This variable is used for
Sequential counter of transaction
items.

5 Config Dictionary(x:String, x:Object) Variable - This variable is used for

Dictionary structure to store
configuration data of the process
(settings, constants and assets).

6 RetryNumber Int32 Variable - This variable is used to control

the number of attempts of
retrying the transaction
processing in case of system
exceptions.

7 TransactionField1 String Variable - Optionally used to include

additional information about the
transaction item.

8 TransactionField2 String Variable - Optionally used to include

additional information about the
transaction item.

9 TransactionID String Variable - Transaction ID used for

information and logging
purposes. Ideally, the ID should
be

unique for each transaction.

10 dt_TransactionData Datatable Variable - Used in case transactions are

stored in a DataTable, for
example, after being retrieved
from a spreadsheet.

11 ConsecutiveSystemExceptions Int32 Variable - Used to control the number of

consecutive system exceptions.

12 in_OrchestratorQueueName String Argument IN Allows the Orchestrator queue

name to be passed as an
argument, instead of only being
defined in the configuration file.

13 in_OrchestratorQueueFolder String Argument IN Allows the Orchestrator folder

name where the queue is
created to be passed as an
argument, instead of only being
defined in the configuration file.

14 DtOutput DataTable Argument IN/OUT This variable is used for Build the
table for store the output value

InitAllSettings :

S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 in_ConfigFile String Argument IN Path to the configuration file that

defines settings, constants and
assets.( Data\Config.xlsx)

2 in_ConfigSheets String Array Argument IN Names of the sheets

corresponding to settings and
constants in the configuration
file.({"Settings", "Constants"}).

3 out_Config Dictionary(x:String, x:Object) Argument OUT Dictionary structure to store

configuration data of the process
(settings, constants and assets).

4 dt_Assets DataTable Variable - This variable used to store the

asset data from config file.

5 Dt_SettingsAndConstants DataTable Variable - This variable used to store all the

Settings And Constants sheet
data from config file.
GetTransactionData :
S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 io_dt_TransactionData DataTable Argument IN This variable can be used in

case transactions are stored in a
DataTable (for example, after
being retrieved from a
spreadsheet).

2 in_TransactionNumber" Int32 Argument IN Sequential counter of transaction

items.

3 in_Config Dictionary(x:String, x:Object)) Argument IN Dictionary structure to store

configuration data of the process
(settings, constants and assets).

4 out_TransactionItem Queue Item Argument OUT Transaction item to be

processed.

5 out_TransactionField1 String Argument OUT Allow the optional addition of

information about the transaction
item.

6 out_TransactionField2 String Argument OUT Allow the optional addition of

information about the transaction
item.

7 out_TransactionID String Argument OUT Transaction ID used for

information and logging
purposes. Ideally, the ID should
be unique for each transaction.

Process Workflow:
S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 in_TransactionItem QueueItem Argument IN This variable can be used to

Transaction item to be
processed.

2 in_Config Dictionary(x:String, x:Object)) Argument IN Dictionary structure to store

configuration data of the process
(settings, constants and assets).

3 StrGetSelect String Variable - This variable use to get the

“GetSelectedButton” status from
Search Task workflow.

4 StrEditSelect String Variable - This variable use to get the

“EditSelectedButton” status from
Search Task workflow.

Search Task :

S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 TransactionItem QueueItem Argument IN/OUT This variable can be used to

Transaction item to be
processed.

2 Config Dictionary(x:String, x:Object)) Argument IN/OUT Dictionary structure to store

configuration data of the process
(settings, constants and assets).

3 DtOutput DataTable Argument IN/OUT This variable used to store Input

data and it status.
4 StrGetSelect String Argument IN/OUT This variable use to get the
“GetSelectedButton” status and
pass the status outside from the
Search Task workflow.

5 StrEditSelect String Argument IN/OUT This variable use to get the

“EditSelectedButton” status and
pass the status outside from the
Search Task workflow.

6 BoolTaskInbox Boolean Variable - This variable used to check the

“TaskInbox” page is exist or not.

7 BoolTaskNotFound Boolean Variable - This variable used to check the

Task is Found or not for the
taskId Number.

8 DtStatusCheck Datatable Variable - This variable used to store the

extracted data which for TaskId.

9 StrStatus String Variable - This variable used to store the

status for the TaskId number.

Assigned task

S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 BoolDispatchDisplay Boolean Variable - This variable can be used to

Check the Dispatch task page is
appear or not.

2 StrGetSelect String Argument IN This variable use to get the

“GetSelectedButton” status from
the Search Task workflow.

3 StrEditSelect String Argument IN This variable use to get the

“EditSelectedButton” status from
the Search Task workflow.

4 DtOutput DataTable Argument IN/OUT This variable used to store Input

data and it status.

DisPatch_task

S.No Variable Name Data Type Variable/Argument ArgumentDirection Comments

1 BoolDispatchDisplay Boolean Variable - This variable can be used to

Check the Dispatch task page is
appear or not.

2 BoolContinue Boolean Variable - This variable can be used to

Check the Continue button is
populated in DispatchDisplay
page.

3 BoolAssignPage Boolean Variable - This variable can be used to

Check the Assign task button is
exist or not.

4 In_TransactionItem QueueItem Argument IN This variable can be used to

Transaction item to be
processed.

5 DtOutput DataTable Argument IN This datatable variable used to

store Input data and it status.

6 In_Config Dictionary(x:String, x:Object)) Argument IN This datatable variable used to

Get the Google sheet url which is
store in the config file.