Call a workflow

Use the Call a workflow action A tool for building the processes, logic, and direction within workflows. to call a Component workflow A workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event., which handles a common task or sub-process.

For example, many HR processes may involve the task of looking up IDs for employees. In this case, you can set up a child Component workflow for ID lookup and call that child workflow from each relevant HR workflow using this action.

Parent and children workflows are tied together. When a parent workflow is terminated, related child workflows also terminate. If a child workflow configured to complete before the parent resumes is terminated, then the parent will also terminate.

Important: File variables are not supported.

Before you start

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 event The 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 actions A 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.

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. Select a connector, from the Start from drop-down list.
  3. Select an event from the Event drop-down list.
    The Source section is displayed.
    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 workflow A 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 actions A 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 Adobe 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 Call a workflow action

In the Designer page:

Click the Logic and flow 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 Call to workflow action to the point where you want to call the Component workflow.
Click the Call a workflow action.
For Workflow, select the Component workflow A workflow that can be started from outside the tenancy; the workflow uses the "Component workflow" start event. you want to call.
Under Workflow, select the option you want (run at the same time or wait).
Fill in the fields for any inputs Variable to store a value or file when the workflow starts. Set up as a start event variable. and outputs Variable to store a value or file on completion of the workflow. Set up as a user-defined variable. that are rendered for the selected workflow.
Important: File variables are not supported.

Call a workflow fields

Section	Field	Description
(unlabeled)	Workflow	Component workflow to start.
	Run both workflows concurrently	When selected, continues running the current (parent) workflow after starting the selected Component workflow.
	Wait for this workflow to complete before continuing	When selected, pauses the current (parent) workflow until the selected Component workflow is completed. Use this option to reference outputs of the selected workflow later in the current workflow.
Inputs	(start event variable for selected workflow)	Value to pass to the selected workflow for the indicated workflow input Variable to store a value or file when the workflow starts. Set up as a start event variable.. For setup details within the Component workflow to be called, see Nintex - Component workflow.
Outputs	(output for selected workflow)	Variable to store the value received from the selected workflow for the indicated workflow output Variable to store a value or file on completion of the workflow. Set up as a user-defined variable.. For setup details within the Component workflow to be called, see Nintex - Component workflow.