This window allows you to define or change the order in which objects should be evaluated if multiple duplicate search configurations apply to a particular user. Each configuration can have one or more objects assigned to it, but each object can only be assigned to one configuration at a time. These objects can be ordered from High Priority (listed first at the top of the list) to Low Priority (listed last at the bottom of the list) by selecting a row and clicking the Move Up or Move Down buttons.
The Object List contains three objects: System, Group, and User. Assigning an object to a configuration indicates that the object is to use the selected configuration by default when conducting a duplicate name search.
|
· If a configuration is assigned to the entire System, then when a Duplicate Name Search is conducted anywhere in J1 Desktop, the specified configuration will be used. · If a configuration is assigned to a Group, anyone logged into J1 Desktop who is a member of that group will use that configuration when doing a Duplicate Name Search. · If the configuration is assigned to a particular user, that user will automatically use the selected configuration during a Duplicate Name Search. Therefore, it is possible for multiple configurations to be valid for a single user based on the roles of which the user is a member, which module they log in to, and the configurations that have been assigned to the various objects. Object priorities should be set so the system can determine which of the valid configurations to use for the logged in user. |
If there is only one configuration defined for all J1 Desktop users, then there is no need to change the object priorities. However, if there will be various configurations assigned to different objects within the system, then the object priorities become very important in the evaluation of which configuration to use by default for each logged in user.
|
Assume that Configuration #1 is defined for the System, Configuration #2 is defined for the ADMANAGER Application group, and Configuration #3 is defined for the user LISA. If Lisa is a member of the ADMANAGER group and she logs in to J1 Desktop, then there would be three possible configurations that could be used as the default when Lisa uses the Duplicate Name Search functionality. Without object priorities, J1 Desktop would not know which of these three configurations to use when Lisa tries to perform a duplicate name search. |
If configurations defined for all three object types are applicable to a J1 Desktop user, then the Duplicate Name Search process will simply use the configurations associated with the object with the highest priority.
|
Using the example above, if the System object has the highest priority, then Lisa would use Configuration #1 by default. If the Group object has the highest priority, then Lisa would use Configuration #2 by default. |
The configuration evaluation is more complex if the logged-in user does not have a configuration assigned to all three of the object types.
|
Assume that the priorities are set in order from highest to lowest as User, Group, and System. · User 1 has a configuration defined for his Application group. There is also a configuration defined for the System. Regardless of which module he logs in to, the configuration associated with the Application group will be used. · User 2 has a User configuration defined, and there is a configuration associated with the System. User 3 will always use his User configuration. · User 3 has no configurations assigned to her User ID or her Application groups, but there is a configuration defined for the System. In this case, the System configuration would be used for all modules. |
If there are no objects for the logged-in user associated with a configuration, including the System object, then the system will use the *DEFAULT configuration.
The Move Up button moves the selected row up one row in the list. If you select the top row, this button is not available.
The Move Down button moves the selected row down one row in the list. If you select the bottom row, this button is not available.
The OK button closes the window and saves changes.
If you made changes and then clicked the Cancel button, you will be prompted as to whether or not you want to save your changes.
· If you click Yes, the changes are saved.
· If you click No, the window closes without saving any changes.