Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-6028

View's columns can't be ordered: Especially in dynamic generated contentType based apps annoying (status & moddate)

XMLWordPrintable

      Tested:

      On current 6.2.2-SNAPSHOT

      Situation:

      • Using a contentType based app.
      • Three columns get automatically created: 'name' & 'activationStatus' & 'lastModified'

      Problem:

      In general one can not impact the order of the Fields at all, therefore one can not place 'activationStatus' & 'lastModified' as the last ones.

      Also not by re-defining them in the app, as the beans are already populated.

      Also when you plug in a new column via decorators into an existing app, one can not control where it will be added. 

      Code in the app:

      subApps:
        browser:
          workbench:
            contentViews:
              tree:
                columns:
                  name:
                    name: jcrName
                    label: Event name
                    nodeTypeToIcon:
                        event: icon-datepicker
                  location:
                    expandRatio: 1.0
                    editable: false
                    filterComponent:
                       $type: textField
                  date:
                    $type: dateColumn
                    expandRatio: 1.0
                    editable: false
                    filterComponent:
                       $type: textField
                  eventType:
                    expandRatio: 1.0
                    editable: false
                    filterComponent:
                       $type: textField
                       
                  activationStatus:
                    expandRatio: 1.0
                    editable: false
                    test: test
      

      Here the result (orange):

      And the proof that it was applied (test: test value) in the definitions app:

       

      Solution:

      Columns should by their default config have a property alike:

      orderNumber: 1

      So one could simply impact the order via decorators of any app existing, and also in the dynamic generated apps.

        Acceptance criteria

              Unassigned Unassigned
              cringele Christian Ringele
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD