The personalization options in the application are very strong, limiting the need for customizations while enabling users to simplify their user interface.
A simpler user interface improves the usability and acceptance of the system. It would be great that an administrator (/ consultant) can create the optimal personalization for the forms in use and easily share or deploy this to all users. This limits the need for customizations to hide and change form objects and increases the maintainability.
One of the most heard requests during an implementation is around simplifying these fields. With this option, we can stay away from customizations / code releases and functional designs while quickly helping the new users to adapt to the system.
Comments
Agreed that centralized workspace management would be very beneficial. The current method of importing and exporting workspace customizations is difficult to manage with a large number of users.
Category: User Experience
Initial feature set allowing the administration of personalization's for groups of users:
https://ax.help.dynamics.com/en/wiki/personalizing-the-user-experience/
Category: User Experience
Wow, that was quick :D
https://ax.help.dynamics.com/en/wiki/whats-new-or-changed-in-dynamics-365-for-operations-platform-update-5-march-2017/
Category: User Experience
In addition, this is also valid for workspaces. It would be a very valueable addition if you are able to publish a workspace to a group of users and be able to maintain it centrally.
In the most ideal situation this is (optionally) integrated with Lifecycle Services. In my vision you should be able to define user group profiles and be able to link them to (parts of) processes in the Lifecycle Services BPM. For these group profiles you should then be able to apply shared personalization and enable (centrally managed) workspaces. This all with respect to the options to disable personalization in a whole or only allowing explicit personalization.
Category: User Experience
Jason Green (administrator) on 10/7/2017 8:26:35 AM
This was addressed in Platform Update 5.