Download Document activity

Display Name

Function:

Specifies the activity name that shows in your process.

Accepted Values:

One line of text that can have spaces.

Default Value:

None

Accepts Process Data Variables:

No

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:

Specifies an optional text description for your activity.

Accepted Values:

More than one line of text.

Default Value:

None

Accepts Process Data Variables:

No

Connection Timeout (Seconds)

Function:

Specifies the number of seconds permitted to complete an action before the connection stops.

Accepted Values:

An integer, representing a number of seconds.

Default Value:

600

Accepts Process Data Variables:

No

Salesforce

Function:

Specifies the access token that connects to your Salesforce application.

Accepted Values:

A list of access tokens configured for your environment.

Default Value:

None

Accepts Process Data Variables:

No

Example:

Refer to:

• (Example) How to Get the Access Token Credentials from Salesforce

Create

Opens this Screen:

Access Token for Salesforce

Function of this Screen:

Configure an access token to connect to Salesforce.

Example:

Refer to:

• (Example) How to Get the Access Token Credentials from Salesforce

Document ID

Function:

Specifies the ID of your document.

The document ID is supplied by Salesforce. The document ID is an identifier used to track a uploaded document.

Accepted Values:

A valid document ID.

Default Value:

None

Accepts Process Data Variables:

Yes

Limitations:

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?

Local Path

Function:

Specifies the location of the file system folder on the local computer where the activity does an action, such as uploading or downloading files.

This setting gives the source location for the files to be uploaded and the target location for the files to be downloaded.

Accepted Values:

A file path relative to the AgilePoint Server application's root directory.

Default Value:

None

Accepts Process Data Variables:

Yes

Example:

• If AgilePoint Server is installed at:

  c:\Inetpub\wwwroot\AgilePointServer\

  And, the file once downloaded is to be located at:

  c:\Inetpub\wwwroot\AgilePointServer\files\MyFile.txt

  Then, the LocalPath property must be set to the following value:

  files

• If AgilePoint Server is installed at:

  c:\Inetpub\wwwroot\AgilePointServer\

  And, the file once downloaded is to be located at:

  c:\Inetpub\wwwroot\AgilePointServer\files\temp\MyFile.txt

  Then, the LocalPath property must be set to the following value:

  files\temp

Store the Document ID in Schema Node

Function:

Specifies the process data variable that contains the document ID.

Accepted Values:

A process data variable that accepts an alphanumeric string with no spaces or special characters.

Default Value:

None

Accepts Process Data Variables:

Yes

Limitations:

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?