Description:

The BoxCreateFolder step is used to create a new folder in Box from within a FlowWright workflow.

The step provides True and False return paths, allowing subsequent workflow processing to respond to the result of the folder creation operation.

Usage:

The BoxCreateFolder step can be used whenever a workflow needs to create a new folder in Box as part of an automated process.

A typical workflow pattern is:

Determine Folder Information → Create Box Folder → Store Result → Continue Processing

The workflow can specify the destination path and, when applicable, a parent folder ID. The operation result can be stored in a Variable/Global for use by subsequent workflow steps.

For example, a workflow processing a new project could create a dedicated Box folder before uploading project documents.

To use this step, you must first configure Dropbox in the FlowWright application. Then, go to the Integrate—Connections—OAuth page to create a new OAuth source. 

A sample OAuth configuration is provided for reference. 

Typical Workflow Suggestions:

Create a Project Folder

Use BoxCreateFolder when a workflow starts processing a new project and needs a dedicated Box folder.

For example:

Create Project → Create Box Folder → Upload Project Documents → Continue

The folder path can be generated from project information available in the workflow.

Create a Customer-Specific Folder

Use the step to create a Box folder for a new customer as part of an onboarding workflow.

For example:

Customer Onboarding → Create Customer Folder → Store Result → Continue

The destination path can be supplied dynamically based on the customer information maintained by the workflow.

Create a Folder Before Uploading Files

Use BoxCreateFolder before Box file-upload operations when documents need to be organized in a newly created folder.

For example:

Prepare Documents → Create Box Folder → Upload Files → Complete

The workflow can create the required folder first, then use subsequent Box operations to place documents in it.

Create a Folder for a Workflow Instance

Use the step to create a dedicated Box folder associated with a particular workflow instance.

For example:

Start Process → Determine Instance Folder → Create Box Folder → Process Documents

A Variable/Global can be used to construct the destination path from workflow information.

Build a Hierarchical Box Folder Structure

Use BoxCreateFolder to create folders within an existing Box folder structure.

For example:

Identify Parent Folder → Create Child Folder → Upload Content

The optional Parent folder ID input can be supplied when the workflow needs to associate the new folder with a specific parent folder.

Example:

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

• Create a new process definition named “BoxCreateFolderDef” and open it in designer mode. 
• Drag a “BoxCreateFolder” step to the canvas.
• Connect the dots between the “Start” and “BoxCreateFolder” 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 result.
• Click the "BoxCreateFolder" step to configure its "Required" properties. Provide a name for the step. Select the “Box” OAuth connection provider. Specify the path where the folder will be created. Provide a variable or global reference to store the result. Click the Save button. Note: Click the "AI Predict" button for Copilot to add new process steps that match your process description. 
   

• Click the "BoxCreateFolder" step to configure its "Optional" properties. Enter the parent folder ID. Then click the Save button. 

• 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 below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. When the workflow reaches the BoxCreateFolder step, FlowWright uses the selected OAuth provider to access Box and uses the supplied folder path and optional parent folder ID as part of the folder creation operation. The result is stored in the Variable/Global specified by Store result in Variable/Global. The workflow then follows the True or False return path based on the result of the operation. Click the process step to view its properties. The step should create a new directory in the box. 

Tips:

• Select the correct OAuth provider: Ensure that the selected provider has access to the Box location where the folder is being created.
• Use a meaningful folder path: A consistent folder naming convention makes automated Box content easier to organize.
• Use the Parent folder ID when appropriate: When creating a folder within an existing Box hierarchy, provide the appropriate parent folder ID.
• Use Variables/Globals for dynamic paths: This allows folder names and locations to be generated from workflow data.
• Store the operation result: Use the result Variable/Global when subsequent workflow logic needs to reference the outcome.
• Handle both return paths: Connect the True and False outputs to appropriate subsequent processing.
• Create the folder before uploading documents: When a workflow needs to populate a newly created folder, execute the folder creation step before the corresponding Box upload steps.

Definition Sample:

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

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

Click here to download the sample file.