[MGNLUI-6028] View's columns can't be ordered: Especially in dynamic generated contentType based apps annoying (status & moddate) Created: 08/Jul/20  Updated: 05/Mar/21  Resolved: 05/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: app, app framework, tree/list, workbench
Affects Version/s: 6.2.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File App-ColumnOrder-InDefintions.png     PNG File App-ColumnOrder.png    
Issue Links:
Relates
relates to MGNLUI-6030 Dynamic generated contentType based a... Open
relates to MGNLUI-6259 ContentType based App & Column Editor... Open
duplicate
is duplicated by MAGNOLIA-7080 Decorators: Provide possibility to de... Accepted
relation
is related to CFGUI-127 View's columns: Their order seems ran... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

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.


Generated at Mon Feb 12 09:32:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.