Priority order of personalizations
This list shows the order of priority:
- User level
- Enterprise Modeler roles, if present
- Role level
- Company level
One level is used per session.
A user level has the highest priority. Changes that are made by a key user have priority over the standard personalized sessions.
A Role code can be a Personalization Role or an Enterprise Modeler Role. If an Enterprise Modeler Role is assigned to a user, then it has priority over the normal Role level. The roles of the Enterprise Modeler are used.
The Role and Company level is assigned by the system administrator at the customer site. The end users work with these personalized roles and company sessions.
Typically, a generic session is prioritized on Company level and is the same for all users. For example the Currencies (tcmcs0102m000) session. All users use the same currency for the specified company. A Sales Order session is on Role level, this is more specific. All users can use the Sales Order session but not all users see the same information. For example, prices are not shown to everyone.
Company and role level personalization, for example on the same field but with other color or other label on the same session is not recommended.
For normal users we do not recommend that they create their own personalization on several fields and colors. To avoid such scenarios, we recommend that you disable normal Personalization for End Users.
In the User Data template, you can specify several Personalization authorizations and options for the user. We recommend to use the own standard templates.
To setup the correct personalizations for users:
Select
.In the Properties (ttadv1140m300) session you can check in the Personalization tab if the user has the correct personalization on runtime.
In the Disable Personalizations (ttadv9109m000) session you can disable several personalizations in case of issues. Afterward, this is also shown in the Properties (ttadv1140m300) session.
End users can always adjust the column width and splitters. These adjustments are not functional form changes and are safe to use.