My Oracle Support Banner

{RequisitionHeader.RecruiterEmail} And {Requisition.RecruiterEmail} Values Out Of Sync For Recruiter (Doc ID 2470666.1)

Last updated on JANUARY 09, 2020

Applies to:

Oracle Taleo Recruiting Cloud Service - Version 17.8 and later
Information in this document applies to any platform.


On : 17.8 version

The correspondence variable is pulling the wrong value for the recruiter's email address.

The correspondence variables {RequisitionHeader.RecruiterEmail} and {Requisition.RecruiterEmail} are supposed to pull the recruiter's email address but they are pulling an incorrect value.

The issue can be reproduced at will with the following steps:
1. Log into Taleo
2. Click on recruiting
3. Enter the candidate id into search
4. Click on their name and then the job submission that needs to be sent a correspondence
5. Click More Actions > Send Correspondence
6. The letter template includes the variables {RequisitionHeader.RecruiterEmail} and {Requisition.RecruiterEmail}
7. These variables are pulling a test email address that was imported previously by TCC. The test email addresses were updated back to the original user email address, but the system was still pulling the test email address.

The issue has the following business impact:
Due to this issue, recruiters are not receiving an email because the correspondence variables are not pulling in their email address. It is pulling a test email address that was previously imported, but has been changed back to the original value.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.