...
It needs at least three stages. One for “Pending”, one for “Approved”, and one for “Denied“. We advise you to call them this for maintainability, however, it’s not required.
The first transition needs to at least have the constraint “Only Specific User or User Group Any user can transition“, else the users will get an error when they try to instantiate. (For admins, we have a role to bypass this “Only Specific user…“ constraint, and it’s called “Business_Workflow_General_Transition_Executor“. Again, only assign this to admins, as all “Only…“ constraints will be bypassed with this.)
We allow for other constraints on this first transition. Some set up “input constraints“, which are data the requester will be asked to fill out to request a transition.
The currently supported input constraints are: String, Int, and Date. Below is an image of how String and Date look for the end user
...
Below are shown the 8 valid scenarios which you can configure the download request.
All users have to request all assets | Metafield = Any |
All users have to request all assets except selected assets | Metafield = Bypass |
All users have to request all assets except for selected formats | Metafield = Any |
All users have to request all assets except selected assets and selected formats | Metafield = Bypass |
No users have to request any assets | Disable download request altogether |
No users have to request any assets except selected assets | Metafield = Require |
No users have to request any assets except selected formats | Metafield = Bypass |
No users have to request any assets except selected assets and selected formats | Metafield = Require |
| Info |
|---|
Please be aware that this does not into consideration that there is the bypass role “Download_Approval_Bypass “ which, as previously stated, will disregard any download restrictions you have in place. |
...