Uploaded image for project: 'Content Types'
  1. Content Types
  2. MGNLCT-81

Content Types evolution

    XMLWordPrintable

Details

    • Epic
    • Resolution: Obsolete
    • Major
    • None
    • 1.0
    • None
    • Content Types evolution

    Description

      Once a Content Type is modeled, it should be clear how to modify it over time, while maintaining integrity of existing content.

      Keep moving away from dialogs/apps as the implicit model for customer data. Offer tooling for it to evolve over time, with assisted bulk-changes and without Java version handlers.

      Example story: As a project developer, I can declare changes to my content types models, so that pre-existing content can be migrated or "adapted", e.g. rename properties, add new properties with a default value, etc.

      TBC

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                mgeljic Mikaël Geljić
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: