E-mail
Using Recipient().FirstName as the second operand in a condition that restricts recipients will limit recipients to users identified by first name.
Recipient().FirstName is often used in conjunction with Recipient().LastName to specify an individual user. If Recipient().FirstName 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 first name.
new zUserFirstName - In the above example, zUserFirstName is the first operand and corresponds to a character field created in the database to store the first name of a user. Since the operand 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 operand is based on the new value of the field, the term "new" is prepended to the field name (see screen capture above).
equal - In the above example, the operator equal is used to evaluate the condition. Literally, the value in the zUserFirstName field must be equal to the second operand for the condition 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().FirstName. Note the use of the "=" sign before Recipient().FirstName. This is required. By using this MetaScript object, the value in the zUserFirstName 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 notifications).