...
Scenario | Configuration | Explanation |
---|---|---|
There is no stage owner. | Set Automatically Assign Stage to “Do not automatically assign”. | This option should be used for the stages which should not lead to task assignment. An example of a use case for this scenario is an approved stage, where no further action is needed after a request download was granted. |
The stage owner is a user. | Set Automatically Assign Stage to “Assign to a user”. In the new field below select the stage owner from the provided list. | This option should be used for stages that should be assigned to a selected user. All the available users are presented in the drop-down list. |
The stage owner is a user group. | Set Automatically Assign Stage to “Assign to a user group”. In the new field below select the stage owner from the provided list. | This option should be used for stages that should be assigned to a selected user group. All the available user groups are presented in the drop-down list. |
The stage owner is the workflow owner | Set Automatically Assign Stage to “Assign to the instance owner”. ? | This option should be used, if the person who needs to take action on the tasks related to the stage is the person who created this specific workflow. |
The stage owner is assigned dynamically. | Set Automatically Assign Stage to any value. Then, select the correct MasterItemReference type metafield from the list under Dynamically Assign Stage. | This option provides more flexibility in terms of who will handle the download requests. An example of a use case is the situation in which each asset has an owner who is responsible for what happens with this particular asset. The asset owner is determined by a metafield. Note that dynamic assignment works only, if there is one asset in the task. If the dynamic assignment fails because of multiple assets in the task or because the indicated metadata field is empty, the automatic stage assignment is the fallback. This is why the user needs to configure both options. |
...