Target Repository Configuration (SharePoint) - Adobe Sign Download Agreement

SharePoint

Function:

Specifies the access token that connects to your SharePoint site.

Accepted Values:

A list of access tokens configured for your environment.

Default Value:

None

Example:

Refer to:

• (Example) Create a SharePoint Access Token

Add Token

Opens this Screen:

Access Token for SharePoint

Function of this Screen:

Configure an access token to connect to SharePoint.

Example:

Refer to:

• (Example) Create a SharePoint Access Token

Site

Function:

Specifies the URL for your SharePoint site.

Accepted Values:

A valid SharePoint site URL.

Default Value:

None

Accepts Process Data Variables:

Yes

Example:

• http://[machine name]:[port]/sites/[site name]

  Note: You must include the /sites in the Site URL for the site to be created successfully.
• Form Based Applications – SharePoint Data Source

Upload Files To

Function:

Specifies whether to upload files to a SharePoint list or library.

Accepted Values:

• List Item - Lets you upload files in a SharePoint list.
• Document Library - Lets you upload files in a SharePoint library.

Default Value:

Document Library

List/Library

Function:

Specifies the name of the SharePoint library or list.

Accepted Values:

A valid SharePoint library name or list name.

Default Value:

None

Accepts Process Data Variables:

Yes

Choose Folder Path

Function:

Specifies the name of the target folder.

To Open this Field:

1. On the Target Repository Configuration screen, in the Upload Files To field, select Document Library.

Accepted Values:

The name of a folder in your repository.

Default Value:

None

Existing Folder ID

Function:

Specifies the ID of the folder the activity uses when the process runs.

To Open this Field:

1. On the Target Repository Configuration screen, in the Upload Files To field, select Document Library.

Accepted Values:

A valid folder ID.

Default Value:

None

Accepts Process Data Variables:

Yes

Create New Folder

Function:

Specifies that a new folder is created for the file by the process.

To Open this Field:

1. On the Target Repository Configuration screen, in the Upload Files To field, select Document Library.

Accepted Values:

• Deselected - The activity does not create a new folder.
• Selected - The activity creates a new folder.

Default Value:

Deselected

Accepts Process Data Variables:

No

Create New Folder Name

Function:

Specifies the name the process gives to the folder the process creates.

To Open this Field:

1. On the Target Repository Configuration screen, in the Upload Files To field, select Document Library.

Accepted Values:

• One line of text that can have spaces.
• A process data variable.

Default Value:

None

Accepts Process Data Variables:

Yes

Overwrite If File Exists

Function:

Specifies if the activity replaces the file if it already exist with the same name at the specified target location.

To Open this Field:

1. On the Target Repository Configuration screen, in the Upload Files To field, select Document Library.

Accepted Values:

• Selected - The activity replaces the file if it exists with the same name at the target location.
• Deselected - The activity saves the file with a different name.

Default Value:

Deselected

List Item ID

Function:

Specifies the ID of a SharePoint list item.

To Open this Field:

1. On the Target Repository Configuration screen, in the Upload Files To field, select List Item.

Accepted Values:

The ID of your SharePoint list item.

Default Value:

None

Accepts Process Data Variables:

Yes

Store the Response ID in this Variable

Function:

Specifies the process data variable that contains the response ID for the document transfer.

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?