Description:

The Move Process Definition To Folder step enables a FlowWright workflow to relocate an existing process definition into a selected process folder at runtime.

Rather than requiring administrators to manually reorganize process definitions, this step allows workflows to perform folder management automatically based on business events, deployment processes, governance policies, or lifecycle milestones.

The workflow specifies the process definition to move and the destination process folder. When the move operation completes successfully, workflow execution follows the True path. If the move operation cannot be completed, the workflow follows the False path, allowing appropriate error handling or notification.

Typical uses include:

• Organizing newly imported process definitions
• Moving approved workflows into production folders
• Archiving obsolete process definitions
• Categorizing workflows by department
• Automating release management
• Supporting governance and compliance initiatives
• Maintaining structured process repositories

This step simplifies process administration by allowing folder organization to become part of an automated workflow rather than a manual administrative task.

Usage:

The Move Process Definition To Folder step is typically used within administrative, deployment, migration, or governance workflows.

During execution:

1. Read the configured process definition identifier.
2. Locate the selected destination process folder.
3. Move the process definition into the specified folder.
4. Continue workflow execution through either the True or False return path.

A typical workflow might look like this:

Typical workflow scenarios include:

• Automatically organizing imported process definitions
• Moving approved workflows into production folders
• Relocating workflows after QA approval
• Archiving retired process definitions
• Organizing workflows by business unit
• Supporting automated deployment pipelines
• Managing workflow lifecycle transitions

Example:

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

• Create a new definition called “moveProcessDefinitionToFolder” and open the definition in designer mode. 
• Drag a “moveProcessDefinitionToFolder” step to the canvas. 
• Connect the dots between the “Start” and “moveProcessDefinitionToFolder” steps, as shown above. 
• Click the "moveProcessDefinitionToFolder" step to configure its "Required" properties. Provide a name for the step and the Process Definition GUID. Click the button to select the target folder on the application server, then click Save. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the button to select the destination folder on the application server. A configuration pop-up window appears. Select the destination folder, or right-click to create a new folder and enter a name. 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 in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. Click the process step to view its properties. The step should move the process definition to the target folder on the application server. 

Tips:

• Organize process definitions into folders that reflect business units, environments, or functional areas.
• Store the process definition identifier in a workflow variable when moving dynamically selected workflows.
• Use this step as part of automated deployment or release workflows to reduce manual administration.
• Verify that the destination folder exists before attempting the move.
• Route the False path to logging or notification activities to simplify troubleshooting.
• Ensure the executing account has permission to modify process definitions and process folders.
• Combine this step with Import Process Definition, Publish Process Definition, Get Process Definition ID, Get Configuration Settings, or Send Email steps to automate workflow lifecycle management.

Notes:

• A valid process definition identifier is required before the step can execute.
• A destination process folder must be selected.
• The step relocates the process definition within the FlowWright repository; it does not modify the process definition itself.
• Successful execution depends on the availability of the destination folder and appropriate user permissions.
• Both the True and False return paths should be implemented to provide complete workflow handling.
• Execution details and folder movement operations are recorded in the FlowWright workflow execution log.

Move Process Definition To Folder vs. Get Process Definition ID:

Both workflow steps work with process definitions, but they perform different functions.

As a general guideline:

• Use Move Process Definition To Folder when workflows need to automatically organize or relocate process definitions within the FlowWright repository.
• Use Get Process Definition ID when workflows need to retrieve a process definition identifier for subsequent workflow operations.

Definition Sample:

You may download the sample workflow definition from the link provided and import it into your FlowWright environment.

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

• Process definition identifier
• Destination process folder
• Success and failure workflow branches
• Appropriate administrative permissions
• Notification or deployment activities

After verifying the configuration, save and publish the workflow before execution.

Click here to download the sample file.