Access Token for Ethereum

Configure an access token to connect to Ethereum.

Figure: Ethereum Access Token Configuration screen

Ethereum Access Token Configuration screen

Background and Setup

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 Google Drive 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?

  • If you need help configuring this access token, contact AgilePoint Professional Services.
  • 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 Name Definition

Token Name

Function:
Specifies the unique name for your connection to Ethereum.
Accepted Values:
A text string that can have letters, numbers, and 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.

Ethereum RPC Endpoint

Function:
Specifies the endpoint URL for your Ethereum environment.

Once you sign in to Ethereum, your endpoint URL shows.

Accepted Values:
An endpoint URL for Ethereum.
Default Value:
None

Authentication Types

Function:
Specifies the authentication type to connect to your Ethereum environment.
Accepted Values:
  • Use Private Key - Uses a private key to connect to Ethereum.
  • Use Account Details - Uses the specified user credentials authentication to connect to Ethereum.
Default Value:
Use Private Key

Private Key

Function:
Specifies a private key from Ethereum.
To Open this Field:
  1. On the Ethereum Access Token screen, click Use Private Key.
Accepted Values:
A string with letters and numbers.
Default Value:
None

Account Address

Function:
Specifies an account address from Ethereum.
To Open this Field:
  1. On the Ethereum Access Token screen, click Use Account Details.
Accepted Values:
A string with letters and numbers.
Default Value:
None
Accepts Process Data Variables:
No

Account Password

Function:
The password for the authentication account.
To Open this Field:
  1. On the Ethereum Access Token screen, click Use Account Details.
Accepted Values:
An alphanumeric string that represents a password.
Default Value:
None
Accepts Process Data Variables:
No

Contract ABI

Function:
Specifies the application binary interface (ABI) of the Ethereum contract to connect.

The contract ABI comes from Ethereum.

Accepted Values:
A contract ABI value from Ethereum.
Default Value:
None

Test Connection

Function:
Makes sure the specified Ethereum account is correct.