Access Token for WCF Service

Configure an access token to connect to a WCF service.

Figure: WCF Access Token Configuration screen

WCF Access Token Configuration screen

Background and Setup

Good to Know

  • In most cases, you can use a global access token or an application level access token:
    • Global access tokens are shared across all users and applications. If you want all process designers and form 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 form 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.
  • The WCF access token supports more than one endpoint in one WCF service.

    This feature requires AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v7.0 Software Update 1 or higher.

  • Documentation for Integrations with Third-Party, External, or Open Source Technologies

    The highest priority for AgilePoint NX Product Documentation is accuracy. Whenever feasible, AgilePoint provides input details, business rules, or example values for third-party integrations. These can include any technology that is not native to AgilePoint NX, such as Salesforce, Active Directory, or REST. However this information is subject to change without notice to AgilePoint. Because we can not guarantee the accuracy of this information, the details provided for third-party product input values, as well as examples for third-party product integrations, are limited in the AgilePoint documentation. It is the responsibility of third-party vendors to provide documentation related to these aspects of their software and services.

    For examples of use case implementations or configuration field input values for third-party products, AgilePoint recommends these resources:

    • AgilePoint Community Forums - An AgilePoint-moderated, crowd-sourcing user forum where you can ask questions about specific techniques, the solutions to use cases, workarounds, or other topics that may not be covered in the Product Documentation.
    • Professional Services - If you can not find the information you need for your specific business problem, mentoring is available through AgilePoint Professional Services.
    • Personalized Training - AgilePoint can provide personalized training for your organization. To request personalized training, contact AgilePoint Sales.
    • Third-Party Vendor Documentation - Whenever feasible, AgilePoint provides links to third-party vendor documentation.

      This does not include technology standards or protocols, such as JavaScript, REST, or FTP. Resources for these technical standards are publicly available on the Internet.

Fields

Field Name Definition

Token Name

Function:
Specifies the unique name for your connection to WCF service.
Accepted Values:
A text string that can have letters, numbers, and spaces
Default Value:
None

Description

Function:
A description for your access token.
Accepted Values:
More than one line of text.
Default Value:
None
Example:
Refer to:

Service URL

Function:
Specifies the URL of your WCF service.
Accepted Values:
A valid WCF service URL.
Default Value:
None
Accepts Process Data Variables:
No
Example:
  • http://demo3:80/agilepointserver/admin.sbc?wsdl

    In this example, SBC is the extension name for the WCF services, and ?WSDL is the query string that contains all the information such as method names of the specific WCF service.

    However, you can leave the extension name in the URL, as follows:

    http://demo3:80/agilepointserver/admin?wsdl

Load

Function:
Gets the data from the WCF service URL.

Binding

Function:
Specifies the data binding you want to use.

The binding defines the communication details required to connect to the WCF endpoint.

Accepted Values:
  • WSHttpBinding
  • NetTcpBinding
  • BasicHttpBinding
Default Value:
None

Endpoint

Function:
Specifies the WCF service endpoint you want to connect.

Endpoints provide access to the WCF service data.

Accepted Values:
A list of Endpoints populated from the WSDL file of the WCF service.
Default Value:
None
Example:
NetTcpBinding_IWCFWorkflowService

User Name

Function:
Specifies the user name for WCF service authentication.
Accepted Values:
A valid user name.
Default Value:
None
Accepts Process Data Variables:
No
Example:
[Example]

Domain

Function:
The authentication domain for WCF service.
Accepted Values:
A valid domain.
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
Example:
Refer to:

Test Connection

Function:
Makes sure the specified WCF service account is correct.

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