- Whether the calendar starts on Sunday or Monday
- The size of the calendar
- The starting time of the calendar
- The end time of an all-day event
All preferences are stored in the UserPreference table.
Levels
Preferences can be defined at 6 different levels:
User preferences are stored at multiple levels.
We always use the most specific preference for the logged-in user.
UserPreference sample table
The
deflevel value defines which level this preference value is defined at. The values here correspond to the list above.
The 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 deflevel value.
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.