Users can change panels in MForms to obtain personalized versions of the standard M3 panels. Examples of personalization are conditional styles, hyperlinks, tab order, label texts and JScripts. Personalization is done directly within MForms using dialogs and special edit mode panels. There is a Personalization menu available under the Tools menu and on the context menu for the panel that contains the available personalization options.
Scripts are deployed on the MNE (Movex Net Extension) server.
When a personalization is created in MForms, it is stored on the M3 Net Extension (MNE) server. When an M3 program is started, the MNE server checks if there
is a personalization for that program and, if so, embeds the personalization data in the response.
Personalization data is stored in a folder called Customizations, located in the data folder for MNE. The MNE data folder is defined using a property
called FileRootPath in the property file for MNE (mne.properties).
Global and Role Personalization
In additions to user-specific personalizations, you can create personalizations for specific roles or global personalizations for all users. Both global and roles
personalizations are stored in the same way as user customizations, but the folder is named after the role id in MNS405 for role personalizations or using
the name GLOBAL_CUSTOMIZATIONS for global personalizations.
On the tools menu you can check which personlizations are loaded by selecting Personalize – > View Personalizations.
You can also turn off all personalizations by selecting Personalize -> Hide All Personalisations.
If you have issues with scripts that are not visible and you would like to know if there are loded or not you should check the log file. There should be logs if the script file cannot be found or if the script cannot be compiled. Filter on ScriptManager in the Origin column in the Log Viewer (internal://log/) or in 9.1.2 or previous version open the Log from the about LSO window.
To verify that the user has a script personalization open the View Personalization dialog from Tools -> Personalizations -> View Personalizations.
If the script personalisation is not there, you might have to restart LSO or clear the personalization cache on the Workplace/MNE server (Functions page in the MNE Manager).
Private personalizations vs global and group personalizations
Peter K gave me this short summary of how it all fits together. Thanks Peter!
- MForms supports customizations from two sources on a panel: User or Central (which includes Role and Global).
- MForms will merge customizations if there are two sources on a panel.
- The merge supports merging of different customization types on a panel.
- If two sources have the same customization types on the same panel they will not be merged, one will be selected based on priority.
- The order of priority is User first, the Central (Role and Global).
– Global tab index customization for MMS001/E
– User conditional style customization for MMS001/E
Both customizations should be active.
– Global script customization for MMS001/E
– User script customization for MMS001/E
Only the user script customization will be active.
Mixing central customizations with user customizations can cause problems. One solution is to use Role customizations for specific groups of users and Global customizations for the rest.
If the users are allowed to create their own customizations these will always override Role/Globe customizations of the same type on the same panel.
The reason for not merging customization of the same type is that the results can be very unpredictable. It might have worked for some customization types in some cases but we decided against supporting this.