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.

Performance Document: Bypassing the approval task still creates approval task

Summary:

We've noticed that when we use the "Move Task Forward" action on the Performance Documents Administration page, to move a document from a step pre-approval to a step after approval, an approval task is still created. I wonder if this is expected.

Content (required):

Hello! I wonder if anyone has come across this. Our Performance Document Process Flow is as follows:

1.     Self-Assessment

2.     Manager Evaluation

3.     Approval

4.     Share Performance Review

5.     Acknowledge Performance Review

When we use the ‘Move Task Forward’ action on the Performance Documents Administration page to bypass the approval task, for example: move from Manager Evaluation to Share Performance Review, or from Manager Evaluation to Acknowledge Performance Review, an approval task is still created for the approver, even though the review is past that step of the process.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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