Source Repository Configuration (SharePoint) - Create Ticket Comment

Specifies the original, or source, location for your attachment files on SharePoint in the Create Ticket Comment activity.

Figure: Source Repository Configuration screen (SharePoint)

Source Repository Configuration screen SharePoint

Examples

Prerequisites

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?

How to Start

  1. On the Application Explorer screen, do one of these:
  2. Do one of these:
    • Add an activity:
      1. In the Process Builder, in the Activity Library, open the Zendesk Zendesk icon tab.
      2. On the Zendesk Zendesk icon tab, drag the Create Ticket Comment Create Ticket Comment icon activity onto your process.
    • Change an activity:
      1. In your process, double-click your activity.
  3. On the Source Repository screen, click SharePoint SharePoint icon.
  4. Click Source Detail Configuration Source Detail Configuration icon.

Fields

Field Name Definition

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:

Add Token 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:

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:

Upload Files To
Function:
Specifies whether to download files from a SharePoint list or library.
Accepted Values:
  • List Item - Lets you download files from a SharePoint list.
  • Document Library - Lets you download files from a SharePoint library.
Default Value:
Document Library
Limitations:

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

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

The option to use a SharePoint list or library is available in these releases:

List Item ID
Function:
Specifies the ID of a SharePoint list item.
To Open this Field:
  1. On the Source 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
Limitations:

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

Folder Path
Function:
Specifies the path of the folder.
To Open this Field:
  1. On the Source Repository Configuration screen, in the Upload Files To field, select Document Library.
Accepted Values:
  • Choose Folder Path - Specifies an absolute path for the folder.
  • Dynamic Folder Path - Specifies a process data variable that stores the relative path of the folder.
Default Value:
Dynamic Folder Path
Example:
  • ${HomeDirectory}\sample2.doc
  • MyFolder1/Sample3.doc

Also refer to:

Limitations:

The option to use a SharePoint folder path in a document library is available in these releases:

File Name/Filter
Function:
Specifies the file name or a set of files expressed with the filter expression to search within the specified source location.
Accepted Values:
  • File Name - Specifies the name of the file in your storage source location.
  • Filter - Specifies a file name or a filter string that uses asterisks (*) as wildcards.
Default Value:
Filter
Accepts Process Data Variables:
Yes
Example:
These are some examples of filter expressions:
  • *.* - All files are searched.
  • *.txt - The files that have the .txt file extension are searched.
  • *.pdf - The files that have the .pdf file extension are searched.
  • MyFile.* - All files start with MyFile are searched.
  • *[part of file name]* - All files that contain the specified part of file name are searched.
  • *.xml - The files that have the .xml file extension are searched.
  • *.doc - The files that have the .doc file extension are searched.
  • MyFile.xml - Only the specific file MyFile.xml is searched.

The filter action is done at the source location specified in the activity.

Limitations:

The File Name/Filter option is available in these releases:

Recursive
Function:
Specifies if the activity's action — such as copy, upload, or delete — is recursive. In other words, it specifies if the activity does the action again in the subfolders of the target location
Accepted Values:
  • Deselected - The activity does the action only on the files in the specified source folder. There is no effect on files in subfolders.
  • Selected - The activity does the action on the files in the specified source folder, as well as the files in the subfolders.
Default Value:
Deselected