Create Folder (Salesforce) activity

An activity that creates a folder in Salesforce.


Create Folder activity

Configure the Create Folder activity

To configure the Create Folder activity, do the procedure in this topic.

Examples

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In the Process Builder, in the Activity Library, open the Salesforce tab.

    Salesforce tab
  3. On the Salesforce tab, drag the Create Folder activity onto your process.

    Create Folder activity

General Configuration

Specifies the basic settings for the Create Folder activity.

Figure: General Configuration screen

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

Create Folder Configuration

Specifies the information for the new folder.

Figure: Create Folder Configuration screen

Create Folder Configuration screen

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:

Create Add Token icon

Opens this Screen:
Access Token for Salesforce
Function of this Screen:
Configure an access token to connect to Salesforce.
Example:
Refer to:

Folder Name

Function:
Specifies the name of a folder.
Accepted Values:
One line of text that can have spaces.
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?

Folder Unique Name

Function:
Specifies the unique name of a folder.
Accepted Values:
A valid unique name of a folder.

The name must start with a letter. You can use text with a letter, number, and underscore (_). The name cannot end with an underscore or have two underscores one after the other.

Default Value:
None
Accepts Process Data Variables:
Yes

Public Folder Access

Function:
Specifies the folder access rights.
Accepted Values:
  • ReadOnly - The Salesforce user can see the folder but cannot change the folder contents.
  • Read/Write - The Salesforce user can change the folder contents.
Default Value:
None
Accepts Process Data Variables:
Yes

Store Response Folder ID in This Variable

Function:
Specifies the process data variable that contains the folder ID from Salesforce.
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?