Note: 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, multi-document workflows and object workflows are unified under Admin > Configuration > Workflows.
If your document lifecycle does not have any legacy workflows, the Legacy Workflow 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.
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.”
Learn how to configure workflow tasks that present options to users, including task dialog display options and user decision options. Note: This article refers to workflow tasks. Vault also includes a User Task object class to track unplanned work. For information on user tasks, see Working with User Tasks.
Workflow Tasks as Stand-Alone Constructs
Workflow tasks serve two purposes, allocating tasks to users and collecting their feedback at the time of task completion. In the case where the user should be prompted to complete their task without any additional feedback (e.g. verdict, disposition, etc.), the workflow should leverage a Workflow Task without a User Driven Decision. In addition, in this scenario, the “Prompt for verdicts” should not be selected.
In a similar scenario, a task may be sent to multiple users, with the goal of capturing a verdict or disposition, but leaving the final decision on the next steps of the document to the workflow initiator or some other user functioning in a coordinator role. In this case, the multi-user workflow task should be used with the “Prompt for verdicts” option enabled and the verdicts defined, however the next step should be a single user workflow task to determine the outcome.
Workflow Tasks with User Driven Decisions
User Driven Decisions should be used only when the Workflow Task preceding the decision is a single user workflow task. User Driven Decisions depend on one verdict from a user which will determine the path of the workflow. This may also be referred to as branching within the workflow. Currently, Vault can branch based only on a single user input, it cannot evaluate the inputs of multiple users and make a decision to progress the workflow.