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.

Candidate Conversion Approach

in Recruiting, Opportunity Marketplace 2 comments

Summary:

As part of the migration to Oracle Recruitment Cloud, we will be converting candidates associated with active requisitions as well as other prior applicants. I'd love to hear from others who have completed a similar requirement.

Content (required):

In current testing, I've converted select previous candidates (not associated with a current open requisition) into a defined candidate pool. This works well, except for the fact that those in the candidate pool are not included in Candidate Search. This group will be closed (no new candidates added) once the records are converted from the source. The only other approach I can think of is a dummy requisition that is never posted. I could convert the records and associate them with this req and they "should" appear in the Candidate Search.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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