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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Candidate profile address vs correspondence token
Summary:
Content (required):
So, we do not ask for a candidate address during the initial application. We really don't care where you live when you first apply. We can worry about that if we move forward. So we don't ask for it. We do ask for it in a background check application. And it will populate the candidates profile with the address they enter in the background check app.
So we had a candidate who picked the wrong state when they entered it in the background check. The recruiter updated it in the general profile but even after that any correspondence we are trying to send using the {Candidate.State} token is showing the wrong state, even though it is right in the profile. Has any one ever run into this and is there a way to fix it?
0