PowerPoint > Target Repository > File System

Specifies the target location for your output Microsoft PowerPoint file on your AgilePoint Server machine with the PowerPoint activity.

Figure: Target Repository Configuration screen (File System)

Target Repository Configuration screen File System

Prerequisites

How to Start

Fields

Field NameDefinition

Folder Path

Function:
Specifies the name of the target folder.
Accepted Values:
The absolute path of a folder on your AgilePoint Server machine.
Default Value:
None

Create New Folder

Function:
Specifies that a new folder is created for the file by the process.
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
Example:

Create New Folder Name

Function:
Specifies the name the process gives to the folder the process creates.
Accepted Values:
Default Value:
None
Accepts Process Data Variables:
Yes
Example:
Refer to:

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.
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:
Selected

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