This section lists the rules for determining the settings implemented - default settings in HTML session files or user customized
.cph settings.
- No user configuration (.cph) file exists
- The first time the user opens a session no user
.cph file exists. Consequently, the user receives the options defined in the Session Configuration Manager.
- Existing user configuration (.cph) file
-
When a user
.cph file exists, the following rules apply:
- If a
.cph file exists, but no particular option is enabled, the user receives the default options set in the Session Configuration
Manager. This is because you have not given the user permission to modify options. For example, if a user
.cph file exists but you did not select
Enable Edit Options, the user cannot create a customized configuration with features, such as word wrap or type ahead. The user is required to
use the values set in the HTML session file.
- If a
.cph file exists and a particular option is enabled, the user can customize the configuration. For example, if
Enable Edit Options is selected, the user can create a personalized environment that allows features, such as word wrap, type ahead, and keyboard
auto reset. In this case, if you make changes to the HTML session file including those features which the user has customized,
the user
.cph file is not deleted and the customized environment remains in effect.
To enforce the use of the default HTML settings, you should disable the relevant option, for example,
Enable Edit Options. Then the HTML settings override user settings for those options only. All other user configurations remain in effect.