Box - Move a file

Box actions are currently unavailable in the APAC region and will be released soon.

See how to implement this action in a step-by-step solution: Automate your document approvals.

The Box - Move a file actionA tool for building the processes, logic, and direction within workflows. moves a file to from one folder to another folder in Box.

Before you start

What are variables?

Variables are placeholders that store information that changes each time the workflow runs or during execution of a workflow instance. To view a list of all variables that you can use in the workflow, access the Variables pane.

Data types of variables

The data types of variables are as follows:

Text: Text string (with optional default value)
Decimal: Integer numerical with a decimal point (with optional default value)
Integer: Integer numerical with no decimal (with optional default value)
Boolean: Yes or No (with optional default value)
DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
Collection: A variable that groups one or more related variables of the same type into an ordered list.

For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.

File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.

For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.

Note: Objects can't be created or modified in the Variables panel.

Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.

For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.

Note: You can assign only the variable type that a workflow expects. For example, if you want to capture a Date entry in a form, then you must create a variable of the DateTime type.

Classifications of variables

In Nintex Workflow Cloud, variables are classified as follows:

Workflow variable

Workflow variables include those that you create and define when you configure an action. These variables store values such as collections, path to files, workflow outputsVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., and other data for use throughout the workflow.

Start event variable

These variables capture data that are present when the workflow starts.
Range of Start event variables
Depending on the Start events you select, one or more of the following start event variables may be available.
- Form field variables capture data that user enters in the fields of a form. These variables are generated when you create a form control. An example is a variable that holds an email address entered into a web form (Nintex - Form).
- Start event context variables, such as an identifier for the selected object (app start events). These variables are passed to the workflow as Start event context variables. Example: an object variable called Workflow Initiator that corresponds to the user who triggered to start a workflow. (Available only in Nintex - Form start event)
- Variables with applied formulas are variables that hold calculated values based on the formula defined in the Formula builder. An example is a variable that holds the calculated number of days between two DateTime variables.
- Provided start event variables such as the names of new files that trigger the workflow to run (new file start events; these variables must be explicitly added for use later in the workflow). (Available only in start events using third-party connectors such as Salesforce and Box.)
- Custom start event variables that you create, such as files or data that you want to pass as inputsVariable to store a value or file when the workflow starts. Set up as a start event variable. to a Component workflowA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.. (Available only in Nintex - Component Workflow start event)
Context variable

These variables represent data that are related to the current workflow instanceAn occurrence of a workflow. such as Current date (DateTime), Current date and time (DateTime), Workflow instance ID (Text), Workflow name (Text), and Workflow ID (Text).

Form-based task variable

These variables capture data that are entered in forms as part of a Form-based task. The following form-based task variables are generated automatically when you configure the Form field for the action:

Form variables - Variables that correspond to controls that you add to a form. Form variables are used only when assignees respond to a task, wherein they select an outcome and fill in a form.
Form URL - A variable that contains the form URL that an assignee can use to access a form.
Task name (Form link) - A variable that contains a hyperlink to the form URL using the Task name.

Note:

Form variables for the Assign a task to multiple users action are found in the Task responses collection. To find the Task responses collection in the Insert variables panel or Variables panel, click the Task name or Action name for the Assign a task to multiple users action > Task name or Action name (Object) > Task responses collection.

The Variable category name can be:
- Task name: The name of the action that is defined in the Task name field.
- Action name: If a variable is inserted as the Task name, the Variable category name can be the default action name or custom name if the action was renamed.
The Task responses collection also includes the Task responder and Outcome variables.
You can use Form URL and Task name (Form link) variables only within the same action.
To access individual responses or form control values, use the Loop for each action.

How do I add variables to my workflow?

You can insert existing variables into configuration fields for workflow actions and you can create user-defined variables for use throughout your workflow. Depending on the selected start event, you may be able to add provided start event variables or create your own.

Insert a variable into an action field

Each field that accepts variables accommodates one or more methods for inserting variables. Some fields allow you to type ahead and select from a filtered list of existing variables while others require selection from a drop-down list or from the Insert variables dialog box.

In the Action configuration panel, do one of the following.

Select an existing variable from a filtered list:
1. In fields that accept variables, type [[.
2. Continue typing to filter the list of displayed variables.
3. Click the variable you want.
Select an existing variable from the drop-down list for the field.

Select a new or existing variable from the Insert variables dialog box:
1. Either click + Insert or click Add variable from the drop-down list.
  
  The Insert variables dialog box appears.
2. To create and insert a variable
  1. Click the Workflow tab.
  2. Click Create variable.
  3. For Name, type the internal name you want to use.
  4. For Type, select a variable type corresponding to the type of data you want to store.
    
    Variable types
    
    Text: Text string (with optional default value)
    
    Decimal: Integer numerical with a decimal point (with optional default value)
    
    Integer: Integer numerical with no decimal (with optional default value)
    
    Boolean: Yes or No (with optional default value)
    
    DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
    
    Collection: A variable that groups one or more related variables of the same type into an ordered list.
    
    For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
    
    File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
    
    Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
    
    For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
    
    Note: Objects can't be created or modified in the Variables panel.
    
    Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
    
    For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
  5. For Default value, if relevant, update the provided default value.
  6. For Component workflowsA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.: To mark the variable as a workflow outputVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., select the Output check box.
    
    For more information about these fields, see Toolbar.
  7. Click Create & insert.
  The new variable appears in the configuration field.

Create a user-defined variable

You can create user-defined variables from the action configuration panel when you're configuring a workflow action or from the toolbar of the workflow designer.

During action configuration

In the Action configuration panel, do one of the following.

Select an existing variable from a filtered list:
1. In fields that accept variables, type [[.
2. Continue typing to filter the list of displayed variables.
3. Click the variable you want.
Select an existing variable from the drop-down list for the field.

Select a new or existing variable from the Insert variables dialog box:
1. Either click + Insert or click Add variable from the drop-down list.
  
  The Insert variables dialog box appears.
2. To create and insert a variable
  1. Click the Workflow tab.
  2. Click Create variable.
  3. For Name, type the internal name you want to use.
  4. For Type, select a variable type corresponding to the type of data you want to store.
    
    Variable types
    
    Text: Text string (with optional default value)
    
    Decimal: Integer numerical with a decimal point (with optional default value)
    
    Integer: Integer numerical with no decimal (with optional default value)
    
    Boolean: Yes or No (with optional default value)
    
    DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
    
    Collection: A variable that groups one or more related variables of the same type into an ordered list.
    
    For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
    
    File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
    
    Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
    
    For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
    
    Note: Objects can't be created or modified in the Variables panel.
    
    Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
    
    For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
  5. For Default value, if relevant, update the provided default value.
  6. For Component workflowsA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.: To mark the variable as a workflow outputVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., select the Output check box.
    
    For more information about these fields, see Toolbar.
  7. Click Create & insert.
  The new variable appears in the configuration field.

From the toolbar

Click Variables.

The Variables panel appears, displaying the Workflow tab that is selected by default.
To create a variable
1. Click the Workflow tab.
2. Click Create variable.
3. For Name, type the internal name you want to use.
4. For Type, select a variable type corresponding to the type of data you want to store.
  Variable types
  
  Text: Text string (with optional default value)
  
  Decimal: Integer numerical with a decimal point (with optional default value)
  
  Integer: Integer numerical with no decimal (with optional default value)
  
  Boolean: Yes or No (with optional default value)
  
  DateTime: YYYY-MM-DD, HH:MM AM/PM (with optional default value)
  
  Collection: A variable that groups one or more related variables of the same type into an ordered list.
  
  For example, a collection variable named Company name can hold a list of names, such as Safalo, Nintex, and Drawloop.
  
  File: Path to a file. Use this variable type to attach files to email messages. A file path must start with the root folder and end with the file name. Example: /Draft/Contracts/ACME.docx
  
  Object: A variable that groups several related variables of any type into a hierarchical structure. Objects can contain other Objects.
  
  For example, an Object variable named Company can hold a list of parameters, such as Company name, Email, Address, and Phone number.
  
  Note: Objects can't be created or modified in the Variables panel.
  
  Collection of objects: A variable that groups a list of Objects of the same variable structure into a list.
  
  For example, a Collection of object variable named Company details can hold a series of objects, detailing Company name, Email, Address, and Phone number for each Company name Safalo, Nintex, and Drawloop.
5. For Default value, if relevant, update the provided default value.
6. For Component workflowsA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.: To mark the variable as a workflow outputVariable to store a value or file on completion of the workflow. Set up as a user-defined variable., select the check box for Output.
  
  For more information about these fields, see Toolbar.
7. Click Create.

Add a provided start event variable

Nintex provides start event variables for most third-party start events, such as Box - New file. If you add the provided variable, then you can use it later on in your workflow.

On the canvas, click Start event.

The configuration panel for Start event appears.
From the Start from drop-down box, select a connector.
From the Event drop-down box that appears, select an event.

The Source section appears.

Note: The Source section is available only for some events.
Click Add variables.

A drop-down list appears, displaying a list of provided variables.

Select the predefined variables that you want to add to your workflow.
Note:
- To select all variables, click Select All.
- If you know the variable and you want to find it faster, type the variable name in the Filter options field.
Click Add.

The Variables dialog box appears, displaying the variables you have selected.

Note: If you want to edit the selection of variables, hover over the variable, click , and then click Show Details. Edit the variable name in the Name field or click .

Create a start event variable (workflow inputVariable to store a value or file when the workflow starts. Set up as a start event variable.)

The Nintex - Component workflow start event allows you to create your own start event variables in the Start event configuration panel. You can use these variables to capture required workflow inputs (files or other data needed to start the workflow).

On the canvas, click Start event.

The configuration panel for Start event appears.
From the Start from drop-down box, select Component workflow.

The Start event variables section appears.

Click Create variable.

The Variables dialog box appears, displaying the Start event tab that is selected by default.

Click Create.

Note: The Create button is available only if you have previously created a variable.

The Create variable box appears.

For Name, enter a user-friendly name for the new variable.

For Type, select the variable type you want.

Data types of variables

Variable type	Usage
Text	String value, such as John.
Decimal	Decimal value, such as 1.2.
Integer	Integer value, such as 1.
Boolean	Boolean value (Yes or No).
DateTime	Date or date and time value.
Collection	Set of files or array of values. If using for file inputs, make sure your default file location is configured.
File	File. Make sure your default file location is configured.

Click Create.

How do I handle files in my workflow?

You can start a workflow whenever a new or updated file is detected (example: Box - New file), upload files on start or at any point in the workflow, generate documents from tagged templates, send and receive files via email, and manipulate files. File handling can be set up in your workflow start eventThe connector and event for triggering the workflow to run, including required configuration. An example is Box - New file, which triggers the workflow to run when a new file is uploaded to the specified folder. and actionsA tool for building the processes, logic, and direction within workflows..

Note: Your tenancy's default file storage location must be configured to hold files for later reference by the workflow. This location is used for uploaded files and for files stored as output from actions.

In addition to handling files in workflows, you can start workflows from files in Box using Nintex Workflow for Box.

Handle files in your workflow start event

Start your workflow when a new or updated file is detected in a service; for example, see Box - New file and Connectors
- Store a file reference for use later in the workflow (file share connector start events)
  File share connector start events, such as Box - New file, require you to add each start event variable that you want to reference later in the workflow. The variables provided vary by start event. See Connectors.
  In the Designer page:
  1. On the canvas, click Start event.
    The configuration panel for Start event appears.
  2. From the Start from drop-down box, select a connector.
  3. From the Event drop-down box that appears, select an event.
    The Source section appears.
    Note: The Source section is available only for some events.
  4. Click Add variables.
  5. Select the predefined variables that you want to add to your workflow.
    Note:
    To select all variables, click Select All.
    If you know the variable and you want to find it faster, type the variable name in the Filter options field.
  6. Click Add.
    The Variables dialog box appears, displaying the variables you have selected.
    Note: If you want to edit the selection of variables, hover over the variable, click , and then click Show Details. Edit the variable name in the Name field or click .
Upload files when filling in a form from:
- Salesforce, using Nintex Drawloop DocAutomation for Salesforce
- The web or an app
Note: Your tenancy's default file storage location must be configured to hold files for later reference by the workflow.
Programmatically upload files for a Component workflowA workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event.; see Nintex - Component workflow

Note: Your tenancy's default file storage location must be configured to hold files for later reference by the workflow.

Handle files in your workflow actions

Generate documents from tagged templates using Generate document
Send and receive files via email; for example, see Assign a task
Manipulate files in services (see Connectors):
- Get, store, move, copy, or delete files using file share connector actionsA workflow action that performs a basic operation through a connected system, such as Salesforce or Box., such as Box - Move a file
- Get and attach files in Salesforce
- Get and store files in SharePoint
- Signatures: Get and store signed documents using DocuSign or Nintex Sign.
Store a file for use later in the workflow
For example, store any email attachments received by the task assignee.

In the Designer page:
1. On the design canvas, click the action you want to configure.
2. Find the output field for storing the file or set of files.
  
  For example, to store attachments received in task assignee email replies when they may attach multiple files, use the Assign a task Multiple file attachments option for the Store output field.
3. In the output field, do one of the following:
  - Select a variable.
    For output storing multiple files, select a collection variable. For output storing a single file, select a file variable.
    Note: Your tenancy's default file storage location must be configured to hold files for later reference by the workflow.
  - Specify a file path.
    You can use any combination of text and variables, beginning with the root folder. If available, use the folder browse icon on the right of the path field to navigate to the folder and any subfolders that you want, and then edit the path as desired to include variables and different text.
  Availability of variable or path options for storing files varies by action. See Connectors and Workflow actions.
Reference a stored file
For example, reference the new Box file that started the workflow to attach it to a task email notification or reference an image received by the task assignee to generate an invoice document.

Note: Your tenancy's default file storage location must be configured to hold files for later reference by the workflow. This location is used for uploaded files and for files stored as output from actions.

In the Designer page:
1. On the design canvas, click the action you want to configure.
2. Find the field where you want to reference the stored file.
3. In this field, do one of the following:
  - Select the file variable associated with the stored file.
    For example, select the variable for the new Box file that started the workflow or select the variable storing Multiple file attachments output from a task action.
  - Specify the file path where the file is stored.
    You can use any combination of text and variables, beginning with the root folder. If available, use the folder browse icon on the right of the path field to navigate to the folder and any subfolders that you want, and then edit the path as desired to include variables and different text.
    View example
    Both a file variable and a file path are used in the example image below for the Dropbox Business - Copy a file action. A file variable is selected for Source and a file path is specified for Destination.
    The variables "CountryVariable" and "Program" insert the values into the file path as determined by earlier workflow logic (in this case, fields in a submitted form). For example, if the person submitting the form selects Australia for country and specifies Inspire2017 for program, then the resulting file path is "/SpecialProgramNDAs/Australia/Inspire2017NDA.docx."
  Availability of variable or path options for referencing files varies by action and field. See Connectors and Workflow actions.

Configure the Box - Move a file action

In the Designer page:

Click the Box action group in the action toolbox.

or

Find actions by browsing action groups or by typing an action name or function in the Search field at the top of the action toolbox.
Drag the Box - Move a file action to the point in the workflow when you want to move the file.
Click the Box - Move a file action.
Select a Connection.
Don't have one yet? Follow these steps to create a Box connection
1. In the drop-down list for Connection, select Add new connection.
  
  A new window appears, prompting you for a connection name.
2. Type a user-friendly Connection name.
3. Click Connect.
4. Enter credentials if prompted.
  
  Upon successful log in, you are prompted to grant or deny access for Nintex Workflow Cloud.
5. Click the option to grant access.
  
  A window appears where you can assign owner and user permissions to the connection. Add Owners and Users, if required. For more guidance on connection permissions, see Permissions.
6. Click Save permissions.
Under Source, specify the file to move: Either select a file variable or type a file path. You can also browse the folder structure using the browse icon ().
Under Destination, in Path, type the file path where you want to move the file. You can also browse the folder structure using the browse icon ().
Select an option for Overwrite file.

For more information on the buttons and settings, see Box - Move a file action fields, buttons, and settings.

Maintain path integrity

Caution: If you move, rename, or delete a file/folder, any workflows that use that file/folder will not start or will fail. Make sure you keep the paths in your workflow configurations up to date.

Box - Move a file action fields, buttons, and settings

Section	Field	Description	Variable types
(unlabeled)	ConnectionCredentials and other settings required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store.	The Box connection to use for moving the file.	(n/a)
Source	Select a source type	Select how the action finds the file: Path: location in Box directory. File ID: unique file identifier number in Box. File variable: file stored in a variable in the current workflow.	(n/a)
	File path	Displays when you select the Path source type. The location in Box where the workflow retrieves the file from to move to the destination path. Accepts any combination of typed text, text added through navigation (), and inserted variables.	Text, Decimal, Integer, Boolean, DateTime
	File ID	Displays when you select the File ID source type. The unique identifier number the action uses to access the file in Box.	Text
	File variable	The file to move to the destination path. Accepts an inserted variable.	File
Destination	New file path	The location in Box where the workflow moves the file to. Accepts any combination of typed text, text added through navigation (), and inserted variables.	Text, Decimal, Integer, Boolean, DateTime
	Overwrite file	When selected, overwrites existing file with the same name in the destination. Accepts either a selection from the drop-down list or an inserted variable.	Boolean
	Store file as a variable	Variable to store the moved file. Accepts an inserted variable.	File
	Store new file ID as a variable	Variable to store the new file ID of the moved file. Accepts an inserted variable.	Text
	Store new path as a variable	Variable to store the path of the moved file. Accepts an inserted variable.	Text