Exception Types :

"Application Unavailable "

"Business Exception"
"Data Exception"
"Empty Field"
"Internal"
"Invalid Data - Y is 0"
"Process Exception"
"Session name"
"System"
"System Error"
"System Exception"
"System Unavailable Exception"

ExceptionDetail() : The detail for the exception currently being recovered from.

ExceptionStage() : The name of the stage which is the source of the exception currently being handled.

ExceptionType() : The type of the exception currently being recovered from.

File :

LoadBinaryFile({Filename}) : Read the contents of a file as binary data.

LoadTextFile({Filename}) : Read the contents of a text file.

Logic:

{Operand A}AND{Operand B} : Gets a flag saying whether two conditions are simultaneously true. E.g. (1<2) AND
(3<4) results in True.

{Operand A}={Operand B} : Gets a flag saying whether one value is equal to another. E.g. 5 = 3 + 2 results in True.

{Operand A}>{Operand B} : Gets a flag saying whether one value is greater than another. E.g. 5 > 3 results in True.

{Operand A}>={Operand B} : Gets a flag saying whether one value is greater than or equal to another. E.g. 5 >= 3
results in True.

IsDate({Text}) : Checks if the given text is a valid Date according to the current regional settings. eg. IsDate("Example")
results in False.

IsDateTime({Text}) : Checks if the given text is a valid DateTime according to the current regional settings. eg.
IsDateTime("Example") results in False.

IsFlag({Text}) : Checks if the given text is a valid Flag according to the current regional settings. eg. IsFlag("Example")
results in False.

IsNumber({Text}) : Checks if the given text is a valid Number according to the current regional settings. eg.
IsNumber("Example") results in False.

IsTime({Text}) : Checks if the given text is a valid Time according to the current regional settings. eg. IsTime("Example")
results in False.

IsTimeSpan({Text}) : Checks if the given text is a valid TimeSpan according to the current regional settings. eg.
IsTimeSpan("Example") results in False.
{Operand A}<{Operand B} : Gets a flag saying whether one value is less than another. E.g. 3 < 5 results in True.

{Operand A}<={Operand B} : Gets a flag saying whether one value is less than or equal to another. E.g. 3 <= 5 results
in True.

{Operand A}<>{Operand B} : Gets a flag saying whether one value is not equal to another. E.g. 5 <> 3 results in True.

{Operand A}OR{Operand B} : Gets a flag saying whether at least one of two conditions is true. E.g. 1<2 OR 3>4 results
in True.

Key Points :

• The Reset button must always be pressed before re-running a Process

• Stages are added by clicking onto the page for the current cursor or by dragging from the toolbar.

• Links are created by dragging from “centre to centre”, not from “edge to edge”.

• Most stages have a single outbound link but some can have more.

• Most stages accept multiple inbound links but some (like the Start stage) cannot be linked to at all.

• Most stages appear on the diagram by a single shape but some have two parts.

• A page can have multiple end points but only one starting point.

• Data Items are not linked into the logical flow, they “float” and cannot be physically connected to any other part of
the diagram.

• Square brackets must be used to include a Data Item in an expression, e.g., [Account ID].

• Set Next Stage does not “fast-forward” or “rewind” but simply “jumps” forward or back.

• Breakpoints only take effect when the diagram is open. In the Production environment, the diagram is not
displayed when a Process runs and Breakpoints are ignored.

• Dot notation is used to refer to Collection fields, i.e., “Collection Name.Field Name”

• As well as being used to sub-divide and organize a diagram, pages can also be used to make reusable functionality.

• An input value is supplied as an expression.

• Usually this expression will simple (e.g., the name of a Data Item like [Full Name]) but could be more complex (e.g.,
[Forename] &“ “& [Middle Name] & “ “ & [Surname]).

• Diagrams are for development and testing purposes. Diagrams are not used to run Processes in the Production
environment.

• A Session can only run once; to run a Process again a new session must be created.

• A Business Object is not configured in Process Studio but in a distinct, parallel environment named Object Studio.

• The purpose of a Business Object is to provide an interface to one application.

• A Business Object is not exposed to Control Room and is never used on its own – it is always used by a Process.

• Business Object logic can be thought of as forming a separate layer to Process logic.
• Data are transferred between a Process and a Business Object via input and output parameters.

• Keep “CTRL” down until you’ve clicked the mouse.

• To exit spy mode, it’s CTRL+right-click.

• Attributes do not come from Blue Prism; the application provides these data to Application Modeler.

• Application Modeler forms these attributes into elements.

• Object Studio uses the elements to manipulate the application.

• Application Modeler suggests a selection of attributes when the element is spied.

• The selection must uniquely identify the element and may require manual alteration.

• The application model should not be created in one go but built up gradually. After spying a few elements, return
to Object Studio to check their use from the diagram.

• Just as in Process Studio, a Business Object must exist (i.e., be saved) in the Blue Prism database before it can run.
• You don’t need to save every time, but you need to save before the very first run.

• The Wait stage is absolutely vital to the creation of Business Objects.

• A Wait stage can wait for a single condition or several conditions.

• A Wait stage will take the path of the first True condition or, if the timeout elapses, the action can proceed to carry
out further actions or as noted previously to throw an Exception as something has not happened as expected.

• An exception at the Timeout stage will alert the Process to an error that has happened.

• A Wait stage can exist without any condition and the timeout can be used as a pause.

• Using Terminate is similar to killing an application using Task Manager.

• Although some applications are not adversely affected by being closed in this way, it is important to remember
that some are and that a gentler, less severe Close method is required.

• You can organize your elements in the Application Modeller treeview as you wish, but best practice is to use a
hierarchy that reflects the structure of the application.

• Application Modeler suggests a selection of attributes when the element is spied.

• The selection must uniquely identify the element and may require manual alteration.

• Finding a winning combination of attributes is largely down to trial and error but as your experience grows, you will
become more adept at making these adjustments.

• Although Ordinal is a fairly common attribute and can, as in this example, make all the difference, it is not available
in all application types.

• Using the application may invalidate elements in the application model.

• The “unable to match with query terms” message is Application Modeler saying, “I can’t find that thing anymore.”

• The selection of attributes can be reduced in order to make an element “correct”.

• You can use the mouse as normal when spying an application; holding the CTRL key prevents the mouse click from
actually pressing the button

• Attach is used to connect a Business Object to a running application.

• Detach is used to disconnect a Business Object from an application.

• Attach needs an input value to help it identify the application.

• Attach will fail if the Business Object is already attached.

• When a Business Object launches an application, it is attached automatically.

• Inputs to a page in Object Studio provide the means for a Process to supply data to the Business Object.

• In Process Studio these inputs are shown in the properties of the Action stage.

• The initial and current values of a Data Item are not expressions, and as such text values do not need quotation
marks.

• A Recover stage acts like a magnet – exceptions are drawn to it and the diagram flow will jump from the exception
point to the Recover stage.

• When Blue Prism is on the path between a Recover and a Resume it is said to be in Recovery Mode.

• A Resume stage neutralizes the exception but does not fix the problem.

• Once past the Resume stage, the exception is effectively “gone” and the diagram can continue its normal flow.

• By default a page only uses one Recover stage and any others will be redundant.

• The Exception Type value in an Exception Stage is not an expression and does not need quotes.

• The Exception Detail value is an expression and does need quotes.

• Exception functions like ExceptionDetail() and ExceptionType() cannot be used anywhere other than in between a
Recover and a Resume, i.e., in Recovery Mode.

• The “Preserve” checkbox is only applicable when in Recovery Mode.

• Re-throwing an exception will generate a second exception unless the “Preserve” checkbox is checked.

• To throw a new exception, make sure it is thrown after a Resume stage, thereby neutralizing the current exception
before the new one is created.

• Exceptions travel upwards towards the Main page of the Process.

• Exception handling can be on the same layer as the source of the exception or above it.

• Unless the exception is intercepted it will terminate the process.

• One Recover stage will handle all exceptions on a page.

• Without Blocks, any extra Recover stages on a page will be superfluous.

• Blocks are a way of using multiple Recover stages on the same page.

• An exception generated inside a Block will be handled by the Recover inside that Block.
• If a Block does not contain a Recover stage, the Block will have no effect.

• One Recover stage will handle all exceptions generated inside its Block.

• Any extra Recover stages in a Block will be superfluous.

• Blocks should not overlap and Blocks cannot be nested (i.e., Blocks within Blocks).

• Blue Prism has some Business Objects that come as part of the software. These “internal” Business Objects are not
diagrams and cannot be seen or changed, only used.

• The special “Work Queue – Internal” Business Object is used to interact with a work queue.

• When an item is being worked, it is “locked” so no-one else can work it.

• When an item is marked as “complete” or “exception”, the lock is released.

• An item is referred to by its unique Blue Prism ID.

• Each item has its own Collection to hold data.

• Like in a Data Item, the initial and current values of a Collection are not expressions and text values do not need
quotes.

• The item data Collection can be updated to save information back to the queue.

• Providing empty fields (like Narrative) when the item is created could provide storage for data collected while the
item is being worked.

• If Get Next Item fails to get an item, it does not necessarily mean there are no unworked items in the queue; it
could be that there are deferred items the queue is yet to release.

• A queue can be set up to enable multiple attempts on an item.

• Attempts only apply to exceptions – items marked as complete cannot be reworked.

• The creation of a retry item can be cancelled from the diagram.

• The inputs of the Internal – Work Queues actions ask for the name of the collection, rather than the collection
itself. The data type of the “Collection Name” input is Text, not Collection.

• The decision as to which stages are logged and which are not should not be overlooked.

• Logs are particularly useful during a test phase as a means to investigate bugs.

• However a live Process running all day can put a vast amount of logs into the database, the maintenance and back
up of which should be considered.

• The security or legal implications of storing sensitive data are also something to think about.

• Blue Prism creates different environments by using separate databases. Typically this would be three databases -
Development, Test, and Live.

• Moving work from one database to another is done by exporting and importing.

• An exported file can also be attached to email and used as a basic back up.

• Environment Variables are available to all Processes and Business Objects.

• Data Items exposed as Environment Variables are read-only.

• The name and type of the Data Item must match the Environment Variable.

• Session Variables are specific to that instance of the Process. If two instances of the same process are running at
the same time, they will both have the same Session Variables but the Session Variables will have different values.

• Session Variables need no setup in System Manager.

• Data Items exposed as Session Variables are writable.

• Session Variables can be viewed and modified from Control Room.

• Blue Prism has multiple spy mode options.

• After pressing the Identify Element button, use the ALT key cycles through them.

• When you request a lock, it will be created automatically if it does not already exist.

• The system will automatically release any locks that your Process neglects to release in the proper fashion,
whenever the Process stops running. This includes Processes running in both Process Studio and Control Room.

• Resource PC is Blue Prism launched in a different mode.

• Any machine with Blue Prism installed can run Resource PC.

Best Practices :

• Get into the habit of using the validation tool as you go along, and in particular, run the validation before you close
the Process. • If you don’t use the validation tool you will almost certainly have a glut of silly problems to fix during
testing.

• Be descriptive when naming a Business Object page – use a verb to communicate the purpose of the page. For
example, “Open Account History” or “Close Account History” is much better than just “Main Menu”. • Open the
Page Information box and provide a description. As you become more proficient you should also document your pre-
and post-conditions.

• Be generous with timeouts - overestimate rather than underestimate. • Recall the timeout of five seconds which
you applied to the wait stage above. In most practical situations, it does not matter if you set this value much higher
(e.g., to 30 seconds), because Blue Prism responds immediately once the expected condition is met – the timeout is
merely the maximum amount of time that you are prepared to wait. • On the other hand, if you were to set the
timeout to an unsuitably small value (such as 1 second), then you would experience unpredictable results. It is
therefore better to overestimate rather than underestimate the length of time you need. • Use Data Items to store
timeout values. You should use Data Items to store timeout values so that you can modify multiple Wait stages with
one easy change to a Data Item. • Business Objects should have global timeout period data items that are used in all
wait stages in the object. • Using global data items to store timeout periods makes it easy to re-configure how long
an application should wait for different types of system activity.

• A Get Next Item Action should almost invariably be followed by some sort of Got Item? Decision. • An expression
checking if the ID is blank is the best way to test if you have got an item.

Object Studio Process Studio

Read Alert
Write
Navigate
Code
Wait

Common in Object Studio and Process Studio :

Pointer Link Block Process Page

Action Decision Choice Calculation Multi Calc

Data Item Collection Loop Note Anchor

End Alert Exception Recover Resume

This Delivery Roadmap navigates through the following stages:

1. Process Management
 Initial Process Analysis (IPA) : An IPA is a means of framing the information available at the early stage of a project
into a succinct document illustrating the salient points. The objective of the IPA is to provide a high level analysis of
the process solution, the automation efficiency and the effort involved in delivering and supporting the solution.

Created by – Blue Prism analyst or Blue Prism developer

Read by – Client sponsor
Approved by – Does not require specific approval

2. Define
 Process Definition Document (PDD) : The main purpose of a Process Definition Document (PDD) is to describe the
manual process that is to be automated. The PDD only needs to be created where existing process documentation
does not exist or isn’t provided to the required detail.

Created by – Client SME and/or Blue Prism analyst

Read by – Client SME, Blue Prism analyst, Blue Prism developer
Approved by – Client operation, client SME.

Process Detail : A robot cannot think for itself and can only follow a set of predefined logical steps. A PDD should
therefore go beyond the level of detail normally provided to a human and specify exactly how the process is to be
carried out. A diagram and descriptions of every stage in the diagram should be included.
The design of a Blue Prism solution will be based on the PDD, so the more explicit the PDD, the greater the chance of
a successful delivery.
Application Detail : Application screenshots and descriptions of each step should be provided, with annotations
applied to the images where necessary. Any system warning messages, pop-up messages that might appear should
also be explained.

 Process Walkthrough : Once a process has been defined, the quality of the PDD can be gauged by using it as a
stepby-step instruction manual.

Participants – Client SME, Blue Prism developer, Blue Prism analyst (optional)

 Functional Requirement Questionnaire (FRQ) : The Functional Requirements Questionnaire (FRQ) provides a quick
checklist of the required details and areas for consideration.

Participants – Client SME, Blue Prism analyst

3. Design
 Solution Design Document (SDD) : The purpose of the Solution Design Document (SDD) is to describe how Blue
Prism will automate the process described in the PDD. As well as describing the automated solution, the SDD should
include details of any other deliverables that are required, such as web services, database tables, input files, network
folders etc. Other derivatives such as security requirements, scheduling, alerting, management information, and
exception handling procedures should also be mentioned.
The SDD includes a description of
 Overview of end-to-end solution
  Object model
 Operational control and alerting
 Data security and credentials
 Business and technical assumptions

Created by – Blue Prism developer

Read by – Client operations, IT
Approved by – Client operations, IT

 Operational Impact Document (OID) : The Operational Impact Document (OID) is required to inform the client
operation team of their responsibilities once the automated solution is in place. It is a description of the change that
will be impacted upon them once the solution has been successfully implemented.

Created by – Blue Prism analyst

Read by – Client operation, Blue Prism controller
Approved by – Client operation

 Solution Walkthrough – Workshop : In the same way that the PDD should be played out, a workshop to walk
through of the SDD and OID should be carried out to check the proposed automated solution and its effect on the
wider business.

Participants – Client SME, client operation, Blue Prism analyst, Blue Prism developer

 Process Design Instruction (PDI) : In the same way that the PDD should be played out, a workshop to walk through
of the SDD and OID should be carried out to check the proposed automated solution and its effect on the wider
business. A completed PDI will form a work task for a developer.

Created by – Blue Prism developer

Read by – Blue Prism developers
Approved by – Peer review

 Object Design Instruction (ODI) : Like a PDI, the Object Design Instruction (ODI) is created as a blueprint from
which business objects can be developed. The object design instruction describes each object to be built and for
each action within that object lists the input and output parameters and the start and end screens.

Created by – Blue Prism developer

Read by – Blue Prism developers
Approved by – Peer review

4. Build

5. Test
Phase 1 :
Performed by – Blue Prism developer, Blue Prism tester and client SME (optional)
Blue Prism running mode – Process Studio and Control Room
Blue Prism environment – Development
Target System environment – Test
Acceptance criteria – Test script

Phase 2 :
Performed by – Blue Prism developer, Blue Prism tester and client SME
Blue Prism running mode – Process Studio and Control Room
Blue Prism environment – Development
Target System environment – Live
Acceptance criteria – Test script
 Phase 3 :
Performed by – Blue Prism tester, client SME
Blue Prism running mode – Control Room only
Blue Prism environment – Test
Target System environment – Live
Acceptance Criteria – Volume, performance and quality targets

Debugging :

GO : F5

Step : F11 - By pressing the Step button the process will move one action at a time.

Step Over : F10 - By pressing the Step Over button the process will move one stage at a time.

Step Out : Shift + F11

Spying Modes
The three spying modes available for browser integration are Win32 mode, HTML mode and Active
Accessibility mode. Sometimes it is logical to use a mixture of all three modes when you are building your
element tree.
 Win32 mode will only work with Internet Explorer windows themselves, not with the web app within.
This mode is particularly helpful for manipulating IE windows by performing actions such as Resize,
Activate and Send Keys. It can also be used with Wait stages, for example, waiting for a window to
appear on the screen.

 HTML mode will only recognise the HTML elements within the web app, nothing outside.

 Active Accessibility mode can detect a mixture of web app elements and Internet Explorer
elements. If the standard HTML mode does not work, this mode often does.

If you encounter any unexpected problems that prevent you from using either of the three spying
modes, an alternative exists in the form of the Application Navigator. To open the navigator, you
 need to click on the drop down arrow next to the Identify button in Application Modeller and select
Open Application Navigator.
Once opened, the application navigator will scan the HTML document for all the elements it can
find. It will then display a tree structured list of HTML elements from which you can choose from to
create your elements in Application Modeller. You will notice that when you select an element in the
tree it will be highlighted within the web browser for confirmation and its attributes will be displayed.
The screenshot below shows a highlighted HTML Edit element selected in the element tree,
resulting in it being highlighted within the browser.

3.7 Wait Stages

Among the conditions that can be checked for in a Wait stage are Parent Document Loaded, Document
Loaded and Check Exists. Each of these conditions check for separate things and should be usually
appropriately.
 Parent Document Loaded. This checks the element exists and that the entire page and all of its
child frames are fully loaded. Parent Document Loaded includes an implicit Check Exists on the
element as well as a Document Loaded check. It is usually good practice to use this at the start of a
browser action.
 Document Loaded. This checks if the current document has loaded. Do not use this unless you
know you are already on the page which you are waiting to load, otherwise it is more appropriate to
use Parent Document Loaded on an element on the target page.
 Check Exists. This simply checks that the specified element exists on the page, regardless of if any
other elements exist.

Pop-up windows may need to be spied using Win32 or AA mode instead of the usual HTML mode. To
speed up development, it might be best to build a separate generic object to handle IE pop-up windows.

4.2 Parent URL

Depending on the structure of the web site, the Parent URL of an element may not be consistent. It is
usually helpful to un-tick the Match column for the Parent URL attribute of the spied element in Application
Modeller, or else problems will arise when you attempt to use the element after the Parent URL has
changed.

4.3 Element Mask

Element Mask is a feature in Application Modeller that enables you to copy the attribute selection of one
element and apply it to another. This can be very useful once you have found a winning combination of
attributes on one element that you want to apply to more elements. To use Element Mask simply right-click
on an element and select Copy Element Mask or Apply Element Mask.

4.4 ID Attribute
Using the ID attribute to match elements can speed up interfacing with the target application. Some web
applications allocate unique IDs to elements meaning the ID attribute can be used by a Blue Prism
developer to create a reliable application model. However, with some applications the ID attribute can be
dynamic, so matching with this attribute might not work reliably.

4.5 Class Name

Like the ID attribute, some web applications contain elements that have static class names. However, some
applications contain elements where the class name changes so be careful when using this attribute to
build an application model.

4.6 Match Index

When the highlight button in the application modeller is pressed, Blue Prism searches for any elements
within the target application that have matching attributes with those selected in the application model
defined by the developer. If more than one element matches more than one elements are highlighted.
When the Match Index attribute is selected, only one element will be highlighted. If the value of Match Index
is set to 1, Blue Prism will stop searching the application for elements as soon as it finds the first element
that matches. If set to 2, the search will halt after a second element that matches is found and that element
will be highlighted, ignoring the first. The value of Match Index can be adjusted by the developer if required.
This can be very useful when working with multiple elements that are difficult to distinguish from each other.

Text Function :

Chr({Code}) : Get the character represented by the given numeric code, e.g. 65 is A, 66 is B

{Operand A}&{Operand B} : Gets a text expression by concatenating two others.

E.g. "A" & "B" results in "AB".

EndsWith({Text}, {Text}) : Checks if one piece of text ends with another

E.g. EndsWith("Example","ample") results in True.

InStr({Text}, {Search}) : Checks if one piece of text ends with another

E.g. EndsWith("Example","ample") results in True.

Left({Text}, {Length}) : Gets text taken from the left of a text expression.
E.g. Left("Example",3) will result in "Exa".

Len({Text}) : Gets the number of characters in some text

E.g. len("Example") will result in 7.

Lower({Text}) : Gets text representing a text expression in lower case.

E.g. Lower("EXAMple") results in "example".

Mid({Text}, {Start point}, {Length}) : Gets text taken from the middle of text expression.
E.g. Mid("Example",3,3) will result in "amp".

NewLine() : Get the new line characters, carriage return followed by line feed.

Replace({Text}, {Pattern}, {NewText}) : Gets text with one piece of text replaced with another
E.g. Replace("Example","am","to") results in "Extople".

Right({Text}, {Length}) : Gets text taken from the right of text expression.
E.g. Right("Example",3) will result in "ple".

StartsWith({Text}, {Text}) : Checks if one piece of text starts with another

E.g. StartsWith("Example","Exam") results in True.

Trim({Text}) : Gets text that is the input with any whitespace trimmed from the start and end.
E.g. Trim(" Example ") results in "Example".

TrimEnd({Text}) : Gets text that is the input with any whitespace trimmed from the end.
E.g. TrimEnd(" Example ") results in " Example".

TrimStart({Text}) : Gets text that is the input with any whitespace trimmed from the start.
E.g. TrimStart(" Example ") results in "Example ".

Upper({Text}) : Gets text representing a text expression in upper case.

E.g. Upper("EXAMple") results in "EXAMPLE".

Number Function :

DecPad({Number}, {Places}) : Gets text representing a number with decimal places padded out with zeros.
E.g. DecPad(1,2) results in "1.00".

Log({Number}, {Base}) : Determines the power to which the logarithm's base must be raised to achieve the input value.
 E.g. Log(1000, 10) = 3 because 10^3 = 1000.

{Operand A}^{Operand B} : Raises a number to the power of another - eg 3^4 = 3*3*3*3 = 81.

RndDn({Number}, {Places}) : Gets a number rounded down to a number of decimal places.

E.g. RndDn(1.47,1) results in 1.4. RndDn is symmetrical, i.e. values are truncated

RndUp({Number}, {Places}) : Gets a number rounded up to a number of decimal places.

E.g. RndUp(1.47,1) results in 1.5.

Round({Number}, {Places}) : Gets a number round off to a number of decimal places.

E.g. Round(1.47,1) results in 1.5.

Sqrt({Number}) : Gets the square root of the number.

E.g. Sqrt(9) results in 3.

Coversion :

ToDate({Text}) : Converts a value to a Date, following the standard Blue Prism data casting rules. Eg : MM/dd/yyyy

ToDateTime({Text}) : Converts a value to a DateTime, following the standard Blue Prism data casting rules.

ToDays({TimeSpan}) : Converts a TimeSpan to a whole number, rounded down, of Days.

ToHours({TimeSpan}) : Converts a TimeSpan to a whole number, rounded down, of Hours.

ToMinutes({TimeSpan}) : Converts a TimeSpan to a whole number, rounded down, of Minutes.

ToNumber({Text}) : Converts a value to a Number, following the standard Blue Prism data casting rules.

ToSeconds({TimeSpan}) : Converts a TimeSpan to a total number of Seconds.

ToTime({Text}) : Converts a value to a Time, following the standard Blue Prism data casting rules.

Data :

Bytes({Data}) : Gets the number of bytes in some binary data.

Date :

AddDays({Date}, {Days}) : Add a number of days to a date. Eg AddDays("01/02/2005",20) results in the date
"21/02/2005".

AddMonths({Date}, {Months}) : Adds a number of months to a date. Eg AddMonths("25/01/2005",3) results in the date
"25/04/2005".

DateAdd({Interval}, {Number}, {Date}) : Gets a date with a number of intervals (e.g. days, months etc) added to it. See
the Help documentation for examples and full interval list.

DateDiff({Interval}, {Start Date}, {End Date}) : Gets the number of intervals (e.g. days, months etc) between two dates.
See the Help documentation for examples and full interval list.

FormatDate({Date}, {Format}) : Gets text representing a local date in a given format. eg. FormatDate("01/02/2003","dd
MMM yy") results in "01 Feb 03".
FormatDateTime({Date}, {Format}) : Gets text representing a local datetime in a given format. eg.
FormatDateTime("01/02/2003","dd MMM yy") results in "01 Feb 03".

FormatUTCDateTime({Date}, {Format}) : Gets text representing a UTC datetime in a given format. eg.
FormatUTCDateTime("01/02/2003","dd MMM yy") results in "01 Feb 03".

LocalTime() : Gets the current local time as a Time value.

MakeDate({Day}, {Month}, {Year}) : Gets a date made from the given day, month and year. E.g. MakeDate(1,2,2005)
results in 01/02/2005.

MakeDateTime({Day}, {Month}, {Year}, {Hours}, {Minutes}, {Seconds}, {Local}) : Gets a datetime made from the given
day, month and year, hours, minutes and seconds.
E.g. MakeDateTime(1,2,2005,13,25,00,False) results in 01/02/2005 at 13:25:00

MakeTime({Hours}, {Minutes}, {Seconds}) : Gets a time made from the given hours, minutes and seconds.
E.g. MakeTime(13,25,0) results in 13:25:00

MakeTimeSpan({Days}, {Hours}, {Minutes}, {Seconds}) : Gets a timespan made from the given days, hours, minutes,
seconds.
E.g. MakeTimeSpan(2,13,25,0) results in 2.13:25:00

Now() : Gets the current date and time as a datetime value.

Today() : Gets the current date as a date value.

UTCTime() : Gets the current UTC time as a Time value.

Environment :

BPServer() : Determine if a Blue Prism Server is being used, rather than a direct database connection. True if so.

BPVersionMajor() : Get the major version number of the running Blue Prism software - e.g. 3 for version 3.5.

BPVersionMinor() : Get the minor version number of the running Blue Prism software - e.g. 5 for version 3.5.

GetClipboard() : Gets text from the Clipboard.

GetConnection() : Gets the name of the current Blue Prism database connection.

GetIEVersionMajor() : Get Internet Explorer major version number.

GetOSArchitecture() : Get the operating system arcitecture.

GetOSVersion() : Get the operating system version - for example 'Windows 2000' or 'Windows XP'.

GetOSVersionMajor() : Get the operating system major version number.

GetOSVersionMinor() : Get the operating system minor version number.

GetResourceName() : Get the name of the Resource running the current process.

GetSessionId() : Get the ID of the session running the current process, or empty text if no session is currently running.

GetStartTime() : Gets the start time of this process instance.

GetUserName() : Get the name of the user responsible for starting the current session, or empty text if no session is
currently running.

IsStopRequested() : Checks if a safe stop has been requested in the current session.

SingleSignon() : Determine if SingleSignon is being used, rather than Blue Prism authentication. True if so.