AICTE ROBOTIC PROCESS AUTOMATION

WITH BLUE PRISM

Internship-I report submitted in partial fulfilment requirements for the award of degree of

BACHELOR OF TECHNOLOGY

IN

COMPUTER SCIENCE AND ENGINEERING

ARTIFICIAL INTELIGENCE AND MACHINE LEARNING

By

J. BHAVYA SRI (20131A4223)

N.V.D. BHAVYA SRI (20131A4237)
SHARATH (21135A4201)
NUZHATH TAHSEEN (21135A4204)

Under the esteemed guidance

Name of course Coordinator Name of Course Mentor

P. POOJA RATNAM P. POOJA RATNAM
(Assistant Professor) (Assistant Professor)

Department of Computer Science and Engineering

GAYATRI VIDYA PARISHAD COLLEGE OF ENGINEERING (AUTONOMOUS)

(Affiliated to Andhra University, Visakapatnam)

VISAKHAPATNAM
2022-2023

Gayatri Vidya Parishad College of Engineering (Autonomous)

Visakhapatnam
 CERTIFICATE
This report on
“AICTE ROBOTIC PROCESS AUTOMATION WITH BLUE PRISM”
Is a Bonified record of the Internship work submitted
By
J. BHAVYA SRI (20131A4223)
N.V.D. BHAVYA SRI (20131A4237)
SHARATH (21135A4201)
NUZHATH TAHSEEN (21135A4204)

In their V semester in partial fulfilment of requirements for the Award of Degree of

Bachelor of Technology in
Computer Science and Engineering Artificial Intelligence and Machine learning
During the academic year 2011-2023

P.POOJA RATNAM Dr. D.N.D. HARINI

Assistant ProfessorHead of the Department
Dept. of Computer Science and Engineering Dept. of Computer Science and Engineering

Internship Mentor
P. POOJA RATNAM
Associate Professor
Certificates
 ACKNOWLEDGEMENT

We would like to express our deep sense of gratitude to our esteemed institute

Gaytri Vidya Parishad College of Engineering (Autonomous), which has provided us

an opportunity to full fill our cherisher desire.

We thank our Course Coordinator and our internship mentor, Dr. P.POOJA RATNAM,
Assiatant Professor, Department of Computer Science and Engineering, and
Dr.Uma Devi (Head of Aritifical Inteliigence and Machine Learning)for the kind
suggestions and guidance for the successful completion of our internship.

We are hightly indebted to Dr. D.N.D. HARINI, Associate Professor and Head of the
Department of Computer Science and Engineering, Gayatri Vidya Parishad College
Of Engineering (Autonomous), for giving us an oppurtunity to do the internship in
college.

We express our sincere thanks to our Principal Dr. A.B. KOTESWARA RAO, Gayatri
Vidya Parishad College Of Engineering (Autonomous) for his encouragement to us
during this project, giving us a chance to explore and learn new technologies in the form
of mini project.

We express our deepest thanks to the AICTE I And EDUSKILLs to offer us this
intership.

(YOU Need To Acknowledge AICTE And Eduskills Also)

Finally, we are indebted to the teching and non-teaching staff of the Computer
Science and Engineering Department for all their support in completion of our
project.
J. BHAVYA SRI (20131A4223)

N.V.D. BHAVYA SRI (20131A4237)

SHARATH (21135A4201)

NUZHATH TAHSEEN (21135A4204)

 ABSTRACT

Blue Prism is an RPA Tool which holds the capability of virtual workforce powered by software robots.
This helps the enterprises to automate the business operations in an agile and cost-effective
manner. The tool is based on Java Programming Language and offers a visual designer with drag and drop
functionalities.
 INDEX

Name of the Course Modules Page No

Course -1 Blue Prism Foundation Training

1.1. Introduction

1.2. Process Studio

1.3. Introduction to process flow

1.4. Introduction to inputs and outputs

1.5. Business Objects

1.6. Object Studio

1.7. Exception Management Overview

1.8. Exception Management

1.9. Work Queues

1.10. Additional Features

1.11. Consolidation Excercise

1.12. Training next steps Guide

Course- -2 Blue Prism Associate Developer (EN-2021)

Module -1 Blue Prism Awareness

2.1.1. New Fronties for Robotic Process Automation

2.1.2. Blue Prism- The Customer Perspective

2.1.3. What is RPA?

2.1.4. The Digital Workforce

2.1.5. The Blue Prism Vision

 2.1.6. Watch it work

2.1.7. How To Automate

2.1.8. How To Monitor

Module-2 Blue Prism Foundation Training

Module-3 Blue Prism Process Templates

2.3.1. Blue Prism Templates

2.3.2. Blue Prism Process Templates

Module-4 Blue Prism Credentials and Credentials

Manager

2.4.1. Blue prism Credentials and Credential

Manager SCORM

Module-5 Blue Prism Advanced Data Items

2.5.1. Blue Prism Advanced Data Items SCORM

Module-6 Blue Prism Advanced Attribute Matching

2.6.1 Blue Prism Advanced Attribute Matching

SCORM

Module-7 Blue Prism Associate Developer Next Steps

2.7.1. Blue Prism Associate Developer Next Steps

Module-8 Blue Prism Associate Developer Cerificate

Readiness - webinar

2.8.1. Webinar- Preparation for Associate Developer

Certification

2.8.2. Reference Material

 COURSE-1
Section-1

Installation
Download the provided blue prism by logging into blue prism website

Figure 1.1
After downloading we get a license for our mail and also download centrix datasolution.csv
file provided by then now install blue prism accept all the default settings

Figure1.2
Set your password and log into again now

Figure1.3
 Section-2
Creating a new process
1.Right click on the process heading in the process studio area and give some
description about your project then double click on process name.
2.After opening the process we have some important terms at left side of the
panel.

Figure2.1

Figure 2.2

Calculating two variables sum:

1.Create a three variables and then click on variable1 and in properties

window give input and input type as integer and do it same for variable2.
2.Drag calculate element and in properties window add the variables available
i.e, variable1 and variable2
3.And store into variable3 as shown
 Figure 2.3

4.Now connect start ,calculate ,end stages using pointer

5.Run the process using icon present in top panel and check the variable3 that is
sum of variable 1and variable 2 is stored in variable3 as an output.
Process is just look like this

Figure 2.4

While running process we get some errors which can be rectified .errors can occurs
sometimes while link is missing or syntax was wrong.
For example delete the link between calculate and end stage ,also delete the bracket
in syntax of calaculation box in properties and run the process.at top next to the
run button there is validation button .
Click on validation button we get the errors occurred in the process ,u can also click
on the button at the bottom of the page and understand how to rectify an error.
 Section-3
Circular paths
1.Create a new process name circular paths.
2.Open process and create two data items and in property panel one as input
an integer and other is limit value an integer value
3.Add decision stage and name “limit exceed” ,in property panel give a
condition( input>limit) for decision end for “yes” link to the end stage and
for “no” add calculate element and in property box add increment and store
into same variable.

Figure 3.1
And we can control process running
We can use run.pause.resume and also control speeding of process

Figure 3.2
We can skip the stages in process by pausing and click on stage and select run
the next stage.use breakpoint for making the process to run up to selected
stage and then pause.
Using other pages as references in process
We can also add pages into main process such that whatever process in page1
contains also run and after ending of page1 again redirects to main process
and continues until the it reaches end stage.

Figure 3.3

Figure 3.4
 Section-4
Introduction to inputs and outputs
1.In main page add data item named “number of loops” in properties window
uncheck “hide from other process”.
2.Drag page element and name “page1” in page1 properties add number of
loops and store in number of loops data item and in page 1 at start stage take
number of loops as input
3.In page 1 ,number of loops variable is created so then create another data
item use for counting until it reaches the number of loops value and follow
by adding decision and calculate stages in page 1 .
4.Add another page2 and create date dataitem in main page and give it as
input to the page2 start stage and then add calculate sage in page2 and
change the date according to the options and send the through end stage as
output to the main page
5.Store this date data item and run the process
Figure 4.1 Figure 4.2

Figure 4.3 Figure 4.4

Figure 4.5
Figure 4.6
 We can also publish our process

Figure 4.7

Section-5
Business object
Here you go with an interesting part!!
You can access some application through blue prism
Add new process and drag action element and select “Notepad”and type “Launch”
and again add and again add action ,select “Notepad” and type “Write” Click on
write action and in input give the data item with text as “Hello World” Now add
action ,Notepad and type “close”.

Figure 5.1 Figure 5.2

Section-6
Object Studio
 It is the design canvas where the Blue Prism “robot” is “trained” to perform the basic
system tasks that form the building blocks of processes.
 The target desktop application is rapidly modelled and verified through the presentation
layer, which provides a library of elements with which to work
Business Objects
 A visual business object is one which is designed from within object studio. In this
case Blue Prism takes care of mapping the interfaces and no configuration is necessary.
 Such business objects appear automatically in System Manager, and in Action Stage
Properties forms.

Application Modeller
The Application
Modeller allows you to run
Blue Prism and your target
application side by side,
and invites you to teach
Object Studio about the
features of your target
application, by pointing and
clicking.
Figure 6.1

Application Modeller Attributes

In this its explains how
Application Modeller can be
used to 'Spy' unique
Attributes for an Element, so
that a Business Object can
identify the Element when it
needs to perform a task.

Figure 6.2

Navigate Stage
• Navigate Stages enable Actions to be used to Launch and Close an application.
• It is best practice to provide 'Preconditions' and'Postconditions' for an Action:
• Preconditions should describe the state of the application prior to running the Action.
• Postconditions should describe the state of the application once the Action has run (e.g.
the application Log In window is open on screen).
• Action Pages must be published before they become visible in the Actions menu, in the
Navigate Stage properties window.

Figure 6.3
Launching or opening the centrix solution using navigation tool.

Figure 6.4
Closing the centrix solution using navigation tool.

Wait Stage
• The use of a Wait Stage, enables Business Objects to pause and wait for an application to
load or a condition to be met, before continuing.
• Wait conditions can be applied to Wait Stages, to evaluate whether a condition exists
within a specified period of time
.• It is also best practice to include a conditional with a application. Wait Stage, following

Figure 6.5
every interaction with application that causes a change in state.
Throttles and Unconditional Waits Timeouts
• Wait Stages can be used without any conditions, with the Timeout serving as a pause to
delay the flow through the Diagram - this is known as 'Throttling'. This allows some extra
time to accommodate the variable performance speed of an application.
• A Global Data Item can be used to store the Timeout duration for all of the Action
Pages within a Business Object, which can make it easier to reconfigure Wait
times in response to application performance.
• It is best practice to create a dedicated Global Throttle Data Item.

The global
data item
is set.

Figure 6.5

Unique Attributes
Identify Element within application window that has identical fingerprint to second
 Element in same window . Use ‘Ordinal Attribute to distinguish unique Attributes for two
Elements

Figure 6.6

Write Stage
• The Write Stage is used to transmit values from a Blue Prism Process, to an external
application.
• These values may be the result of an Expression or may be a value stored within a Data
Item.
• Before the Write Stage can transmit a value to an application, the Element field must
first be defined in Application Modeller. Write Stage. Object Diagram with Write Stage
and Data Items. Data Item providing value for Write Stage. Write Stage properties
window.

Figure 6.7

Unique Attributes (Part 2)

Locate Attribute producing error and remove it from Atributes list
Modify Write Stage to input the password into application.

Figure 6.8 Figure 6.9

Press
• A Navigate Stage can be used to
press a button within an
application window.
Before a button can be pressed, the
button must first be defined in
Application Modeller.
The Navigate Stage can then be set
up to press the button, via the
Actions area of the Navigate
Stage properties window.
Figure 6.10
Attach and Detach
• It is not always necessary for Blue Prism to open an application that it needs to interact with,
this would be the case if an application had already been opened manually or as part of a system
start-up, before Blue Prism
attempted to interact with it.
• If an application is already open
and running on the screen, Blue
Prism can use a Navigate Stage to
'Attach' to the application window.
• Navigate Stages can also be used to
'Detach' from an open and running
application.
Figure 6.11

Read Stage
• The Read Stage is another Stage unique
to Object Studio and is used to read
information
from an application, by taking data from an Element within an application and storing it within a
Data Item.
• To prevent errors, a Read Stage is usually combined with a Decision Stage to determine whether
the application is already attached and whether an Attach is necessary.
Figure 6.12

Actions
• The functionality of Actions can only be utilized once the Business Object has been set up to
interact with a Process. Which can be achieved via the inclusion of Action Stages within the
Process Diagram.
• Action Pages need to be published before they become visible within the Action Stage
properties menu.
• Once an Action has been published, the Action icon will be visible next to the tab containing
the Business Object Action name.

Figure 6.13

Figure 6.14

Action Inputs and Outputs

• Input and Output Parameters are used to transmit values between the Process Diagram and the
Business Object Action.
• Business Objects should not store any values. Any value that is needed to input into the
Elements of an application, should instead be passed down from a Process via an Input
Parameter. The Business Object should only retain the information passed down to it, for as
long as it takes to complete the interaction.
• Configuring a Business Object in this way, provides it with reusable functionalityenabling it to
perform its interaction, regardless of the information it uses to do so.
• For example, different account numbers can be transmitted from the Process to the Business
Object via an Input Parameter, which can be used to login to different accounts via the same
application.

Figure 6.15 Figure 6.16

Figure 6.17 Figure 6.18

Multiple Business Objects

• Business Objects should be kept small and simple and be designed to perform a
specific function or a small group of similar functions.
• It is therefore best practice, to build a separate Business Object for each
window within an application - this approach is known as 'Multiple Business-
Objects' and makes Business Objects much easier to manage and maintain,
especially in a shared work environment.

Figure 6.19

Section-7

Exception Management Overview

 • A Process or a Business Object can be configured so that it is capable of
capturing and handling errors - which are known as 'Exceptions'
• The two main types of Exceptions are 'System Exceptions' - application
based problems and 'Business Exceptions' - rules based problems.
• Digital Workers can pass Exceptions out for manual review and continue
processing the workload, without interruption.
• An escape route for Exception Items must be considered. All items marked
as an Exception must be reviewed by a person, before they can be
completed e.g: -An automated email that sends the details of the Exception
Item to a specified inbox, as soon as it has been processed. -Waiting until
the entire Work Queue has been worked, before collating all of the
Exception Items into a specified file, saved to a drive shared by the manual
team.

Figure 7.1

Section-8
Exception handling
Is defined by the management of exceptions in unassisted automation. It ensures that
problems can be automatically resolved if possible, or easily identifiable and repairable by
system administrators or passed for human completion where appropriate.
 Recovery Mode
• If left unhandled, an Exception will travel up through the Process to the Main Page and cause
the Session to terminate - this is known as 'Exception Bubbling?
The first step to managing Exception Bubbling and enabling the Session to continue in the event
of an Exception, is to build a 'Recovery Mode' into the Process Solution.
The key elements of which are 'Recover' and "Resume, which work together to salvage and move
on from an Exception.

Figure 8.1
Throwing Exceptions and Exception Properties
• If Exception Handling has not been built into a Process Solution, then any Exceptions that are
the result of the way a Process is configured, or of the performance of an application that is
used by a Process, will be categorized as 'Internal Exceptions'.
• When an Internal Exception is identified, an 'Internal Error' message window will appear that
provides detail of the Exception. Though the information contained here, is not always
presented in an intelligible way. Making it difficult to identify the cause of the error.
• To mitigate this, Exception Stages can be included throughout your Process Solution, which
provide the capability to embed more concise and meaningful information about an Exception.
This information is then 'Thrown' up through the Process and once handled, can be accessed via
the Session Log.

Exception Bubbling
• Exceptions can occur at any point throughout a Process Solution, wherever an
Exception occurs, it will always move up towards the Main Page of the Process to
the highest layer of the Process Solution
• An Exception will continue to Bubble up from an Action in a Business Object and
then through the hierarchy of the Pages within the calling Process, until it reaches
a Page that contains Recovery logic. At which point the Exception will be handled.
 • If the Main Page of the highest layer of the Process Solution does not contain logic
to handle the error, then an error message window will appear when running in
Process Studio. If the same occurs when running a Process in Control Room, the
Process will Terminate

Figure 8.2

Preserving the Current Exception

• Each of the Exception Stages used within the main flow of a Diagram, will containa unique
pairing of Exception Type and Exception Detail information. To make the source of the error
easy to identify.
• Exception Stages within Recovery Mode should therefore be configured to preserve the
information that is embedded within the Exceptions that Bubble up to them, to ensure that an
accurate account of the error is retained for the Session Log. This can be achieved by
checking the 'Preserve the type and detail of the current exception' box, in the Exception
Stage Properties.
• The 'Preserve' box should not be checked for Exception Stages that are used within the main
flow of a Diagram. As doing
so, will generate an error. This
is because Exception Stages
outside of Recovery Mode are
always new Exceptions,
meaning there would be no
information to preserve.

Figure 8.3

Blocks
• A greater degree of control can be added to Exception Handling, via the use of 'Exception
Blocks'. Which are used to isolate the area of a Process or Object Diagram, that a Recover
Stage is responsible for Without a Block, a Recover Stage will attract any Exception that
arises from any Stage on that Page (unless the Stage is in Recovery Mode between Recover
Resume).
A Block is a means of dividing a Page into separate Exception Areas, each with its own
Recover Stage and Exception Handling logic. Blocks are beneficial, as they enable the use
of multiple Recovery logic on the same Page.
Which can each be configured differently, to deal with Exceptions in different ways. When
using Blocks to organize Exception Handling logic, it's important to ensure that only one
Recover Stage is used within a Block, that Blocks do not to overlap and that Blocks are not
Nested inside one another

Fi
gure
8.4

Section-9
Work Queue
It is essentially a list of Items, which is populated and then worked by a Process.
This list can then be configured, to enable a Process to manage its own workload.
Should a Process encounter a problem whilst working an Item within a Queue, then
this Item can be tagged with information about the problem, which is then stored in the
Work Queue ready to assist with a manual review. Multiple Digital Workers can request
Items from the same Work Queue at the same time, with each receiving different items
from the Work Queue to process.
Working Items
• Blue Prism comes with some Business Objects, that are pre-installed within the software.
These 'Internal Business Objects' are not diagrams and cannot be viewed or changed -only
used in the Process through an Action Stage
. • An example of this is the Internal Business Object - Work Queues Business Object -
which serves to provide a connection between a Process and a Work Queue. Enabling the
Process to store data extracted from external sources within a Work Queue, to be managed
and worked within Blue Prism.
 • From within Control Room, Work Queues use different icons to communicate the state of
each Item within the Queue: An unworked or 'pending' item is marked with three blue dots.
An Item that is currently being worked by a Process is marked with a padlock. An Item that
has been worked and completed successfully, is marked with a green check. An Item that
has encountered an error is an Exception and is marked with a purple flag.

Figure 9.1 Figure 9.2

Queue Items
• A Work Queue is populated with Items through a Blue Prism Process, ready to be
worked by the same process or by other Processes.
• To ensure a Process is able to work all of the Items within a Queue, the Process must
include a Circular Path to return the flow back up to the Get Next Item Action Stage.

• Once all of the Items have been worked and marked as either 'Completed' or as
'Exception', and
once the Get
Next Item Action
Stage returns an
empty Item ID,
then the Process
will flow
towards the

Figure 9.3
Work Queue Configuration
• Work Queues are created and configured in the Workflow Area of System Manager. This
is where Work Queues can be provided with a Name and a key Name. • The Key Name
directly correlates to a column name in the Collection Stage, that is used within a Process
to add new Items to a Work Queue. The column value for each new Item will appear in
the Item Key column, in the Queue Management Area of Control Room.
 • From the Workflow Area, it is also possible To check the status of a Work Queue. - To
set the number of Retry Attempts for Items within the Work Queue. To find references to
the Process
interacting with a
particular Work
Queue.
• The Encrypted
option is available
to ensure any
sensitive data held
within the Work
Queue, is also
encrypted within
the Blue Prism
database Figure 9.4

Figure 9.5

Deferring Items
• New Items can be deferred to control the day and time on which they are worked.
• If a deferral date is specified when the items are created, then the Work Queue will
hold on to the Items until that date - effectively freezing them. So, when a Process
that is working a Work Queue fails to retrieve any more Items, it does not
necessarily mean that there are no unworked items in the queue as it could be the
case, that there are deferred Items that are being held until a specified date.
• Without the requirement for the Item to be assigned as either 'Complete' or as
'Exception'. This feature is useful, for part-working an Item and then freezing it for
later - for example, if a
Process is only able to
complete half of its
work on one day, then it
can resume the other
half on the next day.
Figure 9.6
 Exception Item Retries
• While an Item is being worked, Exception Retries can occur within a Process or a
Business Object, using retry logic within Recovery Mode..
• A Blue Prism Work Queue can also be set up to enable Exception Items to be
retried, meaning the whole Item is reworked by the Process as if it were a new
pending Item. Attempts only apply to Exceptions - Items marked as 'Complete'
cannot be reworked.
• The Max Attempts field in the Work Queue Configuration section of System
Manager, is set to 1 by default but this can be set to a higher value, if necessary.
When Max Attempts is greater than 1, the Work Queue will revive any Exception
Items, by creating a clone of the Item and injecting it into the queue, at the same
position as the original.

Figure 9.7 Figure 9.8

SECTION-10

Additional Features
This provides a more in depth look at some key aspects of blueprism to refine our
skills and ability
Now we will know how to import and export process Business Object and entire
blue prism solutions through blue prism release manager.
Release Manager
• An individual Process or Business Object can be exported from Blue Prism as an
XML file and these exported files can be imported back into Blue Prism. This can
be useful for backing up, sharing and moving singular components of a Blue Prism
Solution between databases.
• A Blue Prism Solution is a compilation of interconnected Processes, Business
Objects and Work Queues and as a result, should always be migrated as a
'Package' or 'Release!
• Blue Prism Release Manager enables users to compile all of the components of a
Blue Prism Solution into a Package. Including not only Processes, Business
Objects and Work Queues, but also Schedules, Calendars, Tiles and Dashboards.
• A Release is a snapshot of the state of each of the components within a Package at
a particular moment in time. At various stages during the development cycle of a
Blue Prism Solution, Releases will be exported and imported across databases.

Figure10.1 Figure10.2

Figure10.3
Figure10.4

COURSE-2
Module-1 Blue Prism Awareness
Explain what RPA means and understand the need for Intelligent Automation
Describe Blue Prism Digital Workforce and its capabilities
Explain the evolution and vision of Blue Prism
Summarize how Blue Prism can automate and monitor business processes
Module-2 Blue Prism Foundation Training
This module is the 1st part of the course that has been explained in detail.
Module-3 Blue Prism Process Templates
This module will introduce the concept of Blue Prism Process Templates, how to use these
templates, and why it is important to use these templates when starting to build a new
automated Process in Blue Prism.
1.Process Templates : Introduction , Prerequisites ,Availability , Installing
 2.Process Template 1 : Overview ,Exception Handling ,Template Pages ,Training Exercise
3.Process Template 2 Overview ,How to use Process Template 2 ,Generic Main ,Features
Example Main Pages
Process Templates
Blue Prism Process templates are provided in the form of a standard Blue Prism xml file,
which can be imported into your new environment. Blue Prism templates have been built
inline with Blue Prism development best practices. Templates are intended as a base
framework for starting a new processes, the idea being that ‘save as’ is used to make a
copy of a diagram to work on. Using a template as the basis of building a new process has
the following benefits:
• Decrease Process development time
• Provide consistency across all Processes, allowing easier understanding and support
• Assist developers in keeping to best practice and to work within the Development
Methodology of an organization
• As process templates are provided through standard Blue Prism Process xml, the template
file should be imported into your environment using the standard File -> Import.
You only need to import once and use the template as many times as you was by save as.
.Process Template 1
Process Template 1 provides a solid base framework for building a basic Blue Prism
Process, which:
• Loads work from a work source into a Blue Prism Work Queue
• Processes items contained in the Work Queue
• Process completes once all items originally loaded into the Work Queue have been
attempted
This Process template has two main types of exception handling logic: functional (or
component) retry Exception handling within sub-pages; and top level Work Queue item
Exception handling on the Main Page.

Main Page Exception Handling

There is an Exception Block on the Main Page called 'Work' within which all the ‘Work
Step’ pages of the Process template are called.
• If the Work Step pages all complete successfully, the Process flow goes to a 'Mark Item
as Completed' page
• If there is an Exception within any of the Work Step pages that is not successfully
handled by the retry logic within that page, it will be caught by the recover stage in the
‘Work’ block on the Main Page and the process flow will go to the ‘Mark Item as
Exception’ page
• If an Exception occurs outside the ‘Work’ Exception block whist a case is not being
worked, the Process will terminate
Sub-Page Exception Handling
All Pages that call Business Object Action stages that interface with an application contain
retry Exception Loops. These retry loops have use Exception Blocks that contain Action
Stages that perform a distinct function within a system.

Figure 3.1
Exception Data Item Configuration

Data Item Name Data Item Type Description

Retry Limit Local The initial value of this data item should
be set to the maximum number of times
you want the process to recover and retry
the function being performed. This is
usually left with the default initial value of
3, but may be increased if an application is
known to be very unreliable.
Exception Process Flow Configuration

Stage Name Description

Retry? By default, this decision stage has been configured to retry System
Exception and Internal exception types only. If you have other
exception types for which you do not want to recover, you will
need to change this decision to cater for the exception types you
use.
Step 1a, Step 1b These note stages can be replaced by the main flow steps of the
distinct function being performed in a target system.
Step 1c This note stage, after the blocks Resume stage, should be replaced
by the logic that will recover the application back to a known and
working state ready to try and perform the function again.
Examples of how you might recover the application may be: •
Close any child windows and pop-up windows that may be
displayed • Navigate back to a Main Menu or root screen from
which the function can be tried again • Close and restart the
system, logging back in

This process template has a very basic Process Template Pages and Configuration. Here
we will give a description of how to configure each of the pages within the template:

 Main Page The main page within the process does not do any system navigation or
updates within the systems, but instead simply calls sub-pages that do all the work that is
required. This should leave the Main Page as a simple, high level view of what the process
does. The main page contains some global Environment, Session, and queue related data
items. It has the top level exception handling of the process, to handle exceptions that
bubble up from any sub-page whilst a case is being worked.
 Main Page Data Item Configuration
Data Item Data Item Description
Name Type
Process Name Global The initial value of this data item should be set
to be the name of the process you are creating.
The process name could be passed to objects or
subprocesses that it calls, if they have process
specific actions to take.
Queue Name Global The initial value of this data item should be set
to the main Work Queue being used by this
process.
Stop After Session The initial value should be set the time the
Time Variable process should stop running. It might be set to
a time before a system used by the process is
no longer available, or a time when another
process needs to be started instead. This
session variable can be changed by a Blue
Prism Controller at run time if there is an
operational reason that a running session
should finish at a different time to the default.
Stop After Session This data items allows the developer to
Items Variable configure the process to only work a pre-
defined number of cases. The template has the
initial value set to 9999999999, which
effectively means that the process will work all
items. This session variable can be changed by
a Blue Prism Controller at run time if here is an
operational reason to only work a set number
of cases before completing.
Stop ASAP Session This session variable can be changed from
Variable False to True by a Blue Prism Controller to
stop the process. If set to True the process will
stop cleanly, if a case is currently being
worked it will be completed before stopping
Start Up Page Configuration
The Start Up page gets the process ready to be able to work cases. It does this by:
• Performing any configuration and/or verification that is required
• Starting and logging into the systems that the process uses
If there is any validation of the environment required by your process, it should be added
to the Start Up page. Examples of the validation to be added are:

• Check that the directory paths used by the process exist

Check that any databases or web services used are available
• If objects require a specific resolution to run, call an action that ensures the resolution is
correct

Populate Queue Page Configuration

The Populate Queue page in the Template has been left Blank. A flow should be added to
get work from whatever the work source is for this process, and add it to the Work Queue
Work Step Pages Configuration
 These pages should each be updated to contain the logic to work each Work Flow case,
with each page containing logical specific task groupings
• Rename the pages to state what the page does
• Each page should perform a distinct function
You can have as many or as few of these Work Step pages as your process requires. Feel
free to delete some of the template pages, or add additional pages as needed.
• Add or remove additional Work Step pages as required
Each Work Step page that calls Business Object actions should contain retry exception
handling as described in the previous Exception Handling section.
• Include retry exception handling if a system is being used by the sub page
Mark Item as Completed Page Configuration
This page should be updated to perform any actions that need to be done if the Work
Queue item has been successfully worked without an exception.
By default the page simply updates the status on the Work Queue item and marks it as
completed.
If there are any additional actions that the process needs to perform upon completion, they
should be added to this page.
Mark Item as Exception Page Configuration
This page should be updated to perform any actions that need to be completed if the Work
Queue item has been marked as an exception.
Reset Global Data Page Configuration
Any Data Items that are global to the entire process and need to be reset before working a
new case can be reset to their initial value by the call to this page. Simply move any
global data items that need resetting for each case onto this page.
Close Down page Configuration
The Close Down page performs any tasks that need to be done before the process
completes. By default these include:
• Cleanly exiting the applications being used Any other actions that need to be performed
before the process completes should be added to this page.
Using Process Template 1 as the base for your build, rebuild the Blue Prism Foundation
Training Consolidation Exercise Process. As a reminder, this process:
• Read order information from a csv and populates a Work Queue
• Launch and Log into Centrix Data Solutions

Get next item from the Work Queue

• Validate the item
• Process the order through Centrix Data Solutions
• Extract the order confirmation number
• Update the item in the Work Queue to Complete or Exception

1. Process Template 2:
Process Template 2 is a multi-purpose template designed to be modified into the
foundation of numerous different styles of process. It offers the following in addition to
the capabilities offered in Process Template 1:
• Variations to how the Main Page of the Process works
• Additional Sub-Pages that can be used in your Process
Using Process Template 1 should be mastered before moving onto using Process Template
2.
This section describes how to use Process Template 2 to create a new process.
Process Template 2 contains many different example Main Pages, each called EXAMPLE
Main Page, and with a description of the page in brackets. These example main pages are
aimed to fit many different scenarios for processes that you may want to create.
To use the template to create a new process the modification procedure is as follows. •
Select most appropriate ‘example’ page
• Copy the contents of the selected ‘example’ page on to the Main page
• Delete all ‘example’ pages
• Save as

Figure 3.2

Module-4
Blue Prism Credentials and Credential Manager
Create Encryption Key
1. Log into your local Blue Prism training environment.
2. Click on the System icon to access the System area of Blue Prism
 3. From the System Treeview of settings on the left-hand side of the Blue Prism window, look
for the Security grouping and select Encryption Schemes. Figure 4.1
4. If the Security – Encryption Schemes panel looks like the
example below or cont
5. If the Security – Encryption Schemes panel looks like the
example below or contains no entries, then no encryption key
has been setup and you should continue with the following
steps to create one
Figure 4.2

Figure 4.3

5. If your panel displays an Encryption Scheme named Default Encryption Scheme,

then click on Edit from the Schemes: links on the right-hand side of the window. If
the panel has no entries, then click on New.
6. Set the Encryption Scheme Name to Default Encryption Scheme.
7. Select the Database from the Location radio buttons.
8. Select AES-256 AesCryptoServices (256 bit) or AES-256 RijndaelManaged (256 bit)
from the Method drop down list.
9. Click the Generate key link. This will generate the relevant key and add it to the Key
field.
10. Click OK.
The Security – Encryption Schemes panel
should now show your encryption
scheme with a status value of Available. Figure 4.4
The encryption key is ready to encrypt and decrypt Credential information.
Credential Setup
1. Log into your local Blue Prism training environment.
2. Click on the System icon to access the System area of Blue prism
3. From the System Tree view of settings on the left-hand side of the Blue
Prism window, look for the Security group and then select Credentials Figure 4.5
4. Click on New from the Credentials: links on the right-hand side of the window
5. Input a name for the new Credential. This should be descriptive, so it is clear which
business application the Credential entry is used to access.

For example,‘Centrix Data Solutions: Digital Worker1’ would indicate that the
Credential is used by Digital Worker1 to access Centrix Data Solutions.
6. From the Type drop down list, select the General option. The
other options will be explored later as part of the Developer
Certification training.
7. Within the Application Credentials tab, input the username for
Centrix Data Solutions. This is BP.
8. Now input the password for Centrix Data Solutions. This is
password
As Credential Manager governs access to Credential entries, we must assign
permissions to the new Credential so that our Process and Digital Worker can access
the Credential information. For this exercise, we will assign access to all users,
processes and Resources (Digital Workers), however in reality, permissions would
be granted to a smaller group of authorized Figure 4.6
users etc.

9. Click on the ‘Access Rights’ tab.

Figure 4.7

10. Click on the Security Roles tab and then tick

the “All Roles’ tick box.

Figure 4.8

11. Click on the Processes tab and then

check the All Processes checkbox.

Figure 4.9

12. Click on the Resources tab and then

check the All Resources checkbox.

Figure 4.10
13. Click OK. Your new Credential is ready to be used in your process.
Using Credentials in Blue Prism Processes
1. Open your Centrix Data Solutions Process.
2. Locate the Data Items Staff Number and Password and
remove their Initial Values. You can do this by opening the
Properties window for each Data Item and clearing the
Initial Value field.
3. Now locate the Action Stage in your Process diagram
which performs the log into Centrix Data Solutions activity
and add a new Action Stage directly before this Stage. Link
the new Action Stage into your Process diagram.
Your Process diagram should now look like the example
below; Figure 4.11
4. Open the new Action Stage and select Credentials from
the Business Objects drop down list. Credentials is an
Internal Business Object; therefore, you can’t view this
Business Object diagram in Object Studio.
5. Now select the Get Action from the Action drop down list.
6. In the Inputs tab, set the Value column to the name of the
Credential you created earlier. Remember, this is a Text
Input, therefore the value should be enclosed in quotes.
7. Now select the Outputs tab and map the Password output
Figure 4.12
to your existing Password Data Item. 8. Map the Username
output to your existing Staff Number Data Item.
Your Action Properties should resemble the examples below;
9. Press OK to return to your Process diagram.
10. Reset, Save and then Run your Process.
Your process will now retrieve Credential information
from Credential Manager and use this information to log into
Centrix Data Solutions.
Figure 4.13

Module -5
 Figure 5.1 Figure 5.2 Figure 5.3

Figure 5.4 Figure 5.5

Figure 5.6

Figure 5.7

Figure 5.8

Figure 5.9 Figure 5.10

Figure 5.11 Figure 5.12

Figure 5.13 Figure 5.14

Figure 5.15 Figure 5.16

Figure 5.17
Figure 5.18

Figure 5.19

Figure 5.20

Figure 5.21

Figure 5.22
 Module -6
ADVANCED ATTRIBUTE MATCHING
Overview of Attributes
Application Modeller The purpose of a Business Object is to make an application accessible
for use by a Blue Prism Process. To create an integration between a Business Object and an
application, you must create an Application Model.
Using Attributes in Application Modeller Each Element from within the application's user
interface is defined by creating a list of Attributes, which combine together to make a
unique fingerprint of that Element. This fingerprint allows a Business Object to correctly
identify the Element so that it can be continually used to perform specified tasks within a
Blue Prism Process.
The Application Modeller extracts information about the characteristics of an Element from
the target application user interface. This information is used to build the digital fingerprint
known as the Attributes List.

Figure 6.1 Figure 6.2

Attribute match type is always as “equal”.

Figure 6.3
 Match Type: Numeric Match Type Numeric allows you to build match criteria
based on Attribute values such as length and width. (DEALL There are four
numeric operators available when
using Match Type Numeric:

• Greater than (>)

• Greater than or equal to (>=)
• Less than (<)
• Less than or equal to (<=)

Figure 6.4

Match Type: Wildcard The Wildcard Match

Type allows you to perform a fuzzy match
against the Attribute value of the target
Element. Fuzzy matching is a technique
which allows you to identify a non-exact
word or phrase match for an Attribute
value.
Dynamic Attribute Matching
Figure 6.5
Match Type Dynamic The Dynamic Match Type enables you to match against values
which may change. Process logic can be configured to change the match value in
Application Modeller as required
The Parameters Button The value to match when using Dynamic Matching is
configured within the Properties window for each stage which needs to use the
Element. The parameters button, Params for short, is normally disabled and only
becomes enabled once an Element is set-up to use Dynamic Matching.

Figure 6.6
 Attribute Matching Strategy
Matching Strategies Application Modeller Define the elements of an application
that will be used by Object Studio Application Model belongs to this Object
Attribute Matching Strategy As target application technology and user interface
design varies widely, it is impossible to define a single strategy to use in relation
to Element attribute match selection.
Log in window
Matching Strategies Attribute Matching Guidelines Some general guidelines for
selecting effective match Attributes are:
• Carefully select match Elements which uniquely identify your target Element...
using 'least is best approach
• Avoid using Attributes which have the potential to be inconsistent such as Path, X,
Y, Parent X, Parent Y or Class
• Deselect an unused Attribute or Attributes with blank (NULL) values
Data validation
Data Validation At a general level, data validation is the process of ensuring data
has undergone some form of cleansing to ensure it is both correct and useful.
When capturing data, it's critical to verify and validate data before it is used by
your automation. For the purpose of Attribute matching, data validation will allow
you to match Attributes to specific data formats or patterns.
Examples of Data Validations Data validation can be used with Attribute matching
to achieve the following actions:
• Ensuring data is actually present when a process requires it
• Ensuring data is of the correct type i.e. numeric, text or a date
• Checking that data does not exceed a maximum number of characters
 Module-7
Blue Prism Associate Developer Next Steps
Get Certified - Take the Blue Prism Associate Developer exam
Blue Prism University offers an Associate
Developer Certification, through our on-line
exam partner PearsonVue. You can find out
more on our Blue Prism University
certification page

You’ll also find our Certification FAQs from

this page

How to Book Figure 7.1

Visit the Associate Developer Certification
page to find all the information you’ll need
to know regarding the exam, including scope
& preparation.

Figure 7.2

Get a Digital Badge

Blue Prism awards digital badges to candidates who successfully pass an exam with
PearsonVUE. These can be shared on-line for maximum visibility and recognition.
You can share your badges with anyone you’d like, wherever you’d like:
• LinkedIn
• Facebook
• Twitter
• Via email
• Embedded in a website
A viewer can click on your badge and will be
taken back to Acclaim to view all the details
of your achievement. You can also share
your complete Acclaim profile to provide an
employer with the full context of your
abilities, allowing them to authenticate your
Blue Prism certification.
Figure 7.3
 Module-8
Blue Prism Associate Developer Certificate readiness
Webinar

Figure 8.1 Figure 8.2

Figure 8.3 Figure 8.4

Figure 8.5 Figure 8.6

Figure 8.7 Figure 8.8

Figure 8.9 Figure 8.10

Figure 8.11 Figure 8.12

Figure 8.13 Figure 8.14

 Figure 8.15 Figure 8.16

Figure 8.17 Figure 8.18

Figure 8.19

Figure 8.20

CONCLUSION

This project delivers how the Robotic Process Automation works by starting from basic
awareness of the interface and the concept and gives a basic awarness about the
automation process and the blue prism interface and the foundation in the blue prism
can be developed by expaining the project studio and the oject studio seperately and
how the exceptions are managed in the blue prism interface.

Process templates of the work flow are explained an dunderstood to make the working
easy. The Credentials of the blueprism and the credential manager makes it easier to
explore the management of the login and the process edtails of the project.And how the
data items, Attribute matching are managed in the process.