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.

Logic behind the Oracle AI features for Recruiting

edited Oct 29, 2024 8:57AM in Recruiting, Opportunity Marketplace 1 comment

Summary:

We need to know the logic as well as which fields are required to be enabled to get the most relevant suggestions/information for the below AI features that we have enabled:

  1. Estimated Time to Hire
  2. Suggested Candidates
  3. Similar candidates
  4. Suggested Jobs
  5. Similar Jobs

Content (please ensure you mask any confidential information):

Dear All,

We have recently enabled the below mentioned AI features in oracle recruiting.

  • Estimated Time to Hire
  • Suggested Candidates
  • Similar candidates
  • Suggested Jobs
  • Similar Jobs

Request support to kindly help with

  1. what is the logic behind the information being pulled into the above AI features?
  2. Which standard fields are REQUIRED to be enabled (if they are not available/enabled by default) to get the most relevant suggestions/information using the above AI features?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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