• Home
  • Introduction to Blue Prism Objects

When a Blue Prism robot needs to interact with some other software e.g. your order system or employee management system you will need to “teach” Blue Prism how to use that software. This is done by creating an object in Blue Prism. You will need at least one object per software the robot will interact with.

Introduction to Blue Prism Objects

When a Blue Prism robot needs to interact with some other software e.g. your order system or employee management system you will need to “teach” Blue Prism how to use that software. This is done by creating an object in Blue Prism. You will need at least one object per software the robot will interact with.

An object consists of multiple actions which are then used in a process in the appropriate order. The action will contain steps such as instructing Blue Prism to type text to a textbox, choose a value from a drop-down list or click a specific button.

Blue Prism Flow

1. Application Modeller

The application modeller is where you set up information about the software you want to “teach” Blue Prism. The kind of information you will need to provide is:

  1. The type of software: e.g. a Windows or browser-based application
  2. The path to the exe file for a Windows application
  3. The URL for a browser-based application

2. Elements

An element is any part of the software that you want Blue Prism to interact with. This could be a textbox, checkbox, or button. For example, in the screen below you would need Blue Prism to type in the staff number, type in the password and then click on the Log In button. Therefore, you will need to create these 3 elements.

Blue Prism Flow

The elements are created in the Application Modeller.

3. Actions

In an action you will use stages to instruct Blue Prism to write to, read from or click on an element. Below is the action to login to an application.

Blue Prism Flow

An action should contain waits which are used to make sure an element is there before Blue Prism tries to interact with it. Should an element not be there the action will throw an error.