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.

Someone forced ineligible for a Check-In Document on a future Review Period?

in Performance Management 5 comments

Summary:

Check-In Document, Performance Document, forcing eligibility on future Review Periods that don't exist?

Content (required):

Hi All,

We have identified an anomaly in our system. For context, we use the same performance template and same check-in template year-over-year, connecting templates to the current Review Period only.

We have a process in Q3 where managers can force workers eligible/ineligible for a Check-In Document or Performance Document for that current Review Period.

In this case, during our 2022 cycle on our 2022 Review Period - we had a manager force someone ineligible for a 2023 Check-In Document. From a UI-perspective - this would be impossible. We did not open our 2023 Review Period until January 2023. The "force ineligible" action occurred in September 2022.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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