You can configure workflows that are triggered when other users edit code lists, crosswalks, or hierarchies. You can also enable an approval workflow for code lists or crosswalks when you import code values or value mappings by using the import version 2 REST API. You can define the number of approval steps, approvers for each approval task, and whether comments are required for task actions.
Users assigned the following roles can configure workflows that are triggered when other users edit assets, review the tasks, and approve or reject the proposed changes:
•Reference 360 Primary Owner role and the Primary Owner stakeholder role for a code list.
•Reference 360 Business Steward role and the Business Steward stakeholder role for a crosswalk.
•Reference 360 Planner role and the Planner stakeholder role for a hierarchy.
The workflow configuration includes the approval tasks, approvers for each approval task, and whether comments are required.
The following table describes the approval workflows you can configure:
Approval Workflow
Description
Activity
One-step
One-step approval workflows contain one approval task. This workflow is the default approval workflow for all code lists or crosswalks.
An approver can approve, reject, or send the changes back to the originator.
If the changes are approved, they become part of the active version of the code list or the crosswalk.
The first approver can approve or send the changes back to the originator.
If the first approver approves the changes, the next approver can approve or send the changes back to the originator.
The next approver can also approve the changes or send the changes back to the originator.
After the task reaches the final approver, the final approver can approve, reject, or send the changes back to the originator.
If the changes are approved, they become part of the active version of the code list or the crosswalk.
Note: To enable multi-step workflows, configure the approval implementation mode by using APIs. For more information, see Update approval implementation mode.
If approved, the changes become part of the active version of the code list, crosswalk, or hierarchy. You can view your latest changes and previous changes on the History tab of the code list, crosswalk, or hierarchy.