Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Code showing as NULL when recruiter triggers "Send Confirmation Request" to unconfirmed applicants

Summary:

When an external candidate applies for a role, an email is received with the code to confirm identity. When recruiter triggers same email to unconfirmed applicants, code shows as NULL.

Content (please ensure you mask any confidential information):

We have just moved to direct recruiting and are receiving unconfirmed applications. Testing has found that triggering the "Send Confirmation Request" to an unconfirmed applicant results in an email with the code showing as null. The system triggered email includes the code and the recruiter triggered email shows "null" even though they use the same template. I have created a new version, removed the verificationPIN token and re-added it and published the new version however get the same result.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!