Ordering rollout configurations

Avatar

Avatar
Boost 3
Level 2
jeff_foxx
Level 2

Likes

3 likes

Total Posts

10 posts

Correct reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Boost 3
Level 2
jeff_foxx
Level 2

Likes

3 likes

Total Posts

10 posts

Correct reply

2 solutions
Top badges earned
Boost 3
Boost 1
Affirm 1
View profile
jeff_foxx
Level 2

09-12-2020

Since the 6.4 upgrade, rollout configs moved from /etc to various locations (/libs, /apps).  Before, we could set the order by reordering them in the miscadmin tools interface in Classic.  This would control the order that the rollout configs applied to a rollout, when multiple configs were added to a page.

 

Now that they are spread out, how are we to manage the order?  Does it matter the order they exist in the JCR anymore?  

Accepted Solutions (0)

Answers (3)

Answers (3)

Avatar

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile

Avatar
Give Back 5
Employee
vanegi
Employee

Likes

392 likes

Total Posts

378 posts

Correct reply

148 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 10
Give Back
Boost 50
View profile
vanegi
Employee

09-12-2020

Hi @jeff_foxx,

yes, since the 6.4 upgrade sites repository re-structuring has been made. More details on https://experienceleague.adobe.com/docs/experience-manager-64/deploying/restructuring/sites-reposito...

 

Capture.JPG

 

In regards to managing the order, you can keep the order as such as they exist in the JCR before under /etc folder. Just need to migrate the rollout configs to the new locations which are now:

/libs/msm/wcm/rolloutconfigs

/apps/msm/wcm/rolloutconfigs

 

Thanks!!

 

Avatar

Avatar
Affirm 100
MVP
shelly-goel
MVP

Likes

246 likes

Total Posts

410 posts

Correct reply

105 solutions
Top badges earned
Affirm 100
Give Back 25
Ignite 3
Give Back 10
Validate 1
View profile

Avatar
Affirm 100
MVP
shelly-goel
MVP

Likes

246 likes

Total Posts

410 posts

Correct reply

105 solutions
Top badges earned
Affirm 100
Give Back 25
Ignite 3
Give Back 10
Validate 1
View profile
shelly-goel
MVP

09-12-2020

Hi @jeff_foxx  

Yes the rollout configs could be ordered. If you noticed, there's a sling:OrderedFolder node "orderlist" under "/libs/msm" which is actually driving the order in which these configs will be listed in the dropdown (same as the order of nodes under orderlist). All the other rollout configs which are not under "orderlist" will be listed out in the end.

 

So to control the order, create an overlay of /libs/msm/orderlist under /apps/msm and add the nodes for each rollout config under this node as per the order you want (each node will have a "path" property for the rollout config reference). Any config that exists under /libs or /apps but not listed under "orderlist" will appear at the end of the list in the dropdown.

Avatar

Avatar
Give Back 3
Level 4
SundeepKatepally
Level 4

Likes

76 likes

Total Posts

76 posts

Correct reply

21 solutions
Top badges earned
Give Back 3
Boost 10
Boost 25
Boost 50
Affirm 10
View profile

Avatar
Give Back 3
Level 4
SundeepKatepally
Level 4

Likes

76 likes

Total Posts

76 posts

Correct reply

21 solutions
Top badges earned
Give Back 3
Boost 10
Boost 25
Boost 50
Affirm 10
View profile
SundeepKatepally
Level 4

09-12-2020

Firstly

 

Apps/msm --> is is blueprint configs

libs/msm --> is for rollout configs

/etc/*msm --> is the legacy path.

 

Now when it comes to rollout config drop down, which shows in the blueprint tab of content page --> it will pick all the configs from /libs/msm/*. Here you cannot control the order of the elements in the dropdown unless by overlaying , which is not recommended.

 

When it comes to multiple rollout configs on the page ,depends on the order on how it is there is jcr:content . Order is as per the order in which rollout configs are added on the multifield.