Resolution: Won't Do
Affects Version/s: 5.2.1, 5.2.2, 5.2
Fix Version/s: None
Component/s: Content Modelling
Parity needed between bootstrap models and CMM managed models.
In the Content Model Manager, it is not possible to specify aspects as mandatory.
For example: <mandatory-aspects> <aspect>cm:generalclassifiable</aspect> </mandatory-aspects>
This is a major limitation.
- When creating an aspect via the Content Model Manager, the customer would like the ability to designate aspects as mandatory.
- When creating custom aspects via the Content Model Manager there is no ability to designate the aspect as mandatory.
This will save the customer time when deploying new aspects via the custom content models that they create. Currently, as it stands they still have to go into the content model defined and manually add the aspects as mandatory which is, in essence, double work.