...
Constraint type | Description | ||
|---|---|---|---|
Input constraints | This type of constraint can usually be found in download requests. Here, the user is asked for different types of input. The following constraints are available:
This is an example of this type of constraint:   | ||
Metadata constraints | This type of constraint gives the workflow administrator a great flexibility in terms of constraints as it allows to point to and interact with the metadata fields available in the customer’s Media Manager. In this type of constraint the metadata field’s content must match the condition. This is an example of a metadata constraint:  
| ||
Upload constraints | The user who makes a download request will have to attach a file in the from specified by workflows administrator. This could be e.g. a consent form. The upload constraint will be presented the same as any other input constraint, i.e. the functionality is the exact same as the other input constraints. This is an example of an upload constraint:   | ||
Execution condition | This type of constraint is related to who can execute the transition. The following constraints are possible:
This is an example of an execution condition constraint:   |
Each constraint item has two icons in the upper right corner: one for the available actions regarding the constraint, and the other for re-ordering the constraint.
...
in the task list view, in the last column
in the task detail view, in the upper right corner of the modal.
If there are no constraints attached to the selected action, the transition will be successful instantly.
...
In case of input constraints, the user needs to fill in additional information in the form of text, date or selecting an option from the provided list
In case of upload constraint, the user needs to upload a file in a required format
In case of metadata constraints, the user needs to make sure that the provided metadata fields are filled in according to the requirements.
Multi-transition of tasks
...