User Interfaces Release 9.1 Subscriber Provisioning Reference Manual "N": The attribute and its value may or may not be defined in the Invoking file. This is not required to be included in the Invoking file. An attribute that has been implemented as 'mandatory' in the system's database cannot have the XML field "mandatory" set to "N". All the attributes that have been implemented as 'optional' in the system's database can either have the XML field "mandatory" set to "Y" or "N". The default value of the XML field "mandatory" is "N".
This means that when the "mandatory" field is not specified, as shown in the example above for the " Provision State " attribute, the attribute and its value are not required in the Invoking file. Template request identification The part of the Command Template that must be used to identify which Template requests to refer to. This field can be created many times to refer to each Template request it uses. In this field, the attribute " tr id " allows to provide the Template request ID number. Invoking file template The Invoking file contains a type of XML Request that is created to support subscriber provisioning requests based on a Template.
An Invoking file can only be created if Template files are already defined in the system's database. An Invoking file (i.e., tp) contains a Template Id and Request template instructions (i.e., tpi). The Template Id identifies which Command Template to use. Each Invoking file instruction provides a specific attribute and value pair that are used to override the default attribute values found in Template requests associated with the specified Command Template. An Invoking file must be created using the following XML structure: override” val=”value”/> … request template instructions Invoking files can be formulated with these following parts:
Template identification Request template instructions Template identification A template tag (e.g., ) must be used to identify the Template and to specify whether or not the attributes that are not mandatory can or cannot be modified. The " template id " attribute allows to identify the template with a Template ID number. This identification will then be used later when provisioning subscribers with an Invoking file (XML "provisioning commands" written in Requests of type template) to refer to the proper template. The template must also be defined by the following attribute: " otherAttributesModifiable ". This XML field can take one of the following two values :
"Y" or "N" to indicate whether or not the values of the attributes defined in the referenced Template requests can or cannot be modified by commands in the Invoking file. The meaning of the two possible values is as follows: 25 910-6701-001 Revision A, June 2013