Source Repository Configuration (SFTP)

Specifies the original, or source, location for your files on SFTP in the Sertifi eSign Request activity.

Good to Know

Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?

On the Application Explorer screen, do one of these:
- Open a Process.
- Create a Process.
Do one of these:
- Add an activity:
  1. In the Process Builder, in the Activity Library, open the Digital Signature tab.
  2. On the Digital Signature tab, drag the Sertifi eSign Request activity onto your process.
- Change an activity:
  1. In your process, double-click your activity.
On the Source Repository screen, click SFTP .
Click Source Detail Configuration .

Field Name	Definition
SFTP	Function: Specifies the access token that connects to your SFTP server. Accepted Values: A list of access tokens configured for your environment. Default Value: None Accepts Process Data Variables: No
Add Token	Opens this Screen: Access Token for SFTP Function of this Screen: Configure an access token to connect to an SFTP service.
File Path	Function: Specifies the path of the file. Accepted Values: Choose File Path - Specifies an absolute path for the file. Dynamic File Path - Specifies a process data variable that stores the path for the file. Default Value: Dynamic File Path Accepts Process Data Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses 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, and 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?