Investigating
AEMaaCS | Keep user settngs
- February 6, 2025
- 1 reply
- 218 views
| Request for Feature Enhancement (RFE) Summary: | Rework the functionality how settings, which user can adjust, are saved. The current way to do that with a cookie avoid an efficient way of working for editors if they are switching devices and or browsers. |
| Use-case: | As an editor, I configure my AEM UI to my needs so that I can work most efficiently. So, e.g. I set up the left pane to show always the content tree. If I use another browser or switch the device, I'm working with, those settings should be still effective. |
| Current/Experienced Behavior: | Setting are not kept as the are stored not in the user account in AEM but in a cookie (which by the way expires also at next day, I think) |
| Improved/Expected Behavior: | Make those settings persistent in the user account within AEM so that it is not necessary to set them up every time. |
| Environment Details (AEM version/service pack, any other specifics if applicable): | |
| Customer-name/Organization name: | Carl Zeiss AG |
| Screenshot (if applicable): | |
| Code package (if applicable): |