Windchill System Administrator's Guide

• User scope -- This scope is the lowest level in the hierarchy, and allows
individual users to tailor preferences that allow overrides.
Each scope is controlled by a preference delegate. Documentation on preference
delegates can be found in the wt.prefs.delegates javadoc.
Neither the default delegate, nor the user delegate should be removed from the
system or changed; however, the Windchill Enterprise delegate can be changed or
removed, and additional delegates can be defined.
The preference values at the default scope cannot be removed or changed at
runtime; however, preferences at other scopes can be changed or removed (where
applicable) by a member of that scope.
Using the Preference Administrator, you can create, edit, and remove user
preferences, as described in the following sections. For detailed instructions on
how to create, edit, and remove a user preference, click the Help button on the
Preferences Administrator page. The help also contains a link to a table that
contains a list of the system default user preferences.
Creating a User Preference
You can create any preference by giving it a unique name and a value; however, it
will have no effect unless there is code written to use the preference.
Editing a User Preference
You can edit preferences at any level that are defined as overrideable at that
scope.
Before you change a user preference, you should understand the type of values
that the preference requires (for example, numbers and boolean).
Removing a User Preference
Preference values can be removed from a preference scope. When the value is
removed, the value of existing preferences for lower-level scopes (including the
user) either change or remain the same, depending on the following conditions:
• If overrides are allowed and preferences are set within the scope of the
removed preference, then those preferences retain their values.
• If overrides are allowed and preferences are not set within the scope of the
removed preference, then those preferences are reset to the values of the next
highest-level preference scope.
• If overrides are not allowed and there is a scope that does not allow overrides,
then all preference values below the scope that does not allow overrides are
reset to the values of that scope.
• If overrides are not allowed and the overrides are allowed at all other scopes,
then all preference values are reset to the lowest scope in which a preference
is set.
Administering Runtime Services 1-33