Variable

Variables are strings of text replaced by contextual data that you can include in a message or a paragraph.

Variables (also sometimes referred to as tokens) are very useful in the creation of customized messages. Variables are most often used in paragraphs within the body of a message but they can also be inserted in the To, Cc, Bcc, and Subject fields.

When creating message templates, you can select variables from a list of standard variables. Standard variables are provided with the system and represent a specific value in the database. For example, if inserting the {Requisition.JobTitle} variable, the message would display the actual requisition title when the message is sent. or you can create custom variables.

If you do not find the variables you need in the list of standard variables, you can create custom variables by following these rules:

  • Custom variables must be enclosed in curly braces { }.

  • Custom variables must contain valid characters: capital letters (A-Z), numbers (0-9) and the underscore symbol (_).

  • Custom variables must contain no spaces.

Custom variables should only be used in messages sent manually since user intervention is required to replace the variables by text strings just before the message is sent. Note that in the case of eShare, there is no interface presented to the user to make such edits, and as such any custom variables that are contained in a message template will not resolve and will display a blank space.

Messages can contain variables associated to user-defined fields (UDFs). Messages will resolve UDFs even if these UDFs are restricted from the user's view access. You should refrain from inserting sensitive data in message templates if you do not want a user to be able to see such information while sending the correspondence.

Standard field viewing permissions are honored when a user sends a manual correspondence. In such cases, fields are not exposed or included in the message sent if the user sending the message is not authorized to view the field.

Note: If not desired for display, users should be advised to remove unresolved variables prior to sending a printed/faxed correspondence. If variables are not resolved, they will appear as unresolved vs. being hidden in the printed file. This precaution is not necessary when sending a correspondences via e-mail.

For a list of variables, see the table List of Variables at the end of the Correspondence chapter. For the most current list of variables, you can go to the Paragraphs feature in the Recruiting Administration menu.