You can create a workflow that only runs if certain conditions are met. This enables you to create highly customized workflows that align with your organization's specific processes and requirements.
To add a condition to a workflow, select the Start activity. The Conditions page is in the right side panel, and has a counter to denote the number of conditions that have been configured.
Each condition relates to a specific field. The fields that are available to select depend on the object type that the workflow is based on. Depending on the selected field type, a number of operators are available to choose from, such as, contains, does not contain, is populated, is not populated.
You can add more than one condition group. The first condition group is created when you select Save after adding one or more conditions. Within each condition group, if there is more than one condition you can define the relationship between the conditions by selecting one of these options:
- Match all conditions: The workflow is triggered only when all conditions in the group are met.
- Match any conditions: The workflow is triggered when any of the conditions in the group are met.
Conditions can be set on action fields, asset fields or on the existence of a relationship or ownership. For example, trigger a workflow to notify a Data Steward when an asset's "Certification Date" is within 30 days. Or, trigger a workflow to notify a team lead when an asset is assigned to their team.
For field-based workflows, you can select Associated Semantic Type as the condition field to evaluate the semantic type assigned to an asset. Use this condition when a workflow should run only for assets with a specific semantic type, for assets with or without any semantic type assignment, or when the semantic type assignment changes. For value-based conditions, choose from the available semantic type qualifiers in the catalog.* Preview
| Operator | Description |
|---|---|
| is | The assigned semantic type matches the selected value. |
| is not | The assigned semantic type does not match the selected value. |
| is populated | A semantic type is assigned. |
| is not populated | No semantic type is assigned. |
| changed | The semantic type assignment changed. Previous and new values do not need to be specified. |
For example, use Associated Semantic Type is to route assets with a selected semantic type through a review path. Use Associated Semantic Type changed when any semantic type reassignment should start the workflow path.