Description:

The FTPCreateFolder workflow step creates a folder in the specified location on an FTP server using the selected FTP connection.

The step supports:

• Selecting a configured FTP connection.
• Specifying the destination path for the folder.
• Creating FTP folders as part of a workflow.
• Organizing files into workflow-specific FTP locations.
• Preparing an FTP directory before uploading files.
• Continuing workflow processing through the True return path.
• Handling an unsuccessful operation through the False return path.

Usage:

The FTPCreateFolder step is typically placed before workflow activities that need to upload files or otherwise work with a folder on an FTP server.

The workflow selects the FTP connection and provides the destination folder path. The FTPCreateFolder step then performs the folder-creation operation.

A typical workflow pattern is:

Prepare Folder → FTPCreateFolder → Upload File

The step can be used by later workflow activities to:

• Prepare an FTP location for file uploads.
• Create folders for individual workflow instances.
• Organize files by customer or transaction.
• Create date-based processing folders.
• Prepare folders for integration files.
• Separate incoming and outgoing files.
• Continue processing after folder creation.
• Handle folder-creation failures through the False path.

To use this step, you must configure an FTP connection in the FlowWright application. To do so, go to the Integrate > Connections > FTP page and create a new FTP source. 

A sample FTP connection configuration is provided here for reference.

Typical Workflow Suggestions:

Create a Folder Before Uploading Files

Use FTPCreateFolder to prepare an FTP destination before uploading files.

Example:

Start → FTPCreateFolder → FTPSendFile → Complete

You can create the folder before the workflow attempts to upload the required files.

Create a Customer-Specific Folder

Use the destination folder path to organize files by customer or business entity.

Example:

Get Customer Data → FTPCreateFolder → FTPSendFile

A workflow can determine the appropriate destination path and then create the folder before transferring customer-related files.

Create a Transaction Folder

Use the step to create a dedicated FTP folder for a transaction or workflow instance.

Example:

Get Transaction Details → FTPCreateFolder → Generate Files → FTPSendFile

This pattern can provide a separate location for files associated with an individual transaction.

Create Date-Based Processing Folders

Use FTPCreateFolder to prepare folders associated with a processing date.

Example:

Determine Processing Date → FTPCreateFolder → Upload Files

A workflow can use a destination path representing a processing period or date.

The XML defines the destination as a string property, but it does not specify how dynamic expressions are resolved. Verify the supported FlowWright configuration syntax when implementing dynamic paths.

Prepare an Integration Folder

Use FTPCreateFolder before placing files into a folder expected by an external integration.

Example:

Prepare Integration Data → FTPCreateFolder → FTPSendFile → External Processing

This pattern ensures the intended FTP location is prepared before the file-transfer operation.

Create an Export Folder

Use the step to create an FTP destination for generated reports or exported data.

Example:

Generate Report → FTPCreateFolder → FTPSendFile → Notify User

The workflow can create the destination before transferring the generated report.

Organize Files by Workflow Instance

Use a separate FTP folder for each workflow instance when files need to be grouped together.

Example:

Start → FTPCreateFolder → Generate Documents → FTPSendFile → Complete

This can provide a structured destination for files produced during a workflow execution.

Create an Archive Folder

Use FTPCreateFolder as part of an archiving workflow.

Example:

Identify Files → FTPCreateFolder → Move/Upload Files → Complete

The step can prepare the destination used by subsequent archive-related processing.

The XML only defines folder creation; it does not define file movement or archiving behavior. Those operations would need to be performed by other workflow activities.

Handle Folder Creation Failures

Connect the False return path to an appropriate error-handling activity.

Example:

FTPCreateFolder

True → Upload File

False → Log Error → Notify Administrator

This allows the workflow to distinguish between successful and unsuccessful folder creation.

Create a Folder for Batch Processing

Use FTPCreateFolder at the beginning of a batch-processing workflow.

Example:

Start → FTPCreateFolder → Generate Batch Files → FTPSendFile → Complete

The folder provides the destination for files generated during the batch.

Prepare Environment-Specific FTP Locations

Use the Select FTP property to identify the configured FTP connection used by the workflow.

Example:

Prepare Files → FTPCreateFolder → FTPSendFile

Configure the FTP connection for the environment where the workflow is deployed.

The XML confirms that the connection property uses the ClsFTPConnections data type.

Create a Folder Before Multiple Uploads

Create the destination once and then use it for multiple file-transfer operations.

Example:

FTPCreateFolder → FTPSendFile → FTPSendFile → FTPSendFile → Complete

This is useful when several related files need to be placed in the same FTP location.

Conditional Folder Creation

Use the True and False paths to control subsequent workflow processing.

Example:

Check Processing Requirement → FTPCreateFolder

True → Upload Files

False → Error Handling

This allows the workflow to define different actions based on the result returned by the folder-creation step.

Example:

Let’s build and execute the “ftpCreateFolderDef” example.     

• Create a new process definition named “ftpCreateFolderDef” and open it in designer mode. 
• Drag an “ftpCreateFolder” step to the canvas.
• Connect the dots between the “Start” and the “ftpCreateFolder” steps, as shown above.
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, you can configure additional values.
• Define a variable or a global to store the FTP folder path. 
• Click the “ftpCreateFolder” step to configure its “Required” properties. Provide a name for the step. Select the FTP connection from the drop-down list, then click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• Click the “ftpCreateFolder” step to configure its “Optional” properties. Enter the path for the FTP folder. Click the Save button.  

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance and click the process step to view its properties. When the workflow reaches the FTPCreateFolder step, FlowWright uses the selected FTP connection and configured destination folder path for the operation. After the operation completes, the workflow follows the True or False return path according to the result. The XML explicitly defines these two return values.

Tips:

• Verify that the configured FTP connection points to the intended FTP server.
• Verify the destination folder path before executing the workflow.
• Use meaningful step names that identify the purpose of the folder.
• Test the workflow with a non-critical FTP location before deploying it to production.
• Confirm that the FTP account has the required permissions to create folders.
• Connect the True path to the activity that should execute after successful folder creation.
• Connect the False path to appropriate error handling or alternate processing.
• Test the workflow when the destination folder does not already exist.
• Test the workflow when the destination folder already exists.
• Test the workflow when the FTP connection is unavailable.
• Test the workflow when the FTP account does not have sufficient permissions.
• Test representative folder paths used by the workflow.
• Use environment-appropriate FTP connections when moving workflows between environments.
• Keep dynamically constructed folder paths consistent and predictable.
• Log important folder-creation operations when traceability is required.
• If multiple files will be uploaded to the same folder, create the folder before the upload activities.
• Verify the resulting FTP folder structure after workflow execution.
• Do not assume that the step creates missing parent directories unless this behavior has been confirmed.
• Do not assume that an existing folder is treated as a successful operation unless confirmed by the FlowWright implementation.
• Do not assume retry, overwrite, recursive folder creation, or automatic cleanup behavior unless confirmed by the implementation.
• Test both the True and False paths independently.

Definition Sample:

You may download the sample definition from the link provided and later import it into your FlowWright Process Definition XML file or Form Definition HTML file page.

Note: Verify and complete any missing configuration after importing the sample, including:

• FTP connection.
• Destination folder path.
• Workflow Variable references, if used.
• Environment-specific FTP settings.
• Downstream True and False workflow paths.
• Error-handling configuration.
• FTP permissions.

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.