Correspondence

Message Templates

Message Template

Message templates are used whenever a notification or e-mail is sent via the application. Message templates can be used, for example, during a process review, an interview scheduling, an approval process, etc.

Message templates are available via the Configuration menu:

Message templates under Configuration (Security) are messages relating to the security of Oracle Talent Acquisition Cloud (OTAC) products. They are system-generated messages provided by Oracle. For details, see Security Message Templates.
Message templates under Specific Configuration are messages specific to each Oracle Talent Acquisition Cloud (OTAC) product. provides system-generated message templates. But new message templates can also be created by system administrators. Paragraphs are added to messages. They can be accessed directly, or from within a message template.

The Message Templates list contains system-generated message templates provided with the product as well as user-defined message templates created by system administrators. User-defined message templates can be edited by system administrators. The properties, context, content, and attachments can be modified. System-generated message templates can also be edited by system administrators. The properties and content can be edited but the context (that is, the recipient, delivery type, triggering event, OLF) cannot be edited. Also note that system-generated message templates cannot be deactivated.

The Message Templates list contains the following columns. All columns (except the Actions column) can be sorted by clicking on the column header.

Code
Name
Status: Active or Inactive.
Delivery Type: Automatic, Manual, Any.
Origin: System or User-Defined.
Creation Date
Last Modification Date
Actions

The Refine by tool in the Message Templates list provides the following options: All, Name, Code, Status, Intended for, Read-only Attachment, Confidential, Used in Status, Used, in Step, Used in Workflow, Language.

Message Template Key Concepts

Several elements are configured when creating message templates.

Message Template Properties: In the Properties section of a message template, the following elements are defined:

Delivery Type: There are two types of delivery mechanisms for messages:
- Automatic: Messages are sent by the system when a specific triggering event occurs during the hiring process. For example, a message is automatically sent when a candidate applied on a requisition. You can also specify if the system will automatically send email messages when a candidate reaches a specific step/status in a candidate selection workflow. For example, you can automatically have the system send a Congratulatory message when a candidate is moved to the Hired step.
- Manual: Recruiting Center users may decide to send messages to candidates when taking actions on a candidate file or from a candidates list.

Message Format: A message template can be created in different formats:
- Read only PDF file: The message is converted into a read-only PDF file that is attached to the e-mail. This prevents candidates and other users from modifying the message. The sender has the opportunity to enter a plain text introduction message before sending it which is displayed in the body of the e-mail.
- HTML: The contents of the message are displayed in the body of the e-mail in HTML. A HTML copy of the message is also included as an attachment with the label "this_message_in_html.htm". The attachment is for those who cannot read HTML in the mail reader or, in some cases, where the contents do not render perfectly well.
- Plain text: The contents of the message are not displayed in the body of the e-mail, and are replaced with the text "The details of this message can be viewed by opening the enclosed attachment. Replies to this message are undeliverable. Please do not reply." A HTML copy of the message is included as an attachment with the label "this_message_in_html.htm". The attachment is for those who cannot read HTML in the mail reader or, in some cases, where the contents do not render perfectly well. For those without the ability to read HTML in their e-mail, they will not be exposed to wacky HTML content. Instead, they see only a clean plain text that instructs them to open the attachment containing the message (that will open an HTML reader (browser).
Confidentiality: If selecting the Once sent, this message is confidential option, the content of the message can only be viewed by the sender of the message, by users who have the permission to view confidential messages, and by the recruiter, the recruiter assistant, the hiring manager, and the hiring manager assistant. From the candidate file History tab, users can see that a confidential message was sent but they cannot view the content if they don't have the required permission.

Message Header: The message header contains the To, Cc, Bcc, and Subject fields where variables can be dragged and dropped. These variables will automatically call information from the system and display it in the template.

Context: When creating a message template, a context can be defined in order to specify in which specific conditions the template will be used. In the Context section of a message template, the following elements are defined:

Recipient: You can specify who will receive the message:
- All Candidates
- Internal Candidates
- External Candidates
- Referrer
- Agent
- Recruiting User
Note: When more than one message template is associated to the same triggering event, the system must be able to match the correct message to send to the recipient based on audience type. We are able to create a duplicated message template with a customized audience, and when the automatic message is triggered, the system will send the correct version for that audience type, even if there is more than one possible match due to the "all candidates" selection. If a candidate is internal and an internal only audience template exists for the triggering event, the internal candidate(s) will only receive that internal audience message, even if another template exists for all candidates. If a candidate is external and an external only audience template exists for the triggering event, the external candidate(s) will only receive that external audience message, even if another template exists for all candidates.
Delivery Type: While you first indicated the delivery type in the Properties section (Automatic or Manual), you now need to define the details in the Context section, that is the triggering event or the candidate selection workflow, step and status.
Organization-Location-Job Field Association: If contextualization is configured for a message template, the template is available only if the Organization-Location-Job Field structure of the message template matches the Organization-Location-Job Field structure of the object for which the template is being used. Note that the message template contextualization only looks at the Primary Location of a requisition; the "Other Locations" are not considered. For example, if a message template is created to be triggered for each new job posting in Antarctica, then the message template will be sent only for a requisition with Antarctica as a Primary Location. Note that when sending a message in the context of a candidate's General Profile, no OLF association exists, so all messages are available regardless of the message OLF context.

Paragraphs: You define the content of the message by working with paragraphs. You can add existing paragraphs or create new ones.

Attachments: Files can be attached to message templates.

Variables: Messages can contain variables (or "tokens"). For example, if inserting the {Requisition.JobTitle} variable, the message would display the actual requisition title when the message is sent.

Paragraph

A paragraph is a block of text added to a message template.

Paragraphs can be accessed from two places:

Paragraphs list: The Paragraphs list is available via the Paragraphs link in the product administration menu and via the Quick Access box within the Message Templates feature.
Message templates: Message templates are available via the Message Templates link in the product administration menu and via the Quick Access box.

The Paragraphs list contains the following columns. All columns (except the Actions column) can be sorted by clicking on the column header.

Code
Name
Status: Active or Inactive.
Creation Date
Last Modification Date
Actions

The Refine by tool in the Paragraphs list provides the following options: All, Code, Language, Name, Status, Text. When users enter text in the Text option and click Refresh, the system will display only the paragraphs that contain the text. Note that the text field is not case sensitive. Also, the search is performed for the selected language only.

Paragraphs can be created from either the Paragraphs list or from within a message template. When creating a paragraph from the Paragraphs list, the paragraph is available for new and existing message templates. When creating a paragraph from within a message template, the system administrator is prompted to choose whether or not the newly created paragraph should be added to the Paragraphs list. If choosing Yes, the paragraph becomes available in the Paragraphs list to view, edit, and configure. If choosing No, then the paragraph can only be accessed from within the message template.

Paragraph content is created by typing text and/or by adding variables. Variables automatically call information from the candidate file or job specific submission and display it in the template. For example, if the {Candidate.LastName} variable is used, then the last name of the candidate will be automatically included by the system in the outgoing message. By default, all variables are listed in the Available Variables list. However, a shorter list of variables can be displayed by entering a few letters contained in a variable. The system then automatically suggests variables containing these letters. For example, if entering the letters "add", the system could suggest the following variables: "Candidate.Address", "Candidate.Address2", "ElectronicSignature.IpAddress". Once the right variables are displayed, the system administrator can drag and drop the desired variables in the paragraph. To return to the default list of variables, the system administrator just needs to remove the letters they entered.

Paragraphs can be supplied with the system (message templates supplied with the system have default paragraphs attached to them). They can also be duplicated (when duplicating a message template, paragraphs can be duplicated) or they can be created from scratch.

Edits made to a paragraph in the Paragraphs list will affect all message templates using the paragraph, regardless of whether the edits are made directly from within a message template or from within the Paragraphs list.

When viewing a paragraph (by clicking the name of the paragraph), a section called Used In is available. Within this section, users can:

See the list of message templates where the paragraph is used in.
Open the message templates where the paragraph is used in. Users have the ability to modify the message templates from there.
See if the paragraph is included by default in the message templates.
Preview the message templates with the paragraph in it. When previewing a message template, all the paragraphs included by default in the message template are displayed. The paragraph from which the message template was opened is highlighted in yellow if more than one paragraph is included in the message template.

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.

Editable Message Templates

Message Template	Product
Activity Reminder, Recruiter / Task Reminder, Recruiter	Recruiting
ACE Alert Notification	Recruiting
Attached File Contains Invalid Resume Information, Agent	Recruiting
Attached File Contains Invalid Resume Information, Candidate	Recruiting
Attached File Contains Invalid Resume Information, Recruiter	Recruiting
Attached File Contains Virus, Agent	Recruiting
Attached File Contains Virus, Candidate	Recruiting
Attached File Contains Virus, Recruiter	Recruiting
Business Card Request	Legacy Onboarding
Candidate Account Locked	Recruiting
Candidate Matched to Requisition	Recruiting
Completing Online Assessment Questionnaire	Recruiting
Completing Online Assessment Questionnaire (Post-application)	Recruiting
Completing Online Screening Questionnaire	Recruiting
Completing Online Tax Questionnaire	Recruiting
Computer Reminder	Legacy Onboarding
Contribution Request, Agent	Recruiting
Daily Recruiting Report	Recruiting
Duplicated Candidate Email, Agent	Recruiting
Duplicated Candidate Email, Candidate	Recruiting
Duplicated Candidate Email, Recruiter	Recruiting
EEO, Invitation to Self-Identify	Recruiting
Error in Attachments, Agent	Recruiting
Error in Attachments, Candidate	Recruiting
Error in Attachments, Recruiter	Recruiting
ERT, Job-Specific Referral, New Candidate	Recruiting
ERT, Job-Specific Referral, Registered Candidate	Recruiting
ERT, Job-Specific, Referrer	Recruiting
ERT, Unsolicited Referral, New Candidate	Recruiting
ERT, Unsolicited Referral, Registered Candidate	Recruiting
ERT, Unsolicited, Referrer	Recruiting
Fax Cover Sheet	Recruiting
Forgot Password	Recruiting
Forgot User Name	Recruiting
Interview Notification	Recruiting
Invitation to Refer Candidates	Recruiting
Job Posting Notification	Recruiting
Job Search Agent Notification	Recruiting
Job-Specific Application Acknowledgement	Recruiting
Job-Specific Capture Resume Acknowledgement, New Candidate	Recruiting
Job-Specific Capture Resume Acknowledgement, Registered Candidate	Recruiting
Job-Specific Referral, Agent	Recruiting
Merge of Candidate Files, Agent	Recruiting
Merge of Candidate Files, Candidate	Recruiting
Missing Attachments, Agent	Recruiting
Missing Attachments, Candidate	Recruiting
Missing Attachments, Recruiter	Recruiting
Notification Email to the Process Owner	Legacy Onboarding
Notification for a media placement request	Recruiting
Notification for a requisition approval event	No context specific
Notification for a sourcing strategy request	Recruiting
Notification for an Internet mining request	Recruiting
Offer Approval Decision Notification	Recruiting
Offer Approval Final Decision Notification	Recruiting
Offer Approved	Recruiting
Offer Rejected	Recruiting
Rejection Letter	Recruiting
Rejection letter - Requisition closed	Recruiting
Request contribution	Recruiting
Request More Info	Recruiting
Requisition Approved	Recruiting
Requisition Canceled	Recruiting
Requisition Filled	Recruiting
Requisition On Hold	Recruiting
Requisition Reactivated	Recruiting
Requisition Rejected	Recruiting
Resume Parsing Service Unavailable to Agents	Recruiting
Resume Parsing Service Unavailable, Agent	Recruiting
Resume Parsing Service Unavailable, Candidate	Recruiting
Resume Parsing Service Unavailable, Recruiter	Recruiting
Selection Assessment Request (Candidate)	Recruiting
Selection Assessment Request (Recruiter)	Recruiting
Selection Assessment Request (Recruiter) ñ Candidate Email Missing	Recruiting
Send Job to Friend	Recruiting
Share Candidate Notification	Recruiting
Sourcing Event Notification	Recruiting
Standard notification for a candidate account confirmation	SmartOrg
Standard notification for a First Login	SmartOrg
Standard notification for a First Login	Legacy Onboarding
Standard notification for a Forgot Password	Legacy Onboarding
Standard notification for a Forgot Username	SmartOrg
Standard notification for a Password Reset	SmartOrg
Standard notification for a Password Reset	Onboarding
Standard notification for a posting about to expire	Recruiting
Standard notification for a registration	SmartOrg
Standard notification for a reminder	No context specific
Standard notification for a reminder	Onboarding
Standard notification for a Request Approval	Recruiting
Standard notification for a requisition approval	Recruiting
Standard notification for a self-registration	Recruiting
Standard notification for a self-registration	SmartOrg
Standard notification for an expired posting	Recruiting
Standard notification for the Offer approval	Recruiting
Standard notification to fill out a user-defined form	Legacy Onboarding
Standard notification to fill out a user-defined form	No context specific
Submission Progression Notification	Recruiting
Unsolicited Application Acknowledgement	Recruiting
Unsolicited Capture Resume Acknowledgement, New Candidate	Recruiting
Unsolicited Capture Resume Acknowledgement, Registered Candidate	Recruiting
Unsolicited Email Application Acknowledgement, Agent	Recruiting
Unsolicited Email Application Acknowledgement, Candidate	Recruiting
Unsolicited Referral, Agent	Recruiting
Workflow Event Notification	Recruiting

Data Security in Correspondence

Data security is handled for correspondence sent manually by Recruiting Center users as well as correspondence sent automatically by the system.

For correspondence sent manually by a Recruiting Center users:

The data that can be included in the message body and that is rendered in the message preview as well as in the outgoing message is constrained to data that the message sender is authorized to view.
The security level of user-defined fields (UDFs) is not considered when a user sends a message. These fields still appear to the message sender even if the user is not able to otherwise view such data. It is therefore recommended to not use confidential UDFs in message templates where exposure to this data may cause concern.
If a user is not authorized to view a field that is included in a correspondence, the field will be blank both for the message sender as well as the message recipient. Fields may not be visible because the field is at a security level that the user is not authorized to view or the field is a Screening Service field and the user is not able to view that type of service result. If a user tries to print a correspondence, the variables will render and appear unresolved rather than being stripped out.

For correspondence sent automatically by the system:

The visibility of data is set according to the message recipient's permissions. If the message recipient is a candidate or referrer, there is no restriction. If the message recipient is a Recruiting Center user, the message is sent according to the restricted security profile.
UDFs are not considered when messages are sent. Regardless of message recipients or senders viewing permission, UDF variables are always resolved.

Security restrictions are applied on sent correspondence. If a user does not have sufficient permission, the user can see the "Correspondence sent" tracking event in the candidate file History tab but when clicking the correspondence to view its content, the following error message will be displayed: "Your user permission does not authorize you to view this message." To view the content of a sent correspondence, users must have the required security level permissions.

Users having the "general" permission access will only see messages including fields set at the "general" security level.
Users having the "restricted" permission access will see messages including fields set at the "general" and "restricted" security levels.
Users having the "confidential" permission access will see messages including fields set at all security levels, that is "general", "restricted", and "confidential".

There are also security restrictions regarding the display of confidential and non-confidential correspondence in the candidate file History tab:

If a message is non-confidential, all users can see the "Correspondence sent" tracking event.
If a message is confidential, only users having the permission "View Confidential Messages" can see the "Correspondence sent" tracking event.

When viewing a correspondence, users must have the proper permissions to view specific data. For example, to view a correspondence that contains an attachment and requisition fields with a security level set to "Restricted", users must have the "Security level for requisitions (in view mode)" permission set to "Restricted" or "Confidential" as well as the "Access Attachments tab" permission.

Category of Data	Required Permission	Permission Location
Current job data	View candidate current job terms	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Offers
Competitive data	View competitive offer details	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Offers
Expectation data	View and capture candidate expectations	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Offers
Offer data	View offers	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Offers
Compensation data	View Compensation section in requisitions	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Requisitions
Attachments	Access Attachments tab	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Other attachments	View other attachment	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates

Enhancements to the way security is handled in correspondence have brought a change in behavior regarding selected recipients. For automatic message templates, the system will send the message to the recipient audience identified on the message template as configured in the Correspondence Manager, as well as any other recipients indicated in the message header fields (To/Cc/Bcc). To enable customized notifications to users, an exception exists for automatic messages triggered by the Candidate Selection Workflow Context triggering event (Configuration > [Recruiting] Message Templates > Context). For this trigger only, the system will behave differently. Messages sent automatically by the Candidate Selection Workflow Context triggering event will be sent to the recipient if the selected recipient audience is either "External Candidates" or "Internal Candidates;" otherwise, for all other audiences the system will only deliver the message to those recipients identified in the message header fields (see table below). As with all automatic messages sent by the system, Recruiting Center user recipients will only receive messages with tokens resolved for General or Restricted fields, while messages sent to Candidate and Referrer recipients will resolve confidential tokens. Be sure to consider this point when configuring messages triggered by the Candidate Selection Workflow Context triggering event.

Recipient	Automatic triggering event	Delivered to the recipient?	Delivered to the recipients defined in the To, Cc, and Bcc fields
All candidates	Candidate Selection Workflow Context	No	Yes
Internal candidates	Candidate Selection Workflow Context	Yes	Yes
External candidates	Candidate Selection Workflow Context	Yes	Yes
Referrer	Candidate Selection Workflow Context	No	Yes
Agent	Candidate Selection Workflow Context	No	Yes
Recruiting User	Candidate Selection Workflow Context	No	Yes

Message Template Configuration

Creating a Message Template

The creation of message templates consists of the following steps.

Defining the Message Properties

The Access Correspondence Manager configuration user type permission is required.

Configuration > [Recruiting] Message Templates

Click Create.
Enter a code, a name, and a description.
Select the message format.
Select a delivery type.
Specify if the message is confidential.
Complete fields in the message header by adding variables.
1. Scroll the list of variables to find the desired variable. To display a short list of variables matching a specific keyword, you can enter the keyword in the Available Variables field. For example, entering candidate would display all variables containing the word candidate.
2. In the list of variables, select the variable (including curly braces) with your cursor.
3. Drag the variable in the desired location.
Click Save.

Defining the Message Context

The Access Correspondence Manager configuration user type permission is required.

Configuration > [Recruiting] Message Templates

In the message template, click Edit next to Context.
Select the recipients.
Select the delivery type.

If selecting the automatic delivery, select the triggering event.

If selecting the manual delivery, indicate if the message template will be available for all candidate selection workflows or for a specific workflow, step or status.
Associate the message template to an Organization, Location, Job Field.
Click Save.

Adding a Paragraph to the Message Template

The Access Correspondence Manager configuration user type permission is required.

The paragraph must be created and activated.

Configuration > Message Templates

In the message template, click Add next to Paragraphs.
Select one or several paragraphs.
Click Select.

The paragraph appears in the Paragraphs section of the message template.

Creating a Paragraph for the Message Template

The Access Correspondence Manager configuration user type permission is required.

Configuration > Message Templates

In the message template, click Create next to Paragraphs.

A message appears asking you if you want to add the new paragraph in the paragraph library so that it can be reused in other message templates.
Enter a name and a code.
Type the content of the paragraph in the Text box. You can add variables in the text and format the text using the RTF Editor options.
Click Save.

The paragraph appears in the Paragraphs section of the message template.

Ordering Paragraphs in the Message Template

The Access Correspondence Manager configuration user type permission is required.

Configuration > Message Templates

In the message template, click Reorder next to Paragraphs.
Select a paragraph you want to move to a different position.
Use arrows to move the paragraph.
Click Save.

Adding an Attachment to the Message Template

The Access Correspondence Manager configuration user type permission is required.

By default, the attached file maximum size is 1 Mb (setting Attached File Maximum Size).

By default, the maximum number of file attachments allowed per entity record is 10 (setting Attached File Maximum Number).

Configuration > Message Templates

In the message template, click Add next to Attachments.
Enter a code.
Click Browse... to select a document.
Click Save.

The attachment appears in the Attachments section of the message template if the size is below or equal to the maximum size allowed for attachments.

Activating the Message Template

The Access Correspondence Manager configuration user type permission is required.

The message template must have an Inactive or Draft status.

Configuration > Message Templates

In the message template, click Activate.

The status of the message template is Active and is now available to Recruiting Center users when they send messages.

Sending Messages to a Corporate Email Address

Email messages sent with the Correspondence Manager in the Recruiting Center, the Onboarding (Transitions) Center and Career Sections can be sent to a corporate email address.

Some customers need to send all correspondences to a corporate inbox in order to keep a copy of all the messages that were sent.

A setting was created to allow the configuration of a corporate email address. This corporate email address will automatically be added to the Bcc field of a message template (but will be hidden to users) and a copy of all email messages will be sent to that email address. The correspondences that are archived are those sent to all candidates, internal candidates, and external candidates.

Configuration

To send all email messages to a corporate email address, system administrators must configure this setting by adding an email address.

Setting	Description	Location
Bcc address in Correspondence Manager	Email address added to the Bcc field of all Recruiting, Career Section and Onboarding (Transitions) emails sent through the Correspondence Manager.	Configuration > [Configuration] Settings

When creating a message template, if a value is entered in the Bcc field, the email message will be sent to the Bcc field recipient as well as to the email address entered in the new Bcc setting.

Message Template - Permissions and Settings

The following permissions and settings are used to configure message templates and correspondence.

User Type Permission	Location
Access Correspondence Manager configuration	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Administration
Send correspondence (using the Send Correspondence action)	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Send correspondence (while changing the status of a candidate in a workflow)	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Customize messages before sending (using the Send Correspondence action)	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Customize messages before sending (while changing the status of a candidate in a workflow)	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Send messages created from scratch (using the Send Correspondence action)	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Send messages created from scratch (while changing the status of a candidate in a workflow)	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
View confidential messages	Configuration > [SmartOrg] Administration > [Users] User Types > Recruiting > Candidates
Allow users to attach documents in message templates	Configuration > [SmartOrg] Administration > [Users] User Types > Configuration > Security Management

Setting	Description	Default Value	Location
Correspondence Manager Search Order	When two or more message templates are equally relevant, select the nearest match based on order specified here.	By Job, By Location, By Organization	Configuration > [Recruiting] Settings
Display "Reply To" Field	Indicates whether or not to display the "Reply To" field.	No	Configuration > [Recruiting] Settings
Email Attachment Extension	Used to specify the extensions to be used for email attachments (0=No Attachment, 1=HTML, 2=HTM, 3=HTML+HTM, 4=HTM+HTML).	1=HTML	Configuration > [Recruiting] Settings
Email Type Sent to Users	Determines the type of email type sent to users of Recruiting Center (HTML or plain text).	HTML	Configuration > [Recruiting] Settings
Sender Email Address	Default email address used in the system-generated emails sent to the users.	hr-empty @invalid email.com	Configuration > [Recruiting] Settings
Sender Email Address Alias	Name assigned to the email sender. Aliases are multilingual, but if no value is provided in a given language, the English value is used by default.		Configuration > [Recruiting] Settings
Bcc address in Correspondence Manager	Email address added to the Bcc field of all Recruiting, Career Section and Onboarding (Transitions) emails sent through the Correspondence Manager.		Configuration > [Configuration] Settings
Attached File Maximum Number	The maximum number of file attachments per entity record allowed.	10	Configuration > [Configuration] Settings
Attached File Maximum Size	Maximum size of a file attachment (in bytes) allowed.	1 Mb	Configuration > [Configuration] Settings

Message Template - Other Configuration Tasks

Editing the Properties of a Message Template

The Access Correspondence Manager configuration user type permission is required.

It is a best practice to deactivate the message template before modifying a message template. When edits are completed, the message template should be reactivated.

Configuration > Message Templates

Click Message Templates.
Click a message template.
Click Edit next to Properties.
Modify the information.
Click Save.

Modifications made to the code, name, description, message format and message header variable(s) used in the message are automatically reflected in messages sent using this template.

Duplicating a Message Template

The Access Correspondence Manager configuration user type permission is required.

Configuration > Message Templates

Click Message Templates.
Click Duplicate next to the desired message template.
Make required changes.
Click Save.

The message template appears in the Message Templates list.

Deactivating a User-Defined Message Template

The Access Correspondence Manager configuration user type permission is required.

The message template must have the Active status.

Configuration > Message Templates

Click Message Templates.
Click a message template.
Click Deactivate.

The status of the message template is Inactive. The template can no longer be used by Recruiting Center users to send messages, but the template is not permanently deleted from the database.

Deleting a Message Template

The Access Correspondence Manager configuration user type permission is required.

The message template must have the Draft status.

Configuration > Message Templates

Click Message Templates.
Click Delete next to the desired draft message template.
Click Yes.

The message template is permanently deleted from the database.

Removing an Attachment from a Message Template

The Access Correspondence Manager configuration user type permission is required.

Configuration > Message Templates

Click Message Templates.
Click a message template.
Click Remove next to the attachment.

The attachment no longer appears in the Attachments section of the message template.

Editing a Paragraph in a Message Template

The Access Correspondence Manager configuration user type permission is required.

Deactivate the message template before modifying a paragraph.

Note that any edits will affect all templates that use the paragraph, so edit with care. User may chose to duplicate the paragraph and then edit the new version only.

Configuration > Message Templates

Click Message Templates.
Click a message template.
In the Paragraphs section, click Edit next to the paragraph.
Modify the information in the fields.
Click Save.

Previewing a Paragraph in a Message Template

The Access Correspondence Manager configuration user type permission is required.

You must be in the active language of the message template.

Configuration > Message Templates

Click Message Templates.
Click a message template.
Click Preview.

Activating a Paragraph in a Message Template

The Access Correspondence Manager configuration user type permission is required.

The paragraph must have the Inactive status.

Configuration > Message Templates

Click Message Templates.
Click a message template.
In the Paragraphs section, click the paragraph.
Click Activate.

The status of the paragraph is Active and is now available for selection when adding a paragraph in a message template.

Deactivating a Paragraph in a Message Template

The Access Correspondence Manager configuration user type permission is required.

The paragraph must have the Active status.

Configuration > Message Templates

Click Message Templates.
Click a message template.
In the Paragraphs section, click a paragraph.
Click Deactivate.

The status of the paragraph is Inactive and the paragraph can no longer be selected in a template. The paragraph is not permanently deleted from the database.

Adding a Variable in a Message Template

Configuration > Message Templates

Configuration > [Product] Message Templates

Select a message template.
To add a variable in the To, Cc, Bcc, and Subject fields, click Edit next to Properties.
To add a variable in a paragraph, click a paragraph.
Scroll the list of variables to find the desired variable.

To display a short list of variables matching a specific keyword, you can enter the keyword in the Available Variables field. For example, entering candidate would display all variables containing the word candidate.

To display the complete list of variables, simply remove the keyword you entered.
In the list of variables, select the variable (including curly braces) with your cursor.
Drag the variable in the desired location.

When sending the message, the variable is replaced by contextual data.

The system may be unable to replace a variable because:

The data is missing; the variable place holder will be left blank.
The variable is invalid in the context; the variable will be replaced by a blank for automatically sent messages.
For manually sent messages, the variable will be left blank.

Uploading Company Logos for Message Templates

The logo must respect the following criteria:

Must be a .GIF file.
Must have the desired size as it will not be resized by Oracle. Maximum size allowed is 300 KB.
A maximum of 30 logos can be uploaded.
After upgrading to version 13A, the current logos will not show in the settings themselves but they are still available in the zone.

Configuration > [General Configuration ] Settings

In the Refine by list, select Category, then Corporate Branding, and click Refresh.
Select one of the Custom Correspondence Logo setting.

For example, Custom Correspondence Logo 01.
Click Edit.
Click Browse to select an image.
Click Save.

The company logo is now available to be added in message templates. To preview your logo after it has been uploaded, access this link and replace ZONENAME by the proper zone name and XX by the actual logo id (01 to 30): http://zonename.taleo.net/custom/images/company_logo_XX.gif

When changing an existing company logo, the logo is updated everywhere, including past offer letters. In an offer letter, the logo is saved as a link to the logo. As a result, changing the logo will also update the logo in past offer letters. A workaround would be to upload a new logo using another Custom Correspondence Logo setting instead of changing an existing logo setting.

Adding a Company Logo in a Message Template

Configuration > Message Templates

Configuration > [Recruiting] Message Templates

Select a message template.
To add a company logo in a paragraph, click on a paragraph.
Click Edit next to Properties.
Scroll the list of variables to locate the variables called {Other.CompanyLogos}. There are 30 variables for logos.
Select the variable (including curly braces) with your cursor.

For example, select {Other.CompanyLogos1}.
Drag the variable in the desired location in the Text box.
Click Save.

When the message is sent, the variable is replaced by the company logo that was uploaded in one of the Custom Correspondence Logo setting.

Allowing Candidates to Reply Directly to a Message

The Access Correspondence Manager and Message templates user type permissions are required.

The Display "Reply To" Field setting must be enabled (Recruiting Settings).

Configuration

Click Message Templates for the desired product.
Click Edit.
In the Reply To field, enter the email address of the recipient that you want to allow to reply to the message.

Alternatively, you can copy a variable from the Variables list and paste it into the Reply To field.
Click Save.

The Reply To field is displayed in the Correspondence Wizard in the Recruiting Center. If users have the permission to edit messages, they can edit the address displayed in the Reply To field. When candidates receive the email message, they have the option of clicking Reply in their email reader and the message is sent to the address you indicated in the Correspondence Manager.

Notifications

Notification

A notification is an e-mail message automatically sent by the system to notify Recruiting Center and eShare users of key workflow events affecting the recruiting and hiring cycle.

The system administrator can choose whether to send or not send an e-mail for a given triggering event. For example, notifications can be sent for:

Job posting
Approval process
End of sourcing
Candidate selection (when a candidate applies, starts or completes an interview step, when an offer is made, etc.)
Requisition being closed
Requisition being put on hold

When the system administrator chooses to send a notification, the system automatically chooses the message template with the corresponding triggering event.

eShare approval request (offers and requisitions) e-mails have an expiration date of 30 days. This date cannot be changed, but permitted users can resend a stalled approval request.

Job Posting Notification

In the Recruiting Center, in the requisition file Posting and Sourcing tab, when the Email this job posting to matching candidates option is selected, the system matches all the candidates that have the Required criteria to the requisition being posted. Candidates who have all the Required criteria will receive an email inviting them to apply on the job that is posted.

To receive this Job Posting Notification, the candidate must:

Have selected "Please email job postings" in the candidate profiler.
Have a valid email address.
Have not yet applied on the requisition.
Have not yet been invited to apply on the requisition.
Match the selections marked as required in the requisition.

If the requisition is posted on a least one external career section (whether or not it is posted on an internal career section), all the candidates who match the Required criteria will receive a Job Posting Notification.

If the requisition is posted only on an internal career section, only the internal candidates will receive a Job Posting Notification.

Workflow Event Notification

Workflow Event Notifications (WEN) are typically sent when the status of a requisition changes, during an approval process, or when there is a new applicant on a requisition. This notification is sent to the Recruiter, the Recruiter Assistant, the Hiring Manager and the Hiring Manager Assistant. Note that a user who is both the Recruiter and the Hiring Manager of a requisition may receive duplicate notifications for a given candidate.Workflow Event Notifications (WEN) are configured under Configuration > Recruiting Administration > Notifications. See the list of workflow event notifications.

For security reasons, the candidate file is not attached to the notification e-mails. Instead, these e-mails can be configured to include a "deep link" variable that gives deep link access to the candidate file. (Note that no configuration is required for newer customer implementations because the Workflow Event Notification message template already includes the variable).

The {Candidate.CandidateSubmissionUrl} variable can be added to the standard Workflow Event Notification message template or other message templates if desired. When receiving the notification, users must click the hyperlink contained in the message to access the candidate file (note that users must be authenticated, either by signing in or with Single Sign-On). The candidate file is no longer included in the message. The variable is available for use in any message template; however, if placed in a context where there can be no referenced job submission, the link will not work.

Note that if users have the required permission, they can control via the My Setup feature if they want to be kept informed of workflow events by email.

New Entry Event Notifications (NEEN)

New Entry Event Notifications (NEEN) are configured in a specific step or status of a Candidate Selection Workflow (CSW) to notify the recipient(s) when a new candidate enters this specific step or status. This notification is sent to the Recruiter Assistant and/or Hiring Manager Assistant if they exist, otherwise to the Recruiter and/or Hiring Manager. Note that two notifications can be received by a single recipient if it is configured at both the step and the status level reached by a candidate.

Notification - Settings

The following settings are used to configure notifications.

Setting	Description	Default Value	Location
Workflow Event Notification	Keep the user informed of workflow events by email.	By Job, By Location, By Organization	Configuration > [General Configuration] Settings
Job Posting Notification (Internal Candidates)	Email job postings to matching internal candidates.	No	Configuration > [Recruiting] Settings

User Account General Preference	Description	Default Value	Location
Workflow Event Notifications	For the Workflow Event Notifications feature to be available to Recruiting Center users, the system administrator must activate it in the user account's general preferences. Once activated, users with access to the My Setup feature in the Recruiting Center can update their preferences and override the value selected by the system administrator.	Yes	Configuration > [SmartOrg] Administration > [Users] User Accounts > General Preferences

Workflow Event Notifications

The following table presents the criteria under which a workflow event notification can be triggered.

These criteria are available under Recruiting Administration > Notifications.

Notification	Usage
Approval Process Notification
Send notification about the approval process Every time an approval event (decision or termination) occurs But not if the user chooses to pass Only when final (the status changes to Approved or Rejected) But not if the approval is granted	Notifications for a requisition approval event
Posting Notification
Send notification about new postings Only for the first posting For every new posting	Notifications for a sourcing event
End of Sourcing Notification
Send notification when sourcing ends But only if it has expired Send notification when posting is about to expire	Notification for a sourcing event Notification for an expired posting Notification for a posting about to expire
Candidate Selection Notification
Send notification when candidates apply But only if they have all the required criteria But only if they are an ACE candidate Do not notify users to whom an ACE candidate alert is sent Send notification when a candidate starts or completes an Interview step Send notification when an offer is made Send notification when a candidate is hired	Notifications for a workflow event
Requisition Closing Notification
Send notification when a requisition closes But only if it is canceled	Notifications for a sourcing event
Requisition On Hold Notification
Send notification when a requisition is put on hold or reactivated But only if it was posted	Notifications for a sourcing event

Activating a Notification

Configuration > [Recruiting] Administration > Notifications

Select the desired notifications and related options.
Click Save.

For notifications configured in the Notifications feature of the Recruiting Administration menu, the user account preference must indicate if the user wishes to receive workflow notifications. For all other correspondence messages configured within the correspondence manager, the user will receive messages regardless of the configured notifications preference.

The notifications are enabled. E-mails will be sent automatically by the system when selected notifications and options are met.

In SmartOrg, activate the user preference in user accounts entitled Workflow Events Notification. E-mails will be sent automatically when selected notifications and options are met.

Including a Deep Link Variable in a Workflow Event Notification

Configuration > [Recruiting] > Message Templates

Locate the Workflow Event Notification message template.
In the Paragraphs section, click on the paragraph entitled Standard notification for a workflow event.
Click Edit next to Properties.
In the Available Variables field, locate the {Candidate.CandidateSubmissionUrl} variable.
Convert the variable into a hyperlink.
1. Select the text that will contain the hyperlink to the file.
2. Click the Insert or Edit Link icon.
3. Select URL in the Link Type field, select Other in the Protocol field, "and type {Candidate.CandidateSubmissionURL} in the URL field.
4. Click OK.

The paragraph now contains the hyperlink that will take the recipient directly to the candidate's submission.

You can follow the same steps to add the variable to other paragraphs.

Sensitivity Level of Messages and Notifications

Setting the Sensitivity Level of Messages and Notifications

Notifications and email messages sent by Oracle Talent Acquisition Cloud (OTAC) can be set to a specific sensitivity level. This feature applies to messages sent from the Recruiting Center, Onboarding (Transitions), Career Section, Evaluation Management, Performance and SmartOrg.

Notifications and email messages can contain sensitive data that only the intended recipient should see. Notifications and email messages can be configured as Private. When customers client email servers (such as Microsoft Outlook) are configured to respect message sensitivity, this can help ensure unintended recipients do not see the content of messages flagged as private.

Four levels of mail sensitivity are available, corresponding to those in Microsoft Outlook:

Confidential
Normal
Personal
Private

The default setting is Normal, meaning when a person receives an email, its sensitivity level is Normal. If the mail sensitivity configuration is set to Private, when a person receives an email, its sensitivity setting is Private. By default, all messages are set to the same level of sensitivity, as configured by a global setting. However, the system administrator can override the global setting value by configuring the sensitivity level of specific email messages. The system will detect the sensitivity level specified in configuration and provide it to the Correspondence Manager, which will send out messages with the appropriate sensitivity. In environments where message sensitivity levels are respected by the client email server, only the intended recipients will be able to receive and view the contents of messages marked as private. For this feature to work the customer's email client must be configured to respect these mail sensitivity settings.

For example, a company has set the sensitivity level of a message to Private. A user outside the company shares their Microsoft Outlook inbox with an administrator. The user applies to jobs inside the company using their current email address. A recruiter in the company uses the system to contact the user regarding a position they applied for. Because the sensitivity level of the message is set to Private, the administrator will not be able to see the message the company recruiter sent to the user through the system. In Microsoft Outlook the sensitivity level set for Taleo messages is indicated to the user in the Info bar. For example, "Please treat this as Private."

Configuration

A global setting controls the sensitivity level of messages sent by Oracle Talent Acquisition Cloud (OTAC) products. This setting provides the sensitivity levels supported by Microsoft Outlook (Confidential, Normal, Personal, Private).

Setting	Description	Default Value	Location
Mail Sensitivity	Sensitivity of email messages sent from the system. Possible values are: Confidential Normal Personal Private	Normal	Configuration > [General Configuration] Settings

Setting

Description

Default Value

Location

Mail Sensitivity

Sensitivity of email messages sent from the system.

Possible values are:

Confidential
Normal
Personal
Private

Normal

Configuration > [General Configuration] Settings

System administrators can override the Mail Sensitivity global setting by configuring the sensitivity level of specific email messages. This is done via the message template editor, by using the "Sensitivity" drop-down menu. Five sensitivity levels are available:

Default
Personal
Confidential
Normal
Private

Selecting the "Default" sensitivity level means that email messages sent using this message template will use the sensitivity level defined in the "Mail Sensitivity" global setting.

Message Center

Secure Message Delivery

Customers who wish to have increased control over the information sent to Career Section users via email may choose to enable the Secure Message Delivery feature. When enabled, all messages are delivered to a secure Message Center accessible from any of the customer's Career Sections. Message recipients are directed to the Message Center to retrieve their messages.

The Secure Message Delivery feature applies only to messages sent to Career Section users, that is candidates, agents, and referrers. It does not impact Recruiting Center users or messages sent with other Oracle Talent Acquisition Cloud (OTAC) products.

If a message is sent via email (whether it is an automated message or the sender selected to send it via email), rather than receiving the actual message via email the message recipient receives a notification of message delivery containing a deeplink. To receive a notification of message delivery, message recipients must have a valid email address on file and the notification template message must be active.

Note: All messages sent to a single email address will be accessible from any Secure Message Center that is linked to that email. This may cause candidates to see one another's message content, just as though they were receiving messages via a shared inbox. If this is not desired, then the Email Uniqueness setting should be changed (Configuration > [Recruiting] Settings).

To access the Message Center, the message recipient clicks on the deep link in the message and must then authenticate himself/herself by entering a user name and password. If the user does not yet have an account, he must create one prior to be able to access his messages. Alternatively, the Message Center can be directly accessed via any active Career Section by clicking the My Messages tab.

Once in the Message Center, the message recipient can read his messages, delete them, and download the files attached to the messages in order to view them. Before accessing an attachment, the recipient must accept a download agreement. Messages are displayed in a print friendly format should Career Section users wish to print a message using the browser's print functionality.

When viewing a specific message, the recipient can navigate from one message to the next without returning to the list view by using the Previous or Next links. The message may also be deleted.Clicking Back returns the user to the message list.

For Career Section users who do not have an email address, the message sender can still send them messages and these users can access their messages from within the Message Center. For example, a candidate exists in the system and did not supply an email address. A recruiter will still be able to send an email message to the candidate using the Recruiting Center correspondence feature.

The Message Center

The Message Center has the same look and feel as the Career Section; it adopts the theme and branding of the Career Section. Messages inside the Message Center retain the formatting attributes of the message template.

The Message Center language matches the language from where the Message Center was originally accessed. If the user is coming from a Career Section, the Message Center is presented in the same language as the Career Section. If coming from the deeplink contained in the notification, the Message Center is presented in the same language as the notification sent to the user. Messages inside the Message Center are in the language used to transmit the message.

Help text is displayed in the right-hand side of the Message Center. Default universal help text, which can be edited via TexTool, is provided by Oracle. If desired, the text can be customized by a Career Section administrator using the Career Portal Page user-defined labels feature. This text change only affects the Message Center on that particular Career Section.

The Message Center stores messages sent within the past 6 months to a maximum of 100 messages. If more than 100 messages have been delivered, only the most recent 100 messages are accessible.

Messages that do not have a subject cannot be opened from the Message Center.

Note: When the Message Center is enabled, the "To", "Cc", and "Bcc" fields in the message header are not available when sending correspondence; therefore, Recruiting Center users cannot edit the message recipients. Also, Recruiting Center users cannot add additional recipients while manually sending a correspondence.

Note: When Recruiting Center users are resending messages from the candidate file History tab, the system will replicate the method of delivery used for the original message.If a message was sent prior to enabling the Message Center, when the user chooses to resend such a message, the system will not deliver the resent message to the Message Center, it will send the message to the original email address.

Configuring the Secure Message Delivery Feature

The configuration of the secure message delivery feature consists of enabling a setting and configuring message templates.

System administrators may choose to disable the "Email me a copy" link displayed on the Summary page of individual Career Sections. This can be done at any time while the Career Section is not active. If this option is not disabled before the Message Center is enabled, then the full email version of the candidate submission may be delivered via email, it is not sent to the Message Center.

Career Section Property	Default Value	Location
Display the "Email me a copy" link in the Summary page	No	Configuration > [Career Section] Administration > Career Sections > Properties

The Secure Message Delivery Enabled setting allows customers to choose if they want to send messages to Career Section users via email or via the secure Message Center.

When set to Yes, the Message Center is enabled and messages to Career Section users are delivered via the Message Center. Career Section users receive a notification of delivery and need to access the Message Center to view the content of their messages.
When set to No, there are no changes in the way the system sends messages. Career Section users will receive messages by email.

Setting	Description	Default Value	Location
Secure Message Delivery Enabled	Indicates whether the secure message delivery feature is activated in the system.	No	Configuration > [Recruiting] Settings

Three message templates are available. They are used to inform Career Section users that they have received a message and that they can view it by clicking a deeplink giving access to the Message Center. A unique message exists by recipient audience. These message templates are active by default. They can be configured just like any other message templates. System administrators can customize the message body and include tokens. Note that the following tokens containing the OR logic will resolve as follows:

{Candidate.EmailOrOperatorEmail}: message sent to the candidate's Message Center, never to the operator.
{Agent.EmailOrBlank}: looks for an agent email. However, if blank it means that there is no agent. In this case, there is no Message Center to send it to and the email address will resolve to be blank.

Message Template	Location
Message Center Delivery Notification, Agent	Configuration > [Recruiting] Message Templates
Message Center Delivery Notification, Candidate	Configuration > [Recruiting] Message Templates
Message Center Delivery Notification, Referrer	Configuration > [Recruiting] Message Templates

The following messages are delivered directly to the candidate via email regardless of the Message Center being enabled or not:

Forgot User Name
Forgot Password
Candidate Account Locked
Job Specific Referral - New Candidate
Job-Specific Capture Resume Acknowledgment - New Candidate
Unsolicited Capture Resume Acknowledgment
Unsolicited Referral - New Candidate
Resume Parsing Service Unavailable - Candidate
Unsolicited Email Application Acknowledgment - Candidate
Standard notification for a self-registration
All messages sent to Recruiting Center user accounts
All Legacy Onboarding messages

Appendix - List of Variables

List of Variables

For the most current list of variables, you can go to the Paragraphs feature in the Recruiting Administration menu.

Variable Type	Variable
Agency	{Agency.Name}
Agent	{Agent.Email}
Agent	{Agent.EmailOrBlank}
Agent	{Agent.Fax}
Agent	{Agent.FirstName}
Agent	{Agent.FullName}
Agent	{Agent.HomePhone}
Agent	{Agent.LastName}
Agent	{Agent.MobilePhone}
Agent	{Agent.PagerPhone}
Agent	{Agent.WorkPhone}
Application	Application.CandidateFullName}
Application	{Application.CompletedOrCreationDate}
Application	{Application.Date}
Application	{Application.EsignDateSigned}
Application	{Application.RequisitionInfo}
Application	{Application.Status}
Application	{Application.Certifications[1].DateReceived}
Application	{Application.Certifications[1].ExpirationDate}
Application	{Application.Certifications[1].Location}
Application	{Application.Certifications[1].Name}
Application	{Application.Certifications[1].NumberId}
Application	{Application.Certifications[1].Organization}
Application	{Application.Certifications[10].DateReceived}
Application	{Application.Certifications[10].ExpirationDate}
Application	{Application.Certifications[10].Location}
Application	{Application.Certifications[10].Name}
Application	{Application.Certifications[10].NumberId}
Application	{Application.Certifications[10].Organization}
Application	{Application.Certifications[2].DateReceived}
Application	{Application.Certifications[2].ExpirationDate}
Application	{Application.Certifications[2].Location}
Application	{Application.Certifications[2].Name}
Application	{Application.Certifications[2].NumberId}
Application	{Application.Certifications[2].Organization}
Application	{Application.Certifications[3].DateReceived}
Application	{Application.Certifications[3].ExpirationDate}
Application	{Application.Certifications[3].Location}
Application	{Application.Certifications[3].Name}
Application	{Application.Certifications[3].NumberId}
Application	{Application.Certifications[3].Organization}
Application	{Application.Certifications[4].DateReceived}
Application	{Application.Certifications[4].ExpirationDate}
Application	{Application.Certifications[4].Location}
Application	{Application.Certifications[4].Name}
Application	{Application.Certifications[4].NumberId}
Application	{Application.Certifications[4].Organization}
Application	{Application.Certifications[5].DateReceived}
Application	{Application.Certifications[5].ExpirationDate}
Application	{Application.Certifications[5].Location}
Application	{Application.Certifications[5].Name}
Application	{Application.Certifications[5].NumberId}
Application	{Application.Certifications[5].Organization}
Application	{Application.Certifications[6].DateReceived}
Application	{Application.Certifications[6].ExpirationDate}
Application	{Application.Certifications[6].Location}
Application	{Application.certifications[6].Name}
Application	{Application.Certifications[6].NumberId}
Application	{Application.Certifications[6].Organization}
Application	{Application.Certifications[7].DateReceived}
Application	{Application.Certifications[7].ExpirationDate}
Application	{Application.Certifications[7].Location}
Application	{Application.Certifications[7].Name}
Application	{Application.Certifications[7].NumberId}
Application	{Application.Certifications[7].Organization}
Application	{Application.Certifications[8].DateReceived}
Application	{Application.Certifications[8].ExpirationDate}
Application	{Application.Certifications[8].Location}
Application	{Application.Certifications[8].Name}
Application	{Application.Certifications[8].NumberId}
Application	{Application.Certifications[8].Organization}
Application	{Application.Certifications[9].DateReceived}
Application	{Application.Certifications[9].ExpirationDate}
Application	{Application.Certifications[9].Location}
Application	{Application.Certifications[9].Name}
Application	{Application.Certifications[9].NumberId}
Application	{Application.Certifications[9].Organization}
Application	{Application.DisqualificationQuestions[1].Question}
Application	{Application.DisqualificationQuestions[1].Result}
Application	{Application.DisqualificationQuestions[10].Question}
Application	{Application.DisqualificationQuestions[10].Result}
Application	{Application.DisqualificationQuestions[2].Question}
Application	{Application.DisqualificationQuestions[2].Result}
Application	{Application.DisqualificationQuestions[3].Question}
Application	{Application.DisqualificationQuestions[3].Result}
Application	{Application.DisqualificationQuestions[4].Question}
Application	{Application.DisqualificationQuestions[4].Result}
Application	{Application.DisqualificationQuestions[5].Question}
Application	{Application.DisqualificationQuestions[5].Result}
Application	{Application.DisqualificationQuestions[6].Question}
Application	{Application.DisqualificationQuestions[6].Result}
Application	{Application.DisqualificationQuestions[7].Question}
Application	{Application.DisqualificationQuestions[7].Result}
Application	{Application.DisqualificationQuestions[8].Question}
Application	{Application.DisqualificationQuestions[8].Result}
Application	{Application.DisqualificationQuestions[9].Question}
Application	{Application.DisqualificationQuestions[9].Result}
Application	{Application.Experiences[1].BeginDate}
Application	{Application.Experiences[1].CurrentEmployer}
Application	{Application.Experiences[1].Employer}
Application	{Application.Experiences[1].EndDate}
Application	{Application.Experiences[1].JobFunction}
Application	{Application.Experiences[1].NameWhileEmployed}
Application	{Application.Experiences[1].PermissionToContact}
Application	{Application.Experiences[1].Responsibility}
Application	{Application.Experiences[1].Supervisor}
Application	{Application.Experiences[1].SupervisorEmail}
Application	{Application.Experiences[1].SupervisorPhone}
Application	{Application.Experiences[1].SupervisorTitle}
Application	{Application.Experiences[10].BeginDate}
Application	{Application.Experiences[10].CurrentEmployer}
Application	{Application.Experiences[10].Employer}
Application	{Application.Experiences[10].EndDate}
Application	{Application.Experiences[10].JobFunction}
Application	{Application.Experiences[10].NameWhileEmployed}
Application	{Application.Experiences[10].PermissionToContact}
Application	{Application.Experiences[10].Responsibility}
Application	{Application.Experiences[10].Supervisor}
Application	{Application.Experiences[10].SupervisorEmail}
Application	{Application.Experiences[10].SupervisorPhone}
Application	{Application.Experiences[10].SupervisorTitle}
Application	{Application.Experiences[2].BeginDate}
Application	{Application.Experiences[2].CurrentEmployer}
Application	{Application.Experiences[2].Employer}
Application	{Application.Experiences[2].EndDate}
Application	{Application.Experiences[2].JobFunction}
Application	{Application.Experiences[2].NameWhileEmployed}
Application	{Application.Experiences[2].PermissionToContact}
Application	{Application.Experiences[2].Responsibility}
Application	{Application.Experiences[2].Supervisor}
Application	{Application.Experiences[2].SupervisorEmail}
Application	{Application.Experiences[2].SupervisorPhone}
Application	{Application.Experiences[2].SupervisorTitle}
Application	{Application.Experiences[3].BeginDate}
Application	{Application.Experiences[3].CurrentEmployer}
Application	{Application.Experiences[3].Employer}
Application	{Application.Experiences[3].EndDate}
Application	{Application.Experiences[3].JobFunction}
Application	{Application.Experiences[3].NameWhileEmployed}
Application	{Application.Experiences[3].PermissionToContact}
Application	{Application.Experiences[3].Responsibility}
Application	{Application.Experiences[3].Supervisor}
Application	{Application.Experiences[3].SupervisorEmail}
Application	{Application.Experiences[3].SupervisorPhone}
Application	{Application.Experiences[3].SupervisorTitle}
Application	{Application.Experiences[4].BeginDate}
Application	{Application.Experiences[4].CurrentEmployer}
Application	{Application.Experiences[4].Employer}
Application	{Application.Experiences[4].EndDate}
Application	{Application.Experiences[4].JobFunction}
Application	{Application.Experiences[4].NameWhileEmployed}
Application	{Application.Experiences[4].PermissionToContact}
Application	{Application.Experiences[4].Responsibility}
Application	{Application.Experiences[4].Supervisor}
Application	{Application.Experiences[4].SupervisorEmail}
Application	{Application.Experiences[4].SupervisorPhone}
Application	{Application.Experiences[4].SupervisorTitle}
Application	{Application.Experiences[5].BeginDate}
Application	{Application.Experiences[5].CurrentEmployer}
Application	{Application.Experiences[5].Employer}
Application	{Application.Experiences[5].EndDate}
Application	{Application.Experiences[5].JobFunction}
Application	{Application.Experiences[5].NameWhileEmployed}
Application	{Application.Experiences[5].PermissionToContact}
Application	{Application.Experiences[5].Responsibility}
Application	{Application.Experiences[5].Supervisor}
Application	{Application.Experiences[5].SupervisorEmail}
Application	{Application.Experiences[5].SupervisorPhone}
Application	{Application.Experiences[5].SupervisorTitle}
Application	{Application.Experiences[6].BeginDate}
Application	{Application.Experiences[6].CurrentEmployer}
Application	{Application.Experiences[6].Employer}
Application	{Application.Experiences[6].EndDate}
Application	{Application.Experiences[6].JobFunction}
Application	{Application.Experiences[6].NameWhileEmployed}
Application	{Application.Experiences[6].PermissionToContact}
Application	{Application.Experiences[6].Responsibility}
Application	{Application.Experiences[6].Supervisor}
Application	{Application.Experiences[6].SupervisorEmail}
Application	{Application.Experiences[6].SupervisorPhone}
Application	{Application.Experiences[6].SupervisorTitle}
Application	{Application.Experiences[7].BeginDate}
Application	{Application.Experiences[7].CurrentEmployer}
Application	{Application.Experiences[7].Employer}
Application	{Application.Experiences[7].EndDate}
Application	{Application.Experiences[7].JobFunction}
Application	{Application.Experiences[7].NameWhileEmployed}
Application	{Application.Experiences[7].PermissionToContact}
Application	{Application.Experiences[7].Responsibility}
Application	{Application.Experiences[7].Supervisor}
Application	{Application.Experiences[7].SupervisorEmail}
Application	{Application.Experiences[7].SupervisorPhone}
Application	{Application.Experiences[7].SupervisorTitle}
Application	{Application.Experiences[8].BeginDate}
Application	{Application.Experiences[8].CurrentEmployer}
Application	{Application.Experiences[8].Employer}
Application	{Application.Experiences[8].EndDate}
Application	{Application.Experiences[8].JobFunction}
Application	{Application.Experiences[8].NameWhileEmployed}
Application	{Application.Experiences[8].PermissionToContact}
Application	{Application.Experiences[8].Responsibility}
Application	{Application.Experiences[8].Supervisor}
Application	{Application.Experiences[8].SupervisorEmail}
Application	{Application.Experiences[8].SupervisorPhone}
Application	{Application.Experiences[8].SupervisorTitle}
Application	{Application.Experiences[9].BeginDate}
Application	{Application.Experiences[9].CurrentEmployer}
Application	{Application.Experiences[9].Employer}
Application	{Application.Experiences[9].EndDate}
Application	{Application.Experiences[9].JobFunction}
Application	{Application.Experiences[9].NameWhileEmployed}
Application	{Application.Experiences[9].PermissionToContact}
Application	{Application.Experiences[9].Responsibility}
Application	{Application.Experiences[9].Supervisor}
Application	{Application.Experiences[9].SupervisorEmail}
Application	{Application.Experiences[9].SupervisorPhone}
Application	{Application.Experiences[9].SupervisorTitle}
Application	{Application.Experiences[1].UDF_XXXX
Application	{Application.Questions[1].Question}
Application	{Application.Questions[1].QuestionResult}
Application	{Application.Questions[10].Question}
Application	{Application.Questions[10].QuestionResult}
Application	{Application.Questions[2].Question}
Application	{Application.Questions[2].QuestionResult}
Application	{Application.Questions[3].Question}
Application	{Application.Questions[3].QuestionResult}
Application	{Application.Questions[4].Question}
Application	{Application.Questions[4].QuestionResult}
Application	{Application.Questions[5].Question}
Application	{Application.Questions[5].QuestionResult}
Application	{Application.Questions[6].Question}
Application	{Application.Questions[6].QuestionResult}
Application	{Application.Questions[7].Question}
Application	{Application.Questions[7].QuestionResult}
Application	{Application.Questions[8].Question}
Application	{Application.Questions[8].QuestionResult}
Application	{Application.Questions[9].Question}
Application	{Application.Questions[9].QuestionResult}
Application	{Application.References[1].Company}
Application	{Application.References[1].Country}
Application	{Application.References[1].Email}
Application	{Application.References[1].FirstName}
Application	{Application.References[1].LastName}
Application	{Application.References[1].MiddleInitial}
Application	{Application.References[1].Phone}
Application	{Application.References[1].ReferenceType}
Application	{Application.References[1].Relationship}
Application	{Application.References[1].RelationshipLength}
Application	{Application.References[1].Title}
Application	{Application.References[10].Company}
Application	{Application.References[10].Country}
Application	{Application.References[10].Email}
Application	{Application.References[10].FirstName}
Application	{Application.References[10].LastName}
Application	{Application.References[10].MiddleInitial}
Application	{Application.References[10].Phone}
Application	{Application.References[10].ReferenceType}
Application	{Application.References[10].Relationship}
Application	{Application.References[10].RelationshipLength}
Application	{Application.References[10].Title}
Application	{Application.References[2].Company}
Application	{Application.References[2].Country}
Application	{Application.References[2].Email}
Application	{Application.References[2].FirstName}
Application	{Application.References[2].LastName}
Application	{Application.References[2].MiddleInitial}
Application	{Application.References[2].Phone}
Application	{Application.References[2].ReferenceType}
Application	{Application.References[2].Relationship}
Application	{Application.References[2].RelationshipLength}
Application	{Application.References[2].Title}
Application	{Application.References[3].Company}
Application	{Application.References[3].Country}
Application	{Application.References[3].Email}
Application	{Application.References[3].FirstName}
Application	{Application.References[3].LastName}
Application	{Application.References[3].MiddleInitial}
Application	{Application.References[3].Phone}
Application	{Application.References[3].ReferenceType}
Application	{Application.References[3].Relationship}
Application	{Application.References[3].RelationshipLength}
Application	{Application.References[3].Title}
Application	{Application.References[4].Company}
Application	{Application.References[4].Country}
Application	{Application.References[4].Email}
Application	{Application.References[4].FirstName}
Application	{Application.References[4].LastName}
Application	{Application.References[4].MiddleInitial}
Application	{Application.References[4].Phone}
Application	{Application.References[4].ReferenceType}
Application	{Application.References[4].Relationship}
Application	{Application.References[4].RelationshipLength}
Application	{Application.References[4].Title}
Application	{Application.References[5].Company}
Application	{Application.References[5].Country}
Application	{Application.References[5].Email}
Application	{Application.References[5].FirstName}
Application	{Application.References[5].LastName}
Application	{Application.References[5].MiddleInitial}
Application	{Application.References[5].Phone}
Application	{Application.References[5].ReferenceType}
Application	{Application.References[5].Relationship}
Application	{Application.References[5].RelationshipLength}
Application	{Application.References[5].Title}
Application	{Application.References[6].Company}
Application	{Application.References[6].Country}
Application	{Application.References[6].Email}
Application	{Application.References[6].FirstName}
Application	{Application.References[6].LastName}
Application	{Application.References[6].MiddleInitial}
Application	{Application.References[6].Phone}
Application	{Application.References[6].ReferenceType}
Application	{Application.References[6].Relationship}
Application	{Application.References[6].RelationshipLength}
Application	{Application.References[6].Title}
Application	{Application.References[7].Company}
Application	{Application.References[7].Country}
Application	{Application.References[7].Email}
Application	{Application.References[7].FirstName}
Application	{Application.References[7].LastName}
Application	{Application.References[7].MiddleInitial}
Application	{Application.References[7].Phone}
Application	{Application.References[7].ReferenceType}
Application	{Application.References[7].Relationship}
Application	{Application.References[7].RelationshipLength}
Application	{Application.References[7].Title}
Application	{Application.References[8].Company}
Application	{Application.References[8].Country}
Application	{Application.References[8].Email}
Application	{Application.References[8].FirstName}
Application	{Application.References[8].LastName}
Application	{Application.References[8].MiddleInitial}
Application	{Application.References[8].Phone}
Application	{Application.References[8].ReferenceType}
Application	{Application.References[8].Relationship}
Application	{Application.References[8].RelationshipLength}
Application	{Application.References[8].Title}
Application	{Application.References[9].Company}
Application	{Application.References[9].Country}
Application	{Application.References[9].Email}
Application	{Application.References[9].FirstName}
Application	{Application.References[9].LastName}
Application	{Application.References[9].MiddleInitial}
Application	{Application.References[9].Phone}
Application	{Application.References[9].ReferenceType}
Application	{Application.References[9].Relationship}
Application	{Application.References[9].RelationshipLength}
Application	{Application.References[9].Title}
Application	{Application.Skills[1].Name}
Application	{Application.Skills[1].Result}
Application	{Application.Skills[10].Name}
Application	{Application.Skills[10].Result}
Application	{Application.Skills[2].Name}
Application	{Application.Skills[2].Result}
Application	{Application.Skills[3].Name}
Application	{Application.Skills[3].Result}
Application	{Application.Skills[4].Name}
Application	{Application.Skills[4].Result}
Application	{Application.Skills[5].Name}
Application	{Application.Skills[5].Result}
Application	{Application.Skills[6].Name}
Application	{Application.Skills[6].Result}
Application	{Application.Skills[7].Name}
Application	{Application.Skills[7].Result}
Application	{Application.Skills[8].Name}
Application	{Application.Skills[8].Result}
Application	{Application.Skills[9].Name}
Application	{Application.Skills[9].Result}
Application	{Application.Status}
Application	{Application.Studies[1].Gpa}
Application	{Application.Studies[1].GpaRange}
Application	{Application.Studies[1].Graduated}
Application	{Application.Studies[1].GraduationDate}
Application	{Application.Studies[1].GraduationDateProjected}
Application	{Application.Studies[1].InstitutionCity}
Application	{Application.Studies[1].InstitutionLocation}
Application	{Application.Studies[1].InstitutionName}
Application	{Application.Studies[1].NameAttending}
Application	{Application.Studies[1].ProgramName}
Application	{Application.Studies[1].StartDate}
Application	{Application.Studies[1].StudyLevel}
Application	{Application.Studies[10].Gpa}
Application	{Application.Studies[10].GpaRange}
Application	{Application.Studies[10].Graduated}
Application	{Application.Studies[10].GraduationDate}
Application	{Application.Studies[10].GraduationDateProjected}
Application	{Application.Studies[10].InstitutionCity}
Application	{Application.Studies[10].InstitutionLocation}
Application	{Application.Studies[10].InstitutionName}
Application	{Application.Studies[10].NameAttending}
Application	{Application.Studies[10].ProgramName}
Application	{Application.Studies[10].StartDate}
Application	{Application.Studies[10].StudyLevel}
Application	{Application.Studies[2].Gpa}
Application	{Application.Studies[2].GpaRange}
Application	{Application.Studies[2].Graduated}
Application	{Application.Studies[2].GraduationDate}
Application	{Application.Studies[2].GraduationDateProjected}
Application	{Application.Studies[2].InstitutionCity}
Application	{Application.Studies[2].InstitutionLocation}
Application	{Application.Studies[2].InstitutionName}
Application	{Application.Studies[2].NameAttending}
Application	{Application.Studies[2].ProgramName}
Application	{Application.Studies[2].StartDate}
Application	{Application.Studies[2].StudyLevel}
Application	{Application.Studies[3].Gpa}
Application	{Application.Studies[3].GpaRange}
Application	{Application.Studies[3].Graduated}
Application	{Application.Studies[3].GraduationDate}
Application	{Application.Studies[3].GraduationDateProjected}
Application	{Application.Studies[3].InstitutionCity}
Application	{Application.Studies[3].InstitutionLocation}
Application	{Application.Studies[3].InstitutionName}
Application	{Application.Studies[3].NameAttending}
Application	{Application.Studies[3].ProgramName}
Application	{Application.Studies[3].StartDate}
Application	{Application.Studies[3].StudyLevel}
Application	{Application.Studies[4].Gpa}
Application	{Application.Studies[4].GpaRange}
Application	{Application.Studies[4].Graduated}
Application	{Application.Studies[4].GraduationDate}
Application	{Application.Studies[4].GraduationDateProjected}
Application	{Application.Studies[4].InstitutionCity}
Application	{Application.Studies[4].InstitutionLocation}
Application	{Application.Studies[4].InstitutionName}
Application	{Application.Studies[4].NameAttending}
Application	{Application.Studies[4].ProgramName}
Application	{Application.Studies[4].StartDate}
Application	{Application.Studies[4].StudyLevel}
Application	{Application.Studies[5].Gpa}
Application	{Application.Studies[5].GpaRange}
Application	{Application.Studies[5].Graduated}
Application	{Application.Studies[5].GraduationDate}
Application	{Application.Studies[5].GraduationDateProjected}
Application	{Application.Studies[5].InstitutionCity}
Application	{Application.Studies[5].InstitutionLocation}
Application	{Application.Studies[5].InstitutionName}
Application	{Application.Studies[5].NameAttending}
Application	{Application.Studies[5].ProgramName}
Application	{Application.Studies[5].StartDate}
Application	{Application.Studies[5].StudyLevel}
Application	{Application.Studies[6].Gpa}
Application	{Application.Studies[6].GpaRange}
Application	{Application.Studies[6].Graduated}
Application	{Application.Studies[6].GraduationDate}
Application	{Application.Studies[6].GraduationDateProjected}
Application	{Application.Studies[6].InstitutionCity}
Application	{Application.Studies[6].InstitutionLocation}
Application	{Application.Studies[6].InstitutionName}
Application	{Application.Studies[6].NameAttending}
Application	{Application.Studies[6].ProgramName}
Application	{Application.Studies[6].StartDate}
Application	{Application.Studies[6].StudyLevel}
Application	{Application.Studies[7].Gpa}
Application	{Application.Studies[7].GpaRange}
Application	{Application.Studies[7].Graduated}
Application	{Application.Studies[7].GraduationDate}
Application	{Application.Studies[7].GraduationDateProjected}
Application	{Application.Studies[7].InstitutionCity}
Application	{Application.Studies[7].InstitutionLocation}
Application	{Application.Studies[7].InstitutionName}
Application	{Application.Studies[7].NameAttending}
Application	{Application.Studies[7].ProgramName}
Application	{Application.Studies[7].StartDate}
Application	{Application.Studies[7].StudyLevel}
Application	{Application.Studies[8].Gpa}
Application	{Application.Studies[8].GpaRange}
Application	{Application.Studies[8].Graduated}
Application	{Application.Studies[8].GraduationDate}
Application	{Application.Studies[8].GraduationDateProjected}
Application	{Application.Studies[8].InstitutionCity}
Application	{Application.Studies[8].InstitutionLocation}
Application	{Application.Studies[8].InstitutionName}
Application	{Application.Studies[8].NameAttending}
Application	{Application.Studies[8].ProgramName}
Application	{Application.Studies[8].StartDate}
Application	{Application.Studies[8].StudyLevel}
Application	{Application.Studies[9].Gpa}
Application	{Application.Studies[9].GpaRange}
Application	{Application.Studies[9].Graduated}
Application	{Application.Studies[9].GraduationDate}
Application	{Application.Studies[9].GraduationDateProjected}
Application	{Application.Studies[9].InstitutionCity}
Application	{Application.Studies[9].InstitutionLocation}
Application	{Application.Studies[9].InstitutionName}
Application	{Application.Studies[9].NameAttending}
Application	{Application.Studies[9].ProgramName}
Application	{Application.Studies[9].StartDate}
Application	{Application.Studies[9].StudyLevel}
Application	{Application.Studies[1].UDF_XXXX
Application	{Candidate.ShiftGrid}
Application	{Other.RequestMoreInfoData}
Approver	{Approvers.Names}
Approval	{Approval.ApprovalDate}
Approval	{ApprovalObject.Name}
Approval	{Approval.Status}
Candidate Profile	{Candidate.Address}
Candidate Profile	{Candidate.Address2}
Candidate Profile	{Candidate.Availability}
Candidate Profile	{Candidate.BirthDate}
Candidate Profile	{Candidate.CandidateSubmissionUrl}
Candidate Profile	{Candidate.City}
Candidate Profile	{Candidate.Country}
Candidate Profile	{Candidate.Email}
Candidate Profile	{Candidate.EmailOrOperatorEmail}
Candidate Profile	{Candidate.EmployeeNumber}
Candidate Profile	{Candidate.ExpectedHourlyPayRate}
Candidate Profile	{Candidate.Fax}
Candidate Profile	{Candidate.FirstName}
Candidate Profile	{Candidate.FirstNameOrCandidateEmail}
Candidate Profile	{Candidate.FullName}
Candidate Profile	{Candidate.FullNameOrCandidateEmail}
Candidate Profile	{Candidate.HireStartDate}
Candidate Profile	{Candidate.HomePhone}
Candidate Profile	{Candidate.IdentificationNumber}
Candidate Profile	{Candidate.LastName}
Candidate Profile	{Candidate.LastNameOrCandidateEmail}
Candidate Profile	{Candidate.MiddleName}
Candidate Profile	{Candidate.MobilePhone}
Candidate Profile	{Candidate.PagerPhone}
Candidate Profile	{Candidate.Prefix}
Candidate Profile	{Candidate.PrimaryNumber}
Candidate Profile	{Candidate.Region}
Candidate Profile	{Candidate.SecurityCode}
Candidate Profile	{Candidate.ShiftGrid}
Candidate Profile	{Candidate.SocialSecurityNumber}
Candidate Profile	{Candidate.State}
Candidate Profile	{Candidate.Suffix}
Candidate Profile	{Candidate.Travel}
Candidate Profile	{Candidate.Username}
Candidate Profile	{Candidate.WeeklyHoursPreferred}
Candidate Profile	{Candidate.WeeklyHoursWilling}
Candidate Profile	{Candidate.WillWorkHolidays}
Candidate Profile	{Candidate.WillWorkWeekends}
Candidate Profile	{Candidate.WorkPhone}
Candidate Profile	{Candidate.Zipcode}
Candidate Profile	{Candidate.UDF_XXX}
Career Section	{CareerSection.AgentJobDescriptionUrl}
Career Section	{CareerSection.AgentJobListUrl}
Career Section	{CareerSection.AgentReferralUrl}
Career Section	{CareerSection.CareerSectionUrl}
Career Section	{CareerSection.ChangePasswordUrl}
Career Section	{CareerSection.ExternalServiceQuestionnaireUrl}
Career Section	{CareerSection.JobDescriptionUrl}
Career Section	{CareerSection.JobIsiUrl}
Career Section	{CareerSection.JobRmiUrl}
Career Section	{CareerSection.JobUrl}
Career Section	{CareerSection.MyAccountAccess}
Career Section	{CareerSection.MySavedSearchesUrl}
Career Section	{CareerSection.OfferViewURL}
Career Section	{CareerSection.ProfilerUrl}
Career Section	{CareerSection.SecureMessageListURL}
Career Section	{CareerSection.UnsubscribeNowUrl}
Career Section	{CareerSection.UserForgotPwdUrl}
Career Section	{CareerSection.UserWebtopSuiteUrl}
Company	{Other.CompanyLogos0}
Company	{Other.CompanyLogos1}
Company	{Other.CompanyLogos2}
Company	{Other.CompanyLogos3}
Company	{Other.CompanyLogos4}
Company	{Other.CompanyLogos5}
Company	{Other.CompanyLogos6}
Company	{Other.CompanyLogos7}
Company	{Other.CompanyLogos8}
Company	{Other.CompanyLogos9}
Company	{Other.CompanyLogos10}
Company	{Other.CompanyLogos11}
Company	{Other.CompanyLogos12}
Company	{Other.CompanyLogos13}
Company	{Other.CompanyLogos14}
Company	{Other.CompanyLogos15}
Company	{Other.CompanyLogos16}
Company	{Other.CompanyLogos17}
Company	{Other.CompanyLogos18}
Company	{Other.CompanyLogos19}
Company	{Other.CompanyLogos20}
Company	{Other.CompanyLogos21}
Company	{Other.CompanyLogos22}
Company	{Other.CompanyLogos23}
Company	{Other.CompanyLogos24}
Company	{Other.CompanyLogos25}
Company	{Other.CompanyLogos26}
Company	{Other.CompanyLogos27}
Company	{Other.CompanyLogos28}
Company	{Other.CompanyLogos29}
Company	{Other.CompanyLogos30}
Company	{Other.CompanyName}
Company	{Other.CompanyStaticPage}
Company	{Other.FullCompanyName}
Department	{Department.UDF_XXXXX}
Document Shared	{DocumentShared.ShareSender}
Document Shared	{DocumentShared.SharedPDFLink}
Document Shared	{DocumentShared.SharedPDFLinkExpirationDate}
Electronic Signature	{ElectronicSignature.DateSigned}
Electronic Signature	{ElectronicSignature.DocumentIdentifier}
Electronic Signature	{ElectronicSignature.IpAddress}
Enterprise	{Enterprise.SelfAssignedTaskListURL}
Meeting	{Meeting.Attendees}
Meeting	{Meeting.Comments}
Meeting	{Meeting.DateAndTime}
Meeting	{Meeting.Location}
Meeting	{Meeting.Organizer}
Meeting	{Meeting.SharedInformationAccess}
Meeting	{Meeting.Subject}
Offer	{Offer.ActualStartDate}
Offer	{Offer.ActualStartTime}
Offer	{Offer.AfterApprovalSuccess}
Offer	{Offer.AnnualBonus}
Offer	{Offer.ApprovalComments}
Offer	{Offer.ApprovalPathTable}
Offer	{Offer.ApprovalRequestedBy}
Offer	{Offer.CarAllowance}
Offer	{Offer.CommissionAmount}
Offer	{Offer.CommissionType}
Offer	{Offer.CreationDate}
Offer	{Offer.EshareURL}
Offer	{Offer.ExpenseAccount}
Offer	{Offer.ExpiryDate}
Offer	{Offer.ExpiryTime}
Offer	{Offer.ExtendDate}
Offer	{Offer.LastApprover}
Offer	{Offer.MobileURL}
Offer	{Offer.Options}
Offer	{Offer.OptionsType}
Offer	{Offer.OtherBonus}
Offer	{Offer.OtherCompensation}
Offer	{Offer.Pay}
Offer	{Offer.PayBasis}
Offer	{Offer.RelocationAmount}
Offer	{Offer.RelocationType}
Offer	{Offer.Salary}
Offer	{Offer.SalaryCurrency}
Offer	{Offer.SignOnBonus}
Offer	{Offer.StatusDescription}
Offer	{Offer.StockAmount}
Offer	{Offer.StockType}
Offer	{Offer.TargetStartDate}
Offer	{Offer.Vacation}
Offer	{Offer.VacationUnit}
Other	{Other.CurrentDate}
Other	{Other.JobToFriendComments}
Other	{Other.JobToFriendDescription}
Other	{Other.JobToFriendQualifications}
Other	{Other.ListOfAgents}
Other	{Other.MaximumAttachments}
Other	{Other.MaximumAttachmentSize}
Other	{Other.OriginalMessageSentDate}
Other	{Other.OriginalMessageSubject}
Other	{Other.PageBreak}
Other	{Other.ProductName}
Other	{Other.ReferralValidityPeriod}
Other	{Other.RegularCareerSectionURL}
Other	{Other.SupportedAttachmentFormat}
Other	{Other.TimeZone}
Other	{Other.UserEmail}
Other	{Other.UserFirstName}
Other	{Other.UserFullName}
Other	{Other.UserLastName}
Other	{Other.UserMiddleName}
Other	{Other.UserPassword}
Other	{Other.UserUsername}
Owner	{Owner.CorrespondenceEmail}
Owner	{Owner.FirstName}
Owner	{Owner.FullName}
Owner	{Owner.LastName}
Passport	{PassportResult.accuratebackground:AdjudicationResult} {PassportResult.accuratebackground:DetailsUrl} {PassportResult.accuratebackground:Discrepancies} {PassportResult.accuratebackground:PercentComplete} {PassportResult.accuratebackground:ProviderReferenceId} {PassportResult.accuratebackground:ProviderStatus} {PassportResult.accuratebackground:Screenings} {PassportResult.accuratebackground:SummaryText} {PassportResult.choicepoint:AdjudicationResult} {PassportResult.choicepoint:DetailsUrl} {PassportResult.choicepoint:Discrepancies} {PassportResult.choicepoint:ProviderStatus} {PassportResult.choicepoint:Screenings} {PassportResult.choicepoint:SummaryText} {PassportResult.choicepoint_drugtesting:AdjudicationResult} {PassportResult.choicepoint_drugtesting:DetailsUrl} {PassportResult.choicepoint_drugtesting:Discrepancies} {PassportResult.choicepoint_drugtesting:ProviderStatus} {PassportResult.choicepoint_drugtesting:Screenings} {PassportResult.choicepoint_drugtesting:SummaryText} {PassportResult.cswaction:ResultField} {PassportResult.cswaction:someAction} {PassportResult.ddi:PROGRESSIONDECISION} {PassportResult.ddi:STATUS} {PassportResult.ddi:SUMMARYSCORE} {PassportResult.ddi:SUMMARYTEXT} {PassportResult.ddiassessment:BAND} {PassportResult.ddiassessment:DETAILS} {PassportResult.ddiassessment:DETAILSLINK} {PassportResult.epredixscreening:BAND} {PassportResult.epredixscreening:DETAILS} {PassportResult.epredixscreening:GROUPREPORTLINK} {PassportResult.epredixscreening:PASSED} {PassportResult.epredixscreening:PROFILE} {PassportResult.epredixscreening:SCORE} {PassportResult.epredixscreening:SUBJECTREPORTLINK} {PassportResult.epredixselection:BAND} {PassportResult.epredixselection:DETAILS} {PassportResult.epredixselection:GROUPREPORTLINK} {PassportResult.epredixselection:PASSED} {PassportResult.epredixselection:PROFILE} {PassportResult.epredixselection:SCORE} {PassportResult.epredixselection:SUBJECTREPORTLINK} {PassportResult.firstadvantage:AdjudicationResult} {PassportResult.firstadvantage:DetailsUrl} {PassportResult.firstadvantage:Discrepancies} {PassportResult.firstadvantage:ProviderStatus} {PassportResult.firstadvantage:Screenings} {PassportResult.firstadvantage:SummaryText} {PassportResult.hireright:AdjudicationResult} {PassportResult.hireright:DetailsUrl} {PassportResult.hireright:Discrepancies} {PassportResult.hireright:PercentComplete} {PassportResult.hireright:ProviderReferenceId} {PassportResult.hireright:ProviderStatus} {PassportResult.hireright:Screenings} {PassportResult.hireright:SummaryText} {PassportResult.itax:FederalCredits} {PassportResult.itax:FormsLink} {PassportResult.itax:StateCredits} {PassportResult.itax:SummaryText} {PassportResult.kroll:AdjudicationResult} {PassportResult.kroll:DetailsUrl} {PassportResult.kroll:Discrepancies} {PassportResult.kroll:ProviderReferenceId} {PassportResult.kroll:ProviderStatus} {PassportResult.kroll:Screenings} {PassportResult.kroll:SummaryText} {PassportResult.rsassessmentjobspecific:BAND} {PassportResult.rsassessmentjobspecific:DETAILS} {PassportResult.rsassessmentjobspecific:DetailsUrl} {PassportResult.rsassessmentjobspecific:EXCEPTIONAL} {PassportResult.rsassessmentjobspecific:PASSED} {PassportResult.rsassessmentjobspecific:ProviderStatus} {PassportResult.rsassessmentjobspecific:SCORE} {PassportResult.rsassessmentjobspecific:webAddress} {PassportResult.rsassessmentrmi:BAND} {PassportResult.rsassessmentrmi:DETAILS} {PassportResult.rsassessmentrmi:DetailsUrl} {PassportResult.rsassessmentrmi:EXCEPTIONAL} {PassportResult.rsassessmentrmi:PASSED} {PassportResult.rsassessmentrmi:ProviderStatus} {PassportResult.rsassessmentrmi:SCORE} {PassportResult.rsassessmentrmi:webAddress} {PassportResult.taleoschedulingcenter:Appointment} {PassportResult.taleoschedulingcenter:Appointment10} {PassportResult.taleoschedulingcenter:Appointment2} {PassportResult.taleoschedulingcenter:Appointment3} {PassportResult.taleoschedulingcenter:Appointment4} {PassportResult.taleoschedulingcenter:Appointment5} {PassportResult.taleoschedulingcenter:Appointment6} {PassportResult.taleoschedulingcenter:Appointment7} {PassportResult.taleoschedulingcenter:Appointment8} {PassportResult.taleoschedulingcenter:Appointment9} {PassportResult.taleoschedulingcenter:AppointmentStatus1} {PassportResult.taleoschedulingcenter:AppointmentStatus10} {PassportResult.taleoschedulingcenter:AppointmentStatus2} {PassportResult.taleoschedulingcenter:AppointmentStatus3} {PassportResult.taleoschedulingcenter:AppointmentStatus4} {PassportResult.taleoschedulingcenter:AppointmentStatus5} {PassportResult.taleoschedulingcenter:AppointmentStatus6} {PassportResult.taleoschedulingcenter:AppointmentStatus7} {PassportResult.taleoschedulingcenter:AppointmentStatus8} {PassportResult.taleoschedulingcenter:AppointmentStatus9} {PassportResult.taleoschedulingcenter:DetailsUrl} {PassportResult.taleoschedulingcenter:HiddenDetailsUrl} {PassportResult.taleoschedulingcenter:SchedulingError} {PassportResult.taleoschedulingcenter:SchedulingStatus} {PassportResult.taleoschedulingcenter:ShowNoShowStatus} {PassportResult.taleoschedulingcenter:Summary} {PassportResult.taleoschedulingcenter:webAddress} {PassportResult.taleoschedulingcenterproctored:Appointment} {PassportResult.taleoschedulingcenterproctored:Appointment10} {PassportResult.taleoschedulingcenterproctored:Appointment2} {PassportResult.taleoschedulingcenterproctored:Appointment3} {PassportResult.taleoschedulingcenterproctored:Appointment4} {PassportResult.taleoschedulingcenterproctored:Appointment5} {PassportResult.taleoschedulingcenterproctored:Appointment6} {PassportResult.taleoschedulingcenterproctored:Appointment7} {PassportResult.taleoschedulingcenterproctored:Appointment8} {PassportResult.taleoschedulingcenterproctored:Appointment9} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus1} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus10} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus2} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus3} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus4} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus5} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus6} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus7} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus8} {PassportResult.taleoschedulingcenterproctored:AppointmentStatus9} {PassportResult.taleoschedulingcenterproctored:DetailsUrl} {PassportResult.taleoschedulingcenterproctored:HiddenDetailsUrl} {PassportResult.taleoschedulingcenterproctored:SchedulingError} {PassportResult.taleoschedulingcenterproctored:SchedulingStatus} {PassportResult.taleoschedulingcenterproctored:ShowNoShowStatus} {PassportResult.taleoschedulingcenterproctored:Summary} {PassportResult.taleoschedulingcenterproctored:webAddress} {PassportResult.transitiontestpartner:DetailsUrl} {PassportResult.transitiontestpartner:FederalCredits} {PassportResult.transitiontestpartner:InternationalCredits} {PassportResult.transitiontestpartner:KioskLink} {PassportResult.transitiontestpartner:LastError} {PassportResult.transitiontestpartner:ProviderStatus} {PassportResult.transitiontestpartner:StateCredits} {PassportResult.transitiontestpartner:SummaryText} {PassportResult.transitiontestpartner:webAddress} {PassportResult.transitiontestpartnerevent:DetailsUrl} {PassportResult.transitiontestpartnerevent:FederalCredits} {PassportResult.transitiontestpartnerevent:InternationalCredits} {PassportResult.transitiontestpartnerevent:KioskLink} {PassportResult.transitiontestpartnerevent:LastError} {PassportResult.transitiontestpartnerevent:ProviderStatus} {PassportResult.transitiontestpartnerevent:StateCredits} {PassportResult.transitiontestpartnerevent:SummaryText} {PassportResult.transitiontestpartnerevent:webAddress} {PassportResult.verifiedperson:AdjudicationResult} {PassportResult.verifiedperson:DetailsUrl} {PassportResult.verifiedperson:Discrepancies} {PassportResult.verifiedperson:ProviderStatus} {PassportResult.verifiedperson:Screenings} {PassportResult.verifiedperson:SummaryText} {PassportResult.XXXXX}
Referrer	{Referrer.Email}
Referrer	{Referrer.FirstName}
Referrer	{Referrer.LastName}
Referrer	{Referrer.MiddleName}
Requisition	{CareerSection.JobRmiUrl}
Requisition	{Requisition.AfterApprovalSuccess}
Requisition	{Requisition.AnnualBonus}
Requisition	{Requisition.ApprovalPathTable}
Requisition	{Requisition.Approver}
Requisition	{Requisition.ApproverDecision}
Requisition	{Requisition.CarAllowance}
Requisition	{Requisition.ClosingDate}
Requisition	{Requisition.Comments}
Requisition	{Requisition.Commission}
Requisition	{Requisition.CommissionType}
Requisition	{Requisition.ContactEmailExternal}
Requisition	{Requisition.ContactEmailInternal}
Requisition	{Requisition.ContactNameExternal}
Requisition	{Requisition.ContactNameInternal}
Requisition	{Requisition.ContestNumber}
Requisition	{Requisition.DepartmentName}
Requisition	{Requisition.DepartmentNumber}
Requisition	{Requisition.EducationLevel}
Requisition	{Requisition.EmployeeReferralBonus}
Requisition	{Requisition.EmployeeStatus}
Requisition	{Requisition.EshareURL}
Requisition	{Requisition.EventDate}
Requisition	{Requisition.ExpenseAccount}
Requisition	{Requisition.HighQuartileSalary}
Requisition	{Requisition.HmgrAsstEmail}
Requisition	{Requisition.HmgrAsstEmailOrHmgrEmail}
Requisition	{Requisition.HmgrAsstName}
Requisition	{Requisition.HmgrAsstNameOrHmgrName}
Requisition	{Requisition.HmgrAsstPhone}
Requisition	{Requisition.HmgrAsstPhoneOrHmgrPhone}
Requisition	{Requisition.HmgrEmail}
Requisition	{Requisition.HmgrName}
Requisition	{Requisition.HmgrPhone}
Requisition	{Requisition.JobDescriptionExternal}
Requisition	{Requisition.JobDescriptionInternal}
Requisition	{Requisition.JobfieldStructure}
Requisition	{Requisition.JobGrade}
Requisition	{Requisition.JobLevel}
Requisition	{Requisition.JobQualificationsExternal}
Requisition	{Requisition.JobQualificationsInternal}
Requisition	{Requisition.JobSchedule}
Requisition	{Requisition.JobShift}
Requisition	{Requisition.JobTitle}
Requisition	{Requisition.JobType}
Requisition	{Requisition.LocationStructure}
Requisition	{Requisition.LowQuartileSalary}
Requisition	{Requisition.MaximumSalary}
Requisition	{Requisition.MidpointSalary}
Requisition	{Requisition.MinimumSalary}
Requisition	{Requisition.MobileURL}
Requisition	{Requisition.No}
Requisition	{Requisition.Number}
Requisition	{Requisition.OpeningDate}
Requisition	{Requisition.OrganisationStructure}
Requisition	{Requisition.OtherBonus}
Requisition	{Requisition.OtherCompensation}
Requisition	{Requisition.PostedBy}
Requisition	{Requisition.PostedJobCloseDate}
Requisition	{Requisition.PublicReferralBonus}
Requisition	{Requisition.RecruiterAsstEmail}
Requisition	{Requisition.RecruiterAsstEmailOrRecruiterEmail}
Requisition	{Requisition.RecruiterAsstName}
Requisition	{Requisition.RecruiterAsstNameOrRecruiterName}
Requisition	{Requisition.RecruiterAsstPhone}
Requisition	{Requisition.RecruiterAsstPhoneOrRecruiterPhone}
Requisition	{Requisition.RecruiterEmail}
Requisition	{Requisition.RecruiterName}
Requisition	{Requisition.RecruiterPhone}
Requisition	{Requisition.Relocation}
Requisition	{Requisition.RelocationType}
Requisition	{Requisition.RequestedBy}
Requisition	{Requisition.Shares}
Requisition	{Requisition.SharesType}
Requisition	{Requisition.SignOnBonus}
Requisition	{Requisition.StockOptions}
Requisition	{Requisition.StockOptionsType}
Requisition	{Requisition.TargetStartDate}
Requisition	{Requisition.Vacation}
Requisition	{Requisition.VacationType}
Requisition	{Requisition.UDF_XXX} (Offer UDF)
Requisition	{Requisition.UDF_XXX} (Requisition UDF)
Task	{Task.AssigneesNames}
Task	{Task.AssignmentDate}
Task	{Task.Comments}
Task	{Task.CreationDate}
Task	{Task.DueDate}
Task	{Task.Name}
Task	{Task.OwnerCorporateEmailAddress}
Task	{Task.OwnerFirstName}
Task	{Task.OwnerFullName}
Task	{Task.OwnerLastName}
Task	{Task.OwnerPersonalEmailAddress}
Task	{Task.OwnerPreferredEmailAddress}
Task	{Task.OwnerTelephone}
Task	{Task.PriorityType}
Task	{Task.Status}
Task	{Task.Type}
User	{Other.OperatorEmail}
User	{Other.OperatorName}
User	{Other.OperatorPhone}
User	{UsersWithoutAccess.Names}
Work Conditions	{WorkConditions.Currency}
Work Conditions	{WorkConditions.HoursPreferred}
Work Conditions	{WorkConditions.HoursWillingWork}
Work Conditions	{WorkConditions.PayRate}
Work Conditions	{WorkConditions.WorkHoliday}
Work Conditions	{WorkConditions.WorkWeekend}