# Configuring Legacy Workflows: Workflow Process Steps



<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The content in this article refers to single-document workflows, now known as legacy workflows. While existing workflows remain supported and such workflows can continue to be updated and used, legacy workflows will not receive new functionality in future releases. As of the 21R1.2 release, <a href="/en/lr/70436/">multi-document workflows and object workflows</a> are unified under <strong>Admin</strong> &gt; <strong>Configuration</strong> &gt; <strong>Workflows</strong>.</p>

<p>If your document lifecycle does not have any legacy workflows, the <em>Legacy Workflow</em> tab will not appear on your document lifecycle configuration page. If you require legacy workflow functionality for such a document lifecycle in your Vault during this release period, contact Support.</p>

<p>After the 21R3 release, you cannot create or copy legacy workflows in any Vault. You can continue to refresh or clone Vaults with existing legacy workflows.</p>
    </div>
  </div>
</div>



Workflow steps define all the actions within a workflow, whether they are user actions like providing electronic signatures or system actions like sending notifications. This article covers types of steps that relate to a workflow process:

  * **Notification**: The **Notification** step sends a message to users (by email and to the Notification page in their Vault). See [details][2].
  * **Join**: When you create parallel steps in a workflow, the **Join** step re-connects these branches and enforces that all parallel tasks must be complete or canceled before the workflow advances to the next step. See [details][3].
  * **Timer**: The **Timer** step monitors a specific workflow task and expires if the task is not complete at the end of the specified time period. See [details][4].
  * **End Workflow**: The **End Workflow** step marks the end of a workflow. See [details][5].

You can read details about other types of steps in [Legacy Workflow Tasks & Decision Steps](/en/lr/21922/) and [Document Update Steps](/en/lr/21921/). To learn about creating new steps and linking them together, see [Configuring Legacy Workflow Steps](/en/lr/2453/).

## Notification Steps {#notification}

Notification steps allow you to send messages to users associated with the document or workflow. For example, after a State Change step, Vault Notification steps allow you to send messages to users with roles on the document. You can manage the messages themselves from **Admin** > **Configuration** > **Messages**. Notification steps send an email to the selected users and add a new item to the **Home** > **Notifications**.

For workflow tasks, you can select a message as part of the workflow task configuration, so a notification step is not needed to inform users that the workflow has assigned a task to them.

<table class="wbord">
  <tr>
    <td>
      <strong>Field</strong>
    </td>
    <td>
      <strong>Description</strong>
    </td>
  </tr>
  <tr>
    <td>
      Message Template
    </td>
    <td markdown="span">
      Select a message to send in the notification. Learn more about [message templates](/en/lr/2157/).
    </td>
  </tr>
  <tr>
    <td>
      Recipient
    </td>
    <td>
      Select a user role as recipient for the notification. If multiple users are in a role, Vault sends the notification to all of them.
    </td>
  </tr>
  <tr>
    <td>
      Show decision/comments from previous task(s) in notification detail
    </td>
    <td>
      Optional: Select this checkbox if Vault should include decisions (Approve, Deny, etc.) or comments from one or more previous tasks in <strong>Active Workflows</strong> and <strong>Show Notifications</strong> on the Doc Info page.
    </td>
  </tr>
  <tr>
    <td>
      Display decision and comments from
    </td>
    <td>
      Optional: Choose the previous tasks from which to include decisions and comments.
    </td>
  </tr>
</table>

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Do not configure notifications related to task assignments. Vault automatically notifies users when they have tasks to complete.</p>
    </div>
  </div>
</div>



## Join Steps {#join}

When including parallel workflow tasks, the Join step enforces that all parallel tasks must be complete or canceled before the workflow can advance to the next step. Parallel tasks with a Join step are a different workflow model than a single task assigned to multiple users. With parallel tasks, you can send different instructions for each task, whereas a single task with multiple users must have a single instruction set. For a typical parallel review workflows, it is better to use parallel tasks and assign different functional roles to each task than to assign the same review task to multiple users.

To use the Join step, create the step and set it as the next step for all parallel tasks.

### Short-Circuit Setup in Join Step

Workflows sometimes include parallel tasks, meaning that more than one task is assigned simultaneously for the workflow and multiple tasks are open at the same time. The short-circuit option allows you to identify verdicts that will short-circuit the review and approval process by canceling open parallel tasks.

To configure short-circuiting on a Join step:

  1. From the **Step Details** page for the Join step, click **Edit** and select the **Allow Short-Circuit** checkbox.
  2. All valid Workflow Task steps will appear in the **Parallel Tasks** list. To be valid, a step must have verdicts and have the Join step selected as its "next step."
  3. For each task, select one or more verdicts that will cause Vault to cancel outstanding parallel tasks. If needed, you can choose to not select any verdicts for some Workflow Task steps.
  4. Click **Save**.

Learn more about [short-circuiting parallel workflow tasks](/en/lr/21922/#short-circuit).

## Timer Steps {#timer}

Timer steps monitor a workflow task and expire if the task is not complete at the end of the specified time range. When a timer step expires, Vault notifies the Workflow Owner. Depending on settings, a timer step may also cancel outstanding tasks. The system updates the timer step's due date when you update workflow due dates. Note that timer steps expire at the end of the day, according to UTC.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: To create a Timer step, you must go to the <strong>Tabular View</strong> for the <strong>Workflow Steps</strong> panel and click the blue <strong>+ Create</strong> button. The Timer step type does not appear for steps created in any other way.</p>
    </div>
  </div>
</div>



<table class="wbord">
  <tr>
    <td>
      <strong>Field</strong>
    </td>
    <td>
      <strong>Description</strong>
    </td>
  </tr>
  <tr>
    <td>
      Associated Workflow Task
    </td>
    <td>
      Select the workflow task to which the timer is linked. The list includes all current workflow tasks.
    </td>
  </tr>
  <tr>
    <td>
      Timer Parameter
    </td>
    <td>
      Select the field to use as the timer expiration date. This list only includes fields for which there is a <strong>Date Control</strong> configuration in the workflow's <strong>Start</strong> step.
    </td>
  </tr>
  <tr>
    <td>
      Cancel outstanding tasks on timer expiration
    </td>
    <td>
      Optional: Select this checkbox to automatically cancel all incomplete tasks associated with the timer when the timer expires. This option can ensure that the workflow progresses without any open tasks.
    </td>
  </tr>
  <tr>
    <td>
      Remove completed task owners from participant list
    </td>
    <td>
      Optional: Select this checkbox to automatically remove all users that have completed their tasks from the list of workflow participants. This action enables you to resend the task to only the users with outstanding work to complete.
    </td>
  </tr>
</table>

### Timer & Join Step Behavior

Tasks canceled by a timer do not behave exactly the same way as tasks canceled manually, and may produce unexpected results if followed by a **Join Step**. In this situation, the join will never complete because the canceled task wasn't completed (just canceled), and the join is still waiting for the canceled task.

If you must have a join step follow a timer step, create a **Decision Step** in-between with no rules except the "Else" statement pointing to the join step. Next, set both the task and timer to point to this decision step as their next step. This way, whether the task is completed or canceled by the timer, the task will go to the decision step which will go to the join.

## End Workflow Steps {#end}

Vault automatically includes an **End Workflow** type step in every workflow. If your workflow includes a decision step that branches the workflow, you can add an **End Workflow** step to each branch.

<table class="wbord">
  <tr>
    <td>
      <strong>Field</strong>
    </td>
    <td>
      <strong>Description</strong>
    </td>
  </tr>
  <tr>
    <td>
      Display Start Next Workflow dialog when workflow ends
    </td>
    <td>
      Set the checkbox if you want Vault to display a dialog when this workflow completes that prompts the user to start one of the other workflows that is available for the document's lifecycle state. This dialog appears only for the user who completes the last workflow task step in the workflow.
      <p>
        If the final task owner does not have the necessary permissions for the workflow's final document state, the <strong>Start Next Workflow</strong> dialog will not appear, even if configured.
      </p>
    </td>
  </tr>
</table>

Some migrated workflows may not have an **End Workflow** step. In this case, the workflow ends automatically when no additional steps are available to process.

 [2]: #notification
 [3]: #join
 [4]: #timer
 [5]: #end