E-mail
Using Recipient().LastName as the second operand in a condition used for restricting recipients will limit recipients to users identified by last name.
Recipient().LastName is often used in conjunction with Recipient().FirstName to specify an individual user. If Recipient().LastName is used alone in the condition, it is possible that notifications will get sent to multiple users defined in the system if they share the same last name.
new zUserLastName - In the above example, zUserLastName is the first operand and corresponds to a character field created in the database to store the last name of a user. Since operands can be based on both new and old values of a field (if the notification routine is defined for an updated record event), and in this example the first operand is based on the new value of the field, the term “new” is prepended to the field name (see the screen capture above).
equal - In the above example, the operator equal is used to evaluate the condition. Literally, the value in the zUserLastName field must be equal to the second operand if the condition is to resolve to True for a selected user. (Only users for whom the condition resolves to True receive a notification.)
=Recipient().FirstName - In the example above, the second operand of the condition uses the MetaScript object Recipient().LastName. Note the use of the “=” sign before Recipient().LastName. This is required. By using this MetaScript object, the value in the zUserName field on the record must be equal to the user name of a selected user for him/her to receive a notification. All other selected users are filtered out (do not receive a notification).
Note: Definitions of Operator, Operand, and other technical terms are provided in “Parts of Conditions”.
“Using the Recipient() MetaScript Object” on page 553
“Recipient().Name” on page 555
“Recipient().FirstName” on page 556
“Recipient().EmployeeNumber” on page 560
“Recipient().EmployeeNumber” on page 560