Robotic Process Automation

RPA Challenge Bot

Process Definition Document (PDD)
UiPath

1
RPA Challenge Bot - UiPath – Process Definition Document
Disclaimer

The information contained in this document is confidential and is provided to the reader only for its
personal use. All information contained in this document is provided to the reader “as is” and is subject
to various risks and uncertainties that could cause actual results to differ materially from expectations.
UiPath disclaims any liability for any use or reliance of the reader upon such information. Readers are
cautioned not to place undue reliance on this information, which speak only as of their dates. UiPath
undertakes no obligation to publicly update or revise any of this information.

2
RPA Challenge Bot - UiPath – Process Definition Document
 Document History

Date Version Role Name Organizatio Function Comments

n
08.07.2019 1.0 Author Tudor Professional RPA Creation
Bestea Services Developer

3
RPA Challenge Bot - UiPath – Process Definition Document
Contents

1. Introduction 5
1.1 Purpose of the document 5
1.2 Objectives 5
1.3 Process key contacts 5
1.4 Minimum Pre-requisites for automation 6
2. As IS process description 6
2.1 Process Overview 6
2.2 Applications used in the process 6
2.3 As IS Detailed Process map 7
2.4 Detailed Process Steps 7
2.5 Exceptions Handling 8
3. Document Approval Flow 9

4
RPA Challenge Bot - UiPath – Process Definition Document
 1. Introduction

1.1 Purpose of the document

The Process Definition Document outlines the business process chosen for automation using UiPath
Robotic Process Automation (RPA) technology.

The document describes the sequence of steps performed as part of the business process, the
conditions and rules of the process prior to automation and how they are envisioned to work after
automating it, partly or entirely. This specifications document serves as a base for developers,
providing them the details required for applying robotic automation to the selected business process.

1.2 Objectives

The process that has been selected for RPA is part of the larger project initiative conducted within
UiPath organization inside Community department.

The objective of this process automation is linked to the project business case and is mainly intended
to:

 Deliver faster processing

 Reduce the duration of time-consuming activities
 Leverage automation to improve the overall performance and reliability of the department.

1.3 Process key contacts

The design document includes a brief, but comprehensive set of requirements for the process. Its
structure is based on the input provided by the Subject Matter Expert (SME) in the process.

For escalation points, please review the table below:

Role Name Contact details Notes

(email, phone number)
Process SME Tudor Bestea tudor.bestea@uipath.com Point of contact for
questions related to
business exceptions
and passwords
Reviewer / Owner Ninett Panfir ninett.panfir@uipath.com Point of Contact for
process exceptions
Approver for Paul Punguta Paul.punguta@uipath.com Escalations, Delays
production

5
RPA Challenge Bot - UiPath – Process Definition Document
 1.4 Minimum Pre-requisites for automation

1. Filled in Process Definition Document

2. Credentials (user ID and password) required to logon to machines and applications
3. Test Data to support development.

2. As IS process description

2.1 Process Overview

General information about the process selected for RPA prior to automation.

# Item Description
1 Process full name RPA Challenge Bot
2 Process Area Data Entry
3 Department Community
4 Process short description Fill in browser forms which change position on the screen
(operation, activity,
outcome)
5 Role required for N/A
performing the process
6 Process schedule and Daily, Monday to Friday, 11 AM
frequency
7 # of items processes /day ~100
8 Average handling time <1 Sec
per item
9 Peak period (s) No peak period
10 Total # of FTEs supporting 1
this activity
11 Level of exception rate ~1% exceptions (Page input fields may not work sometimes)
12 Input data Excel with data from website
13 Output data A text file with the success rate
14 Dependencies N/A
(upstream, downstream)

2.2 Applications used in the process

The table includes a comprehensive list all the applications that are used as part of the process
6
RPA Challenge Bot - UiPath – Process Definition Document
automated, at various steps in the flow.
# Application System Login Interface Environment/ Comments
name & version Languag Module Access method (Include URLs)
e
1 Default EN n/a Client Local desktop
Browser
2 Microsoft EN SSO Client Local desktop
Excel

2.3 As IS Detailed Process map

This chapter depicts the AS IS business process in detail to enable the developer to build the
automated process.

Ste Short Description of Key Process Steps

p
1 Open the RPA Challenge website
2 Download the Excel file with data
3 For each row in the Excel, input the corresponding data
3.1 Submit the data
4 Save the success message in a text file

2.4 Detailed Process Steps

# Step action description Screenshot Expected result Remarks

7
RPA Challenge Bot - UiPath – Process Definition Document
1 Open Website is
http://www.rpachalle opened
nge.com/

2 Click the download Excel is

button downloaded

3 For each row in the

excel, perform the
following step
3 Match each field from Data is entered
. the Excel with their
1 respective field from
the website

3 Submit the current Data is submitted

. data and a new empty
2 input page is
shown

4 Get the success rate The challenge

and write it in a text finishes and the
file process ends

2.5 Exceptions Handling

The Business Process Owner and Business Analysts are expected to document below all the business
exceptions identified in the automation process. These can be classified as:

# Exception name Step where Parameters Action to be taken

exception is
encountered
8
RPA Challenge Bot - UiPath – Process Definition Document
1.0 Application Any No response / No error handling is needed
unresponsive / page blank page for now
not loading

3. Document Approval Flow

Version Flow Role Name Organization Approval

(Dept.) Date:
1.0 Document Technical Name Surname
prepared by Solution
Architect
1.0 Document Process Name Surname
Approved by: Owner
1.0 Document Operations Name Surname
Approved by:
1.0 Document Compliance Name Surname
Approved by:
1.0 Document RPA Name Surname
Approved by: Architect/
Developer

9
RPA Challenge Bot - UiPath – Process Definition Document