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.
Best practice approach for talent review meetings for optimum system performance
Summary
Is there a recommended number of talent reviews and reviewee population that ensures optimal system performance?Content
Hi
Do you conduct a talent review for all employees within your organization? If so, have you observed any performance issues?
We are looking to conduct a talent review for all employees in our organization (circa. 70K EEs), however wanted to check if anyone has done this before and if so did you experience slow system performance - within talent review module as well as general slowness with HCM?
Can an Oracle product manager recommend best practice approach i.e.
1. Is there a limit to how many talent reviews we should be creating on mass?
Tagged:
3