Adobe Sign Set Alternate Signer activity

An activity that configures a new signer to replace a signer.

Configure the Adobe Sign Set Alternate Signer activity

To configure the Adobe Sign Check Status activity, do the procedure in this topic.

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX Private Cloud or AgilePoint NX OnPremises v7.0 Software Update 1 or higher.

Good to Know

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
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?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the Digital Signature tab.
On the Digital Signature tab, drag the Adobe Sign Set Alternate Signer activity onto your process.

General Configuration

Specifies the basic settings for the Adobe Sign Set Alternate Singer activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
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

Field Name

Definition

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:

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

Adobe Sign Set Alternate Signer Configuration

Specifies information to assign an alternative signer for an agreement.

Fields

Field Name	Definition
Adobe Sign	Function: Specifies the access token that connects to your Adobe Sign environment. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Create	Opens this Screen: Access Token for Adobe Sign Function of this Screen: Configure an access token to connect to Adobe Sign.
Agreement ID	Function: Specifies a unique ID of the eSigned document to assign an alternative signer. Adobe Sign gives a unique ID for each agreement. Accepted Values: An agreement ID from Adobe Sign. 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?
Current Participant Email	Function: Specifies the e-mail address of the configured signer. Accepted Values: One line of text (a string) in email address format. Default Value: None Accepts Process Data Variables: Yes
Alternative Participant Email	Function: Specifies the e-mail address for a different signer if the configured signer can not complete the task. Accepted Values: One line of text (a string) in email address format. Default Value: None Accepts Process Data Variables: Yes
Message	Function: Specifies the content of the message for a new signer. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: Yes
Store the Participant ID	Function: Specifies a process data variable to store the participant ID from Adobe Sign. Accepted Values: A process data variable that accepts a numeric 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?