The second set of variables, called attribute variables, is available only if you select the Write To File option when you define the notification method. They are written to the notification file only—not to the environment. They are of the form:
NX_NTF_attribute[.secondary_attribute]=value
where:
The name of the attribute whose value you want to obtain. This is the attribute name as defined for the object. For a complete list of all attribute names for any object, see the CA SDM Technical Reference Guide. The most common objects associated with notifications are the ticket, which has an object name dependent of the type of ticket (for example, cr for requests), and the contact identifying the recipient, which has an object name of cnt. For example, the environment variable for the description attribute of a ticket might look as follows in the notification file:
NX_NTF_DESCRIPTION=This is a sample description.
If the first attribute is an internal identifier for another object, a secondary attribute is often attached to give more meaningful information using the dot notation. In database terms, attribute is a foreign key that points to a row in another table, rather than a simple data value. Using this raw key value would probably have little meaning. To save you the effort, many of these types of fields are resolved or de-referenced for you. When this is the case, secondary_attribute will be the value in the referenced table. For example, instead of writing the value for the assignee attribute, which is actually stored as the unique ID of the contact record for the assignee, the assignee’s combined name is written be referring to the combo_name attribute for the contact object, as shown in the following example:
NX_NTF_ASSIGNEE.COMBO_NAME=Armstrong, Beth
If an attribute does not have a value, the corresponding value is usually (NULL) or blank. For example:
NX_NTF_CALL_BACK_DATE=(NULL)
NX_NTF_GROUP.COMBO_NAME=
Note: An attribute variable that exists for both the ticket and the recipient is NX_NTF_ID (the id attribute), which is the unique database ID for the object.
|
Copyright © 2013 CA.
All rights reserved.
|
|