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?
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.
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.