Groups/user level of user interface

Build 1501 on 14/Nov/2017  This topic last edited on: 5/Jul/2016, at 10:49

Since the version 2.4, GN4 supports multiple user interfaces, based on a group membership or even on a user level. This requires that you have not only one set of configuration files for menus, keyboard and mouse shortcuts, navigators, search dialogs, and preview panels, but multiple sets with modified copies of such files, one for each variated UI.

IMPORTANT: the configuration files for menus, keyboard and mouse shortcuts, navigators, search dialogs, and preview panels in any set MUST HAVE THE SAME NAMES. Therefore, you need to keep them in different folders.

Examples

1.You want all the users in all the titles to have the same configuration: just load the configuration file from the main set on the root level, as explained in the paragraph "Examples of loading configuration files".

2.You want the users in two titles to have different configuration: make a copy of the main set of configuration files for menus, keyboard and mouse shortcuts, navigators, search dialogs, and preview panels, keeping the same names, store them in separate folders and then edit the files and apply changes you want: this will be the second set of configuration files. In that way you have two sets of configuration files. Create the Everyone2 group (so you have Everyone and Everyone2), and then move the users of the second title to the Everyone2 group. Load the second set of configuration files as shown in the point 2. of the "Examples of loading configuration files" paragraph, putting the appropriate group name, e.g. Everyone2.

3.You want some groups in one title to have different configuration: make a copy of the main set of configuration files for menus, keyboard and mouse shortcuts, navigators, search dialogs, and preview panels, keeping the same names, store them in separate folders and then edit the files and apply changes you want: this will be the second set of configuration files. If you need more than just one variation, then create as many sets as you need, e.g. for Reporters, Editors, Subs etc. Load the appropriate set of configuration files as shown in the point 2. of the "Examples of loading configuration files" paragraph, putting the appropriate group name, e.g. Reporters, Editors, Subs etc.

How it works?

Since the version 2.4. you can load a configuration file not only as in previous versions, at the so-called root level, therefore, equal for all groups and users, but also to a group or a user. If a given configuration exists both on the root, group and user level, the user-level configuration is used. See more details in the "Examples of inheritance" paragraph.

Examples of inheritance

1.A configuration is loaded only on the root level: the root-level configuration is used for all the users (as it was in the versions prior to 2.4).

2.A configuration is loaded on the root level and on one group level: the group-level configuration is used for the members of that group; the root-level configuration is used for all other users.

3.A configuration is loaded on the root level and on the group level and on one user level: the user-level configuration is used that for user; the group-level configuration is used for the members of that group except for the user who has his own; the root-level configuration is used for all other users.

4.A configuration is loaded on the root level and on the user level: the user-level configuration is used that for user; the root-level configuration is used for all other users.

Examples of loading configuration files

1.Loading the file fred4_Tabitems.xml on the user level for the user whose sign in name is jack.

cmd4.exe config -in c:\myfiles\fred4_tabitems.xml -srvurl "http://test.xyz.com/gn4/adminsrv.asmx" -UserName jack -Password abc -who jack

2.Loading the file fred4_Tabitems.xml on the group level for the group whose name is Editors.

cmd4.exe config -in c:\myfiles\fred4_tabitems.xml -srvurl "http://test.xyz.com/gn4/adminsrv.asmx" -UserName jack -Password abc -who Editors

3.Loading the file fred4_Tabitems.xml on the root level:

cmd4.exe config -in c:\myfiles\fred4_tabitems.xml -srvurl "http://test.xyz.com/gn4/adminsrv.asmx" -UserName jack -Password abc 

How to organize all this?

Instead to deal with only one set of configuration files for menus, keyboard and mouse shortcuts, navigators, search dialogs, and preview panels, you will have multiple modified copies of such files. The main set will