Canceled Timecard Notifications Displayed As Active After Timecard Timeout / Rollup
(Doc ID 2709170.1)
Last updated on SEPTEMBER 19, 2024
Applies to:
Oracle Time and Labor - Version 12.2.8 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Canceled Timecard Notifications Displayed as Active after Timecard Timeout / Rollup
Submitted timecard notifications that have timed out (e.g: after 72 hours) and rolled up to the second level approver are not being canceled when the timecard is subsequently updated and resubmitted.
These notifications are still showing in the Open notifications worklist even though another active/open notification has been sent to the first line supervisor.
When the second line supervisor attempts to open the old notification which still showing as open, they receive an Unexpected Error.
EXPECTED BEHAVIOR
-----------------------
Submitted timecard notifications that have timed out after 72 hours and rolled up to the second level approver are expected
to get canceled when the timecard is subsequently updated and resubmitted.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login as Employee > Self Service Time Responsibility > created and submitted a timecard
2. 1st level Supervisor receives the timecard approval notification
3. Submitted timecard notification that have timed out after 72 hours and rolled up to the second level approver.
4. Now the same timecard is subsequently updated and resubmitted by employee ..
5. The notifications (sent to second level approver as mentioned in step# 3) is still showing in the Open notifications worklist
even though another active/open notification has been sent to the first line supervisor.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |