Order of menu bar options should be unique in all scenarios , please find example below.
"When you select from a folder, they are ordered CREATE - SHARE LINK - DOWNLOAD - CHECKOUT - PROPERTIES - TO COLLECTION - etc. In a search selection, they are ordered PROPERTIES - SHARE LINK - TO COLLECTION - DOWNLOAD - CHECKOUT - etc."
Having to constantly search for options that are in a different location makes for inefficient navigation.
Use-case:
Visibility of menu bar option in fix order in all scenarios / views.
Current/Experienced Behavior:
Options are not in order if we consider scenario of select searched assets vs navigate to folder and select asset, if you compare menu bar option order , it's not the same.
Improved/Expected Behavior:
Options should be in one unique order.
Environment Details (AEM version/service pack, any other specifics if applicable):
6.5.7
Customer-name/Organization name:
Hershey's
Screenshot (if applicable):
Search "Running" in vanilla instance (6.5.7) - selected one 1 and got below order of menu bar options.
Navigate to the folder i.e. /content/dam/we-retail/en/activities/running - and select the 1 asset - see order of menu bar options.
Thanks for submitting this request to the AEM community. Please note that the tool bar options are mainly different between the mentioned use cases. While I understand there are some common options but It does not seem to have significant impact.
@hamidk92094312 Hi Sir, From customer perspective, order of the option is important I think, as they are frequently using menu bar options, so if we have certain order efficiency of work will be increased.
i.e. "When you select from a folder, they are ordered
CREATE - SHARE LINK - DOWNLOAD - CHECKOUT - PROPERTIES - TO COLLECTION - etc.
In a search selection, they should be ordered as
SHARE LINK - DOWNLOAD - CHECKOUT- PROPERTIES - TO COLLECTION - etc."
Visibility wise it's fine if different use case having different options visibility, but order wise if we can make it consistent it will be very helpful.
Please note that per my earlier update, while we understand the behavior could be improved but it at this time it can not be classified as a high business impact request based on the prioritization model. We appreciate you as an active member of the community with multiple ideas in review by the product team.