Who is this article for?

Administrators configuring Workflows.

Workflow Designer access is required.

Workflow Automation steps allow you to start system actions directly from a Workflow instance. Typically this feature is used to have one Workflow be automatically started based off of selections made in another Workflow, via the Workflow Launcher.

Automation steps can be created for any default system action, such as copying data from one Workflow Instance to another, waiting on a Workflow to copy data, launching new Workflow Instances from an existing process, or automatically populating a Word template with data captured a Workflow. This article shows you how to configure it.

1. Creating Automation steps

1. Creating Automation steps

1. Select Administration in the Navigation Bar.
2. Click Workflows.
3. Open a Workflow Definition.
4. Give the new step a Title.
5. Select Automation from the Type dropdown.
6. Click Add Step.

7. Create Routes to and from the step.
8. Select the newly created Automation step.
9. Choose an Automation type from the System Actions dropdown.
   This will refresh the window with additional options.
10. Complete the remaining information.
11. Click Add Automation.

Below is a description of what each Automation can help you achieve:

• Workflow Launcher initiates a new Workflow Instance.
  Like with the data copier step above, data between common fields is automatically copied over into the newly launched Workflow Instance.
• Data Copier copies data from this Workflow into another related Workflow.
• Form Filler populates a Word template with data from the Workflow.
  The filled form can then be attached to the Workflow as a record, added to the document tree in a specific location, or both. The form can also be converted to PDF for final storage if desired.
• Wait on Workflow forces this Workflow to wait at the Automation step until one or more related Workflow Instances progress to a specific step in their processes.
  Once they do (and typically then use Data Copier to update the waiting Workflow), the waiting Workflow moves to its next step.

Instances (Children) linked through an Automation step will be accessible and viewable by the initiator of the Parent Workflow.