These pages describe the user preferences used in SuperOffice.
Many of these preferences control important system functions, and changing the values or adding a new preference value may cause the SuperOffice application or specific functionality (like Travel or Area management) to stop working. Be very careful when changing these preferences.
Preferences are stored in the
UserPreference table in the database.
Preferences can be defined at 6 different levels:
|3||database-wide (for example, specific to a satellite)|
|4||user-group-wide (all users in a particular group)|
|6||machine-specific (stored in registry under HKLM)|
User preferences are stored at multiple levels.
We always use the most specific preference for the logged-in user.
UserPreference sample table
deflevel value defines which level this preference value is defined at. The values here correspond to the list above.
maxLevel value defines the maximum level at which a preference should be shown in the GUI. Some preferences are not controlled by the user, and can only be edited in the admin tool.
The meaning of the
owner_id depends on the
|3||satellite ID (
|6||not stored in database; stored in registry|
Given the sample data above, a typical user would have the default value for the preference
[MyThing] Volume = "quiet"
since this is the system-wide default.
A user who is in primary user-group 123 would get the value "off" for the same preference since row ID 2 overrides the more general preference in row ID 1.
The user with
associate_id 456 (even if he was in user-group 123) would get his user-specific preference, which is "loud".
The user with
assoicate_id 789 would get the value "quiet" because of the preference with ID 4. The user-specific preference has a higher priority than any of the others, so it is the one that applies.
You can define whatever section and key names you want. You do not need to register your section with SuperOffice. Just start using the section and key names directly.
If there is no value defined, you won't find a user-preference value in the table. Your code should take care to handle empty preferences sensibly.
With no default defined, we get the empty string back.