...
In order for a user to have the ability of request the download of an asset, they need to have the roles ‘Asset_Can_Download', ‘Business_Workflow_Instance_View', and ‘Business_Workflow_Instance_Transition'. They also need the download qualities (as they normally would, if download approval wasn’t enabled.
As of Media Manager 5.4, workflow functionality, including Download Approval, is under feature flag. For more information, go to MM5.4 Feature flags
already did).
The workflow used for the approval process needs to fulfill all of the following conditions:
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 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
...