Description:

The OneDriveRenameFolder step renames or moves a specified OneDrive folder. The step uses a configured OAuth provider to access OneDrive, identifies the folder by the configured folder path, specifies the new destination/name in the Renamed To property, and stores the result in a Variable or Global variable.

The step supports:

• Selecting an OAuth provider.
• Specifying the existing OneDrive folder path.
• Specifying the new folder path/name.
• Storing the result in a Variable or Global variable.
• Routing the workflow through True, False, and error connections.

Usage:

The Rename Folder step typically follows a workflow that determines a OneDrive folder needs to be renamed or moved to a different path.

A typical workflow pattern is:

Prepare/Validate → Rename Folder → Continue Process

The workflow supplies the OAuth provider, identifies the existing folder through folderPath, specifies the new value through renamedTo, and stores the operation result through resultJson.

The supplied example definition demonstrates this pattern using:

Start → Pre-Process → Rename Folder → Continue Process

with separate False, True, and error paths.

To use this step, you must configure OneDrive in FlowWright.

The Windows Live OAuth configuration is included here for reference. 

Typical Workflow Suggestions:

Rename a Project Folder

Use the step when a project folder needs to be renamed as the project progresses through workflow stages.

Example:

Project Setup → Rename Folder → Continue Project

For example, you could rename a folder initially created for an active project when it reaches a new stage.

Rename a Folder After Processing Completes

Use this step to change a folder's name after workflow processing finishes.

Example:

Process Files → Rename Folder → Complete Workflow

This lets the folder name reflect the workflow's next state.

Organize Completed Workflow Folders

Use the step to rename folders as part of a document-management workflow.

Example:

Complete Documents → Rename Folder → Archive Processing

A workflow can use a consistent naming convention to distinguish folders that have completed processing.

Rename a Folder Based on Workflow Data

Use workflow Variables or Globals to construct the value supplied to the folder path or renamed-to property when dynamic naming is appropriate.

Example:

Get Project Information → Build Folder Name → Rename Folder

For example, a workflow could construct a destination such as a project-specific folder name before executing the Rename Folder step.

The XML defines both folder path and renamed-to values as strings, so you can configure them as text inputs.

Rename Folders After Approval

Use the step when folder naming should change after an approval process.

Example:

Submit Request → Approval → Rename Folder → Notify User

This can provide a workflow-driven distinction between folders associated with pending and approved work.

Rename a Folder as Part of a Document Lifecycle

Use the step as one activity within a larger document-management process.

Example:

Create Documents → Review → Approval → Rename Folder → Complete

The folder name can be changed when the workflow reaches the appropriate lifecycle stage.

Separate Successful and Unsuccessful Operations

Use the True and False paths to control what happens after the rename operation.

Example:

Rename Folder → True: Continue / False: Alternate Processing

This lets the workflow follow different paths based on the operation's result.

Add Dedicated Error Handling

The supplied sample workflow demonstrates a separate error connection from the Rename Folder step to a Log Error placeholder.

A practical pattern is:

Rename Folder → error → Log Error → Notify Administrator

This keeps error-handling logic separate from the normal workflow path.

Notify an Administrator When Renaming Fails

Use the False or error path to direct the workflow toward an administrator notification process.

Example:

Rename Folder → Failure → Notify Administrator

The supplied definition specifically includes a Notify Administrator placeholder connected from the Rename Folder step's False path.

Store the Rename Result for Reuse

The resultJson property is specifically provided to store the operation result in a Variable or Global variable.

A typical pattern is:

Rename Folder → Store Result → Subsequent Processing

This allows later activities to access the value produced by the operation.

Use a Pre-Processing Stage

A workflow can prepare or validate data before attempting the OneDrive operation.

Example:

Pre-Process → Rename Folder → Continue Process

The supplied OneDriveRenameFolderDef example uses a Pre-Process placeholder immediately before the Rename Folder step.

Example:

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

• Create a new definition called “OneDriveRenameFolderDef” and open the definition in designer mode. 
• Drag a “OneDriveRenameFolder” step to the canvas. 
• Connect the dots between the “Start” and “OneDriveRenameFolder” 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. 
• Click the “OneDriveRenameFolder” step to configure its “Required” properties. Provide a name for the step. Select “WindowsLive” from the OAuth providers drop-down list. Provide the folder path to rename. Provide the new folder name. Provide a variable or a global to store the result after execution. Click the Save button. Note: Click the "AI Predict" button so Copilot can add new process steps that match your process description. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Configure 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 and click the Rename Folder step to view its properties. When the workflow reaches the step, FlowWright uses the configured OAuth provider and folder path information to perform the configured rename operation. The result is stored using the Variable or Global specified by resultJson. Inspect the workflow paths after execution:
  • True for the successful continuation path.
  • False for the alternate path.
  • Error for dedicated error handling when configured.

Tips:

• Verify the OAuth provider. The OAuth provider is required, so make sure the selected provider is available and correctly configured in the target environment. 
• Verify the existing folder path. Make sure it folderPath identifies the intended OneDrive folder.
• Use a clear naming convention. Consistent folder names make automated document-management workflows easier to understand and maintain.
• Review the renamed-to value carefully. The renamedTo property determines the new value supplied to the operation. Confirm that it represents the intended destination/name. 
• Use Variables or Globals for dynamic values. Where appropriate, construct folder paths from workflow data rather than hard-coding environment-specific values.
• Test with representative folders. Before deploying a workflow, test the operation against folders that reflect the expected production structure.
• Use the True path deliberately. Connect the True path to the activity that should follow a successful rename operation.
• Provide failure handling. Use the False path for an alternate process and/or an error connection for dedicated error handling.
• Consider administrator notification. For important OneDrive operations, route failures to logging or notification activities.
• Store the result meaningfully. Use a descriptive Variable or Global name for resultJson so that later workflow designers understand its purpose.
• Do not assume overwrite behavior. The XML defines the folder path and renamed-to values, but does not specify what happens if the target name/path already exists. Verify this behavior in the deployed implementation.
• Do not assume path semantics. The XML identifies folderPath and renamedTo as strings but does not document the exact OneDrive path syntax or whether the values are interpreted as names, paths, or both.
• Review environment-specific configuration. OAuth providers and OneDrive folder locations may differ between development, test, and production environments.

Notes:

Definition Sample:

The supplied OneDriveRenameFolderDef provides a useful example of configuring the step within a workflow.

Before importing or executing a similar definition, verify:

1. The OAuth provider referenced by the definition is available in the target environment.
2. The folderPath identifies the intended OneDrive folder.
3. The renamedTo value matches the target OneDrive location.
4. The Variable or Global used by resultJson exists or is configured appropriately.
5. The True, False, and error connections lead to the intended activities.
6. Any administrator notification or error logging activities are configured for the target environment.
7. Environment-specific OneDrive paths have been reviewed.
8. The workflow is saved before creating and executing an instance.

The supplied definition illustrates a particularly useful production-oriented pattern:

Start → Pre-Process → Rename Folder → Continue Process

with:

False → Notify Administrator

and:

error → Log Error

This makes the sample useful not only for demonstrating the Rename Folder step itself, but also for showing how normal, alternate, and error workflow paths can be organized around a OneDrive operation.

Click here to download the sample file.