Siebel Service Handheld Guide > Application Administration >
About Settings in the Handheld Administration Screens
Settings can appear at three levels: Application, Component, or User. Certain settings are only allowed at specific levels.
There are also two types of settings: single-line and multi-line settings. For a single-line setting, only one row may contain a unique setting name at a given level. Thus, a single-line setting at the User level may only be used once at that level. For single-line settings, the Sequence column should always contain a value of zero. For multi-line settings, the sequence column is necessary to allow multiple rows. The sequence column has no effect on actual processing, but is part of the logical key in the database table. When you create a new record in this database table, the record must have a unique logical key. For single-line settings, you may leave the sequence column value alone, which will result in a default value of zero being assigned. For multi-line settings, each line must include a different sequence number to avoid logical key conflicts. If the combination of setting name and sequence number is not unique for a particular parent record (Application, Component, or User), you will receive an error message when stepping off or saving the record. Multi-line entries must contain correct the key values before they can be saved to the database.
The rules for override are that any setting, whether single line or multi-line, specified at the lower levels overrides that same setting name at higher levels. Thus the settings at the application level apply unless specific settings are overridden for a particular component or a particular user. When an override occurs, it occurs for the complete setting name. Thus, if a particular multi-line setting has three rows at the user level and twelve rows at the application level, the resulting multi-line setting value for that setting will contain only the three rows at the user level. There is also an override mechanism to allow a setting to be removed, rather than replaced. To remove a setting from a higher level, specify the setting name to be removed, with an empty setting value.