Notification & Escalation Timeout Is Based On Modified Date EOAWDTTM_MODIFIED

(Doc ID 2397803.1)

Last updated on MAY 11, 2018

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.

Goal

PT 8.55+

We have setup timeout options as follows
Timeout Option 1: Send reminder to the approver after 1 hour
Timeout Option 2: Send a second reminder to the approver after 2 hours
Timeout Option 3: Reassign the workflow to the approver’s next level manager after 3 hours if still unapproved.
Timeout Option 4: Reassign to System Administrator after 4 hours if still unapproved.
After Timeout Option 3 (Reassign to next level manager), the EOAWDTTM_MODIFIED Date Field is being updated to the system date.
After 1 hour, when NEM_MAIN runs again, the system sends a reminder to the next level approver.
Question: Why does the NEM_MAIN process refer to EOAWDTTM_MODIFIED date instead of the Creation Date??

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms