Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-18953

Content Model Manager does not provide the ability to specify mandatory aspects

    Details

    • Type: Improvement
    • Status: Closed
    • Resolution: Won't Do
    • Affects Version/s: 5.2.1, 5.2.2, 5.2
    • Fix Version/s: None
    • Component/s: Content Modelling
    • Labels:
      None
    • Bug Priority:
      Category 4
    • ACT Numbers:

      00948025, 00932012

      Description

      Summary

      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. 

      Desired Behavior

      • When creating an aspect via the Content Model Manager, the customer would like the ability to designate aspects as mandatory.

      Current Behavior

      • When creating custom aspects via the Content Model Manager there is no ability to designate the aspect as mandatory.

      Use Case
      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.

        Attachments

          Issue Links

            Structure

              Activity

                People

                • Assignee:
                  closedissues Closed Issues
                  Reporter:
                  bgottschling Brandon Gottschling [X] (Inactive)
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  7 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel