Note: The name of a template must contain alphanumeric, @, #, $, ., :, -, (, and ) characters only. It must not be a number.
The panels used to add a resource template definition for a particular resource class are the same as the panels that you use when you add a resource definition for that class. You can define any information that will be used generically by a specific resource.
You can use a variable to supply the value for a field in the resource template definition.
Variables in a template are substituted by their values when you apply the template to a resource definition. You can disable variable substitution—that is, you want the variable to appear in the resource definition, not the value of the variable.
To disable the substitution of a variable during application, replace the ampersand (&) in front of the variable name by the underline character (_).
For example, if you specify _ZMSGTEXT in a template and apply the template to a resource definition, _ZMSGTEXT becomes &ZMSGTEXT in the resource definition.
Some messages contain left-justified fixed-length fields for resource names. If the name is not of the maximum length, the name is left justified. You cannot use normal variables because they do not provide padding.
To handle left-justified fixed-length fields, use less-than signs (<).
Each < represents one character. For example, <<<<< represents a five-character field with left justification.
Some messages contain right-justified fixed-length fields for resource names. If the name is not of the maximum length, the name is right justified. You cannot use normal variables because they do not provide padding.
To handle right-justified fixed-length fields, use greater-than signs (>).
Each > represents one character. For example, >>>>> represents a five-character field with right justification.
| Copyright © 2012 CA. All rights reserved. |
|