Access Token for Blue Prism

Configure an access token to connect to Blue Prism.

Figure: Blue Prism Access Token Configuration screen

Blue Prism Access Token Configuration screen

Background and Setup

Video: AgilePoint NX Connector for Blue Prism RPA

Embedding for the video is not available at this time. To view the video, refer to http://agilepointnxblog.com/agilepoint-nx-connector-for-blue-prism-rpa/

Prerequisites

Good to Know

  • In most cases, you can use a global access token or an app level access token:
    • Global access tokens are shared across all users and apps. If you want all process designers and runtime app users in your AgilePoint NX tenant to be able to connect to an external data source, use a global access token. An example is a SharePoint site on an intranet that all employees in a company can access.
    • Application level access tokens are shared with all processes in a process-based app, or restricted to use within a form-based app. Use application level access tokens if only process designers or runtime app users for a particular application should access an external system — for example, a Box account that is only used to share files within a small team.
  • Access tokens are collections of credentials that are used to authenticate communication directly between AgilePoint NX and an external system. Because it is the AgilePoint NX system that uses these credentials, rather than an app, there is no difference between design time and runtime access tokens. Access tokens are never checked in or published, and they do not use version control. If you change an access token in the App Builder or Manage Center, the access token changes immediately everywhere the access token is used. Changes to app level access tokens apply to all versions of an app, including running application instances. Changes to global access tokens apply everywhere they are used in AgilePoint NX. You can not roll back an access token to a previous version.

    For more information, refer to What Data Is Deleted When I Delete an App or Application Resource?

  • This screen may look different in different places. The UI varies for this screen depending upon how you open it. However, the fields for this screen are the same in all places.
  • Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

Fields

Field NameDefinition

Token Name

Function:
Specifies the unique name for your connection to Blue Prism.
Accepted Values:
One line of text (a string).

Accepted:

  • Letters
  • Numbers
  • Spaces
Default Value:
None
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Function:
A description for your access token.
Accepted Values:
More than one line of text.
Default Value:
None
Example:
This is a common configuration field that is used in many examples. Refer to:
  • Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Process Service URL

Function:
Specifies the process service URL from Blue Prism environment.

The process services URL comes from Blue Prism.

To Open this Field:
  1. On the Blue Prism Access Token screen, click Process Service URL.
Accepted Values:
A process service URL from Blue Prism.
Default Value:
None

Business Object Service URL

Function:
Specifies the business object service URL of your Blue Prism environment.

The business object service URL comes from Blue Prism.

To Open this Field:
  1. On the Blue Prism Access Token screen, click Business Object Service URL.
Accepted Values:
A business object service URL from Blue Prism.
Default Value:
None

User Name

Function:
Specifies the user name for Blue Prism authentication.
Accepted Values:
The user name for your Blue Prism environment.
Default Value:
None
Accepts Process Data Variables:
No

Password

Function:
The password for the authentication account.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Accepts Process Data Variables:
No

Domain

Function:
The authentication domain for the Blue Prism environment.
Accepted Values:
A valid domain.
Default Value:
None

Timeout (In Seconds)

Function:
Specifies the maximum time in seconds to connect to the Blue Prism.
Accepted Values:
An integer.
Default Value:
60

Test Connection

Function:
Makes sure the specified Blue Prism account is correct.

Before you click the Test Connection button, make sure that you are signed in to your Blue Prism environment. Otherwise, it shows a test connection failure error.

Encrypt

Function:
Stores the access token in the AgilePoint database as encrypted data.
Note: AgilePoint recommends you to store this access token in the database in encrypted format.
Accepted Values:
  • Deselected - The access token is in plain text in the database.
  • Selected - The access token is encrypted in the database.
Default Value:
Selected
Limitations:
  • This field was removed from the UI in AgilePoint NX OnPremises and Private Cloud v7.0 Software Update 2. Access token credentials are encrypted by default. If you want to store credentials in unencrypted format, contact AgilePoint Customer Support.