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.

Preferred work location is not saving

edited Dec 1, 2020 11:36PM in Taleo Enterprise 3 comments

Summary

When creating a candidate, the preferred work location does not save

Content

We use User Groups based on location (country) to determine what candidates recruiters have access to.  This is primarily to comply with privacy laws.  Since moving to Fluid we have noticed that a lot of candidates are being created without the preferred work location, which is the field that is referenced in user groups.  Upon researching, we have learned that when recruiters create a candidate profile, the preferred work location is entered at the time of creation but it is not being saved.  As a result, these candidates appear in all searches, regardless of the recruiter's home country.  Oracle has created

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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