Description:

The Move Folder workflow step moves a SharePoint folder from a specified source path to a specified destination path.

The step provides configuration for:

• Specifying the BaseURL for the SharePoint site.
• Selecting an OAuth provider.
• Specifying the source path of the folder to be moved.
• Specifying the destination path for the folder.
• Storing the operation result in a FlowWright Variable or global variable.
• Routing the workflow through True or False return paths.

The step can be useful for:

• SharePoint folder organization
• Document lifecycle management
• Project folder management
• Archiving completed work
• Moving folders between processing stages
• Reorganizing customer or case folders
• Workflow-driven document management

The XML defines the step as a SharePoint process step named spmovefolder, with the display name Move Folder and the label Move a SharePoint folder. It is implemented by FlowWright.Workflow.dll in the FlowWright.Workflow.SpMoveFolder namespace.

Usage:

The Move Folder step is typically used when a workflow needs to reorganize an existing SharePoint folder based on workflow state or business rules.

A typical workflow can be structured as:

The source and destination paths can be supplied directly or determined dynamically from workflow data.

The spMoveFolder definition contains the SharePoint site BaseURL, OAuth provider, source folder path, destination folder path, and result-storage properties, together with True and False return paths.

To use this step, configure SharePoint with Flowwright OAuth connections.

A sample SharePoint OAuth configuration is included here for reference.

Typical Workflow Suggestions.

Move a Completed Project to an Archive

Use Move Folder after a project has completed its processing lifecycle.

For example, folders can be moved from an active project's location into an archive location.

Move Documents Between Processing Stages

Use SharePoint folders as workflow stages, and move a folder when processing reaches the next stage.

Project Folder Organization

Use the step to reorganize project folders when a project changes status.

The source and destination paths can be generated from workflow data.

Customer or Case Folder Management

Use Move Folder when a customer or case moves between business stages.

This approach can help maintain a structured SharePoint repository while the workflow manages the business process.

Archive Folders After Retention Processing

Use the step as part of an archival process.

This can be useful when completed workflow data needs to be moved into a separate SharePoint archive structure.

Dynamically Determine the Destination

Use workflow data to determine where the folder should be moved.

For example, the destination could be based on project status, customer, business unit, year, or another workflow value.

The XML exposes separate sourceFolderPath and destinationFolderPath inputs, allowing the workflow to specify both locations independently.

Handle Move Results

Use the True and False paths to distinguish successful and unsuccessful move operations.

Both return values are defined in the XML.

Example:

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

• Create a new definition called “spMoveFolderDef" and open the definition in designer mode. 
• Drag a “spMoveFolder” step to the canvas.
• Connect the dots between the “Start” and “spMoveFolder” steps, as shown above. 
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, Error, and Evaluate”. Depending on the step’s purpose, additional values are available for configuration. 
• Define a variable or a global variable to store the file path.
• Click the "spMoveFolder" step to configure its "Required" properties. Provide a name for the step. Enter the base URL of your SharePoint site. Select an OAuth provider from the dropdown list. Enter the source file path of the folder to move. Enter the destination path. Enter a variable or a global to store the result. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• 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. The process step should move the SharePoint folder from one location to another.

Tips:

• Verify the SharePoint BaseURL before executing the workflow.
• Select the correct OAuth provider.
• Verify that the source folder path identifies the intended folder.
• Verify that the destination path is valid for the SharePoint site.
• Make sure the destination does not conflict with an existing folder unless the intended SharePoint behavior supports that situation.
• Use Variables or Globals when source or destination paths are determined dynamically.
• Store the operation result in a clearly named Variable or Global.
• Use the False return path for appropriate error handling.
• Test the SharePoint authentication and folder paths before deploying the workflow.
• Consider downstream workflow activities that reference the original folder path.
• Update any workflow data or references that depend on the folder's previous location.
• Use consistent SharePoint folder structures when Move Folder is part of a document-management workflow.
• The XML does not define the exact path syntax or runtime move behavior, so verify these details against the FlowWright SharePoint implementation.

Notes:

• The step belongs to the SharePoint category. 
• The display name is Move Folder. 
• The step name is spmovefolder. 
• The step label is Move a SharePoint folder. 
• The namespace is FlowWright.Workflow.SpMoveFolder. 
• The step is implemented by FlowWright.Workflow.dll. 
• The step is defined as a Process step.
• The definition specifies two input connections and two output connections. 
• BaseURL is required.
• Select OAuth provider is required.
• The source path of the folder to be moved is required.
• The destination path of the folder to be moved is required.
• Storing the result in a Variable/Global is required. 
• The OAuth provider uses the SelOAuthProvider data type. 
• The string properties use the FlowWright.DataTypes.ClsTextBox implementation. 
• The step provides True and False return values. 
• The XML does not specify the exact SharePoint path syntax.
• The XML does not specify the exact structure of the result stored in the configured Variable or Global.
• The XML does not specify the runtime conditions that produce the True or False result.
• The XML does not document handling of authentication failures, SharePoint API errors, retries, timeouts, or cancellation behavior.

Recommended Workflow Pattern:

A useful pattern for the Move Folder step is to separate source identification, destination determination, SharePoint processing, and result handling.

This pattern provides a clear separation between deciding what to move, where to move it, and executing the SharePoint operation.

Definition Sample:

You may download the sample definition(s) from the link here and later import them (drag-and-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after the import. Then, save the definition to confirm the changes.

Click here to download the sample file.