VTech ET685 Administrator And Provisioning Manual page 40

Example:
<ReplacementPlan>
<key id="ResourceListBuddy"
wui_translation_key="fkeys_ssi_buddy_from_server_list">...</key>
<setting_replacement id="user_event_list_uri">...</setting_replacement>
</ReplacementPlan>
Level 1
Element: ReplacementPlan
<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.
Level 2
Element: key defines a key-type that will get listed in fkey-WUI-page as type for a line-key.
Attributes:
id attribute is mandatory and used to define the key type, so it can be deleted or

altered in later provisions.
wui_translation_key attribute is mandatory and used to define the key type, so it

can be deleted or altered in later provisions.
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
firmware version 8.9.3.66).
The subtrees will get additional variables in the beginning of the init-section:



Element: setting_replacement defines a an XML that will be used should the named
setting get set up with non-XMLcontent.
Attributes: id attribute names the setting, currently ONLY user_event_list_uri is valid.
The subtrees will get additional variables in the beginning of the init-section:



Provisioning
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.
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.
40
ET685 Administrator and Provisioning Manual
Back to Contents