When a request is assigned to the next stage in the workflow path, Data Relationship Management matches user groups associated with the stage in the workflow model to the user groups with appropriate workflow access to the data for the request items in the request to determine which users can participate in the request for the stage. This intersection will typically result in at least one user per stage, but in some cases there may be no matching users for a particular stage. In these situations, governance workflows may permit a workflow stage to be skipped if all required values are already provided and all validations for the stage pass successfully. The ability to skip workflow stages enables the workflow model to adapt the workflow path to only stages necessary to be completed based on the actual items in a request. This adaptation capability enables broader workflow models to handle specific workflow requirements for certain data sets differently using the same model rather than requiring a separate workflow model and separate requests to be used for that purpose. Any approve, enrich, or commit workflow stage can be configured to permit or restrict the stage from being skipped.
A workflow stage cannot be skipped if any request items in a request do not have required values or fail validations configured for the stage, or if the workflow model has been configured to restrict this behavior. In this case, the request is escalated to Data Manager role users.