[ADMINCTR-53] Switcher option between old and new groups Created: 18/May/22  Updated: 27/Jul/22  Resolved: 22/Jul/22

Status: Closed
Project: Admincentral
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.21

Type: Story Priority: Neutral
Reporter: Laura Delnevo Assignee: Jesus Alonso
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: 0d Remaining Estimate: 0d
Σ Time Spent: 7.5h Time Spent: 7.5h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
dependency
depends upon ADMINCTRLG-7 Use a provider for loading AppLaunche... Closed
is depended upon by ADMINCTR-55 DOC: Migration guide for the redesign... Closed
is depended upon by ADMINCTR-47 Inform users about changes after firs... Closed
supersession
supersedes ADMINCTR-14 Update the existing groups of apps. Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ADMINCTR-163 QA Sub-task Completed Jesus Alonso  
Template:
Acceptance criteria:
Empty
Date of First Response:
Epic Link: App Launcher redesign
Sprint: AuthX 14
Story Points: 5

 Description   

Provide the possibility to implement a switcher so that Current On-prem Clients can choose between the two options:

  • Getting New UI, but no grouping update
  • Getting New UI and new grouping

Notes https://wiki.magnolia-cms.com/display/PMTEAM/App+Launcher.+Migration+of+Apps+for+existing+customers?focusedCommentId=258022383&refresh=1652860241665#comment-258022383 in comments 



 Comments   
Comment by Jesus Alonso [ 02/Jun/22 ]

My proposal would be to have a configuration variable (e.g. layoutConfigurationMode) with 2 possible values:
  * CLASSIC: So we would use the current way to configure the apps & groups. It would be the default mode for 6.2
  * MODERN: Then, we would change the way we configure apps & group, letting us to define a new grouping without affecting 6.2. This would be the default mode for 6.3 (SaaS)

Comment by Jesus Alonso [ 22/Jun/22 ]

PoC created. 

Comment by Jesus Alonso [ 22/Jun/22 ]

Closed by mistake

Generated at Sun Feb 11 23:03:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.