Thexml replacement plans (<ReplacementPlan> tag) contain xml's that get inserted into the settings when certain conditions are met The <ReplacementPlan> tag can be used either
inside the <settings> tag or
as an individual XML file whose URL is listed inside <setting-files> tag
<ReplacementPlan>knows two sorts of subtrees: <key> and <setting_replacement> (described below)
You may delete plans already on the phone by providing the <key> or <setting_replacement> with the correct id-attribute set but without any subtree-content.
Look here for the syntax of the subtrees of the <key> and <setting_replacement> subtrees.
<key>defines a key-type that will get listed in fkey-WUI-page as type for a line-key
Theidattribute is mandatory and used to define the key type, so it can be deleted or altered in later provisions.
Thewui_translation_keyis used to find the correct translation when listing the key-type in the WUI. If the wui_translation_key is not part of the translation-map, it will be used directly to describe the key in the WUI. Note: renamed and moved to general tag since 8.9.3.66)
The subtrees will get additional variables in the beginning of the init-section:
The variable "ui_argument" will hold whatever is entered in the "Number"-text-field next to the type in the fkey-WUI-page.
The variable "ui_label" will hold whatever is entered in the "Short Text"-text-field next to the number in the fkey-WUI-page (on 8xx only).
<setting_replacement>defines a an xml that will be used should the named setting get set up with non-xml content.
Theid attributenames the setting, currently ONLY user_event_list_uri is valid.
Thesubtreeswill get additional variables in the beginning of the init-section:
The variable "setting_value" contains the exact non-xml setting value that was used for set up.
The variable "setting_index" contains the index of the setting.