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.

Fluid Recruiting 20B.3 Sorting Not the same a Legacy

edited Oct 7, 2020 10:16PM in Taleo Enterprise 1 comment

Summary

Weighted ACE questions are getting different sorting results from Legacy to Fluid.

Content

Anyone having issues with sorting candidates using Fluid Recruiting and getting different results sorting using Legacy?

We are using the weighting of the ACE questions and getting different sorting results from Legacy to Fluid. This is different than the posted bug information that is NOT using the weighting.  Bug 31849128 - FLUID-PRESCREENING REQUIRED/ASSET NUMBERS INCORRECT FOR CANDIDATES.
We are getting different sorting results of candidates from different Recruiters in the selection steps (new/to be reviewed and recruiter screened/to be recruiter screened). Multiple Recruiters have looked at the same candidate pools and each view is not sorting the same for all of us.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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