User Interfaces Release 9.1 Subscriber Provisioning Reference Manual Once Templates have been defined in the database, it can be used (referred to) for subscriber provisioning with an Invoking file. Template file description The XML template file (containing Command Template(s) and Template requests) must be setup so that it is framed by the following XML File tags: template request1 template request2 template request3 Command template 1 Command template2 Firstly, in a Template file, the Template requests must be defined. The Template requests are stored in the original XML request format with the identification of the Template request specified.
This specification is done by including the following additional attribute " id " in the request identification field, as shown in the structure below. … request properties The Command Template Loader supports the following types of Template requests: Update Insert Delete Template requests can be formulated with all or some of these following parts: Request identification Request properties entity identification set of attributes and values criteria For a Template request, only the Request identification part is different from the original XML requests. Request identification A request tag (e.g., ) must be used to formulate the type of template request and to identify it.
The attribute " name "is used to provide the type of template request and it must be followed by the attribute " id " which will identify the Template request with an ID number. This identification will be used by the template to refer to the proper Template request. Secondly, in a template file, the Command Template(s) must be defined and contain the constraints for Template attributes that can be overwritten (that must be modified, can be modified or cannot be modified) and it must also refer to the Template requests it uses. 23 910-6701-001 Revision A, June 2013