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.

Why can't the absence module handle the previous date in the notifications in case of an update?

Summary:

Why can't the absence module handle the previous date in the notifications in case of an update?

Based on the current design of the absence module, the approver will not be able to know the previous dates in case the employee updates the leave and submits the request for approval. This is a fundamental request functionality that when I'm trying to update any existing data in the notification, the approver should see and view the current data and the proposed one, and this already exists in the assignment changes, promotions, transfers, and personal information data.

Below is a screenshot of any updated leave from the employee submitted to the line manager. Can anyone tell me what was the original absence dates?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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