How to make categories mandatory in RAM during asset creation?
How does one forces the submitter of an asset to specify a category in order for the asset to be created and enter into draft state?
So far, I can specify Category Validation Policy for transitioning between states in a lifecycle, but I can't find a way to make it mandatory from the point of asset creation.
|
One answer
There is no way to force a category on a submit (unless you automate this category with a policy or on the type from an XML content).
This is the reason for a draft state, in which a user "packages" the asset ... mostly you hide the visibility of that asset on this state, so that it is only available to the submitter, until he packages the asset properly, in which case they can more it to the next state. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.