Upload Document activity

An activity that uploads a document to Salesforce.

Configure the Update Multiple Entities activity

To configure the Upload Document activity, do the procedure in this topic.

Examples

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

Good to Know

To send an e-mail notification, click Advanced > E-mail Notifications .
For more information, refer to Configure E-mail Notifications for Any Activity.
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?
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?

How to Start

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 Salesforce tab.
  2. On the Salesforce tab, drag the Upload Document activity onto your process.
- Change an activity:
  1. In your process, double-click your activity.

General Configuration

Specifies the basic information for a CRM activity.

Screen

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
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

Upload Document Configuration

Specifies how to upload your document to Salesforce.

Fields

Field Name	Definition
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
Add Token	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 Name	Function: Specifies the name of the document you want to show in Salesforce. Accepted Values: A valid document name. Default Value: None Accepts Process Data Variables: Yes
Document Description	Function: A description of your document. Accepted Values: More than one line of text. Default Value: None Accepts Process Data Variables: Yes
Document File Path	Function: Specifies the absolute path and file name of your document. Accepted Values: An absolute path and document name on the AgilePoint Server or SharePoint Server. Note: The size limit for any document you upload is 5 MB. You can only upload one document. Default Value: None Accepts Process Data Variables: Yes Example: c:\My Documents\sample1.doc ${HomeDirectory}\sample2.doc http://demo3:8000/DocumentLib1/sample3.doc
Select Folder	Function: Specifies the Salesforce folder name from the list. Accepted Values: A valid Salesforce folder. Default Value: None When you select the Salesforce access token, the folder name shows in the Select Folder field. Accepts Process Data Variables: Yes
Folder ID	Function: Specifies the ID of the folder from Salesforce that contains the document. Accepted Values: A valid Salesforce folder ID. Default Value: None When you select the folder, the folder ID shows in the Folder ID field. 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?
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, 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?