Solicitation Approval Workflow Notifications Due Date Causing Reminders That Confuse Users (Doc ID 3027803.1)

Last updated on JUNE 14, 2024

Applies to:

Symptoms

The Solicitation Approval Workflow Notifications are listing a date in the Due column (Due date) that create confuse its not known where this Due Date comes from.   This Due date is sometimes set to a date in the past and ends up prompting the Workflow Notification system to cancel the original approval notification and send a new Reminder approval notification. This ends up causing up to three emails for the approver: 1) Original Approval, 2) Cancelled Original Approval, and 3) Reminder Approval.

This would be okay if the Due date of the original approval notification was in the future which would result in the user being reminded to approve the solicitation if they ignored the original notification for too long.   But setting the Due date of the original approval notification to a date in the past serves no purpose and causes the three notifications described above.

 
Steps
-------------
1. Create a Solicitation just to the point before it is published and initially approve it.
2. Create an amendment to that Solicitation and submit it for approval.
3. The approver will receive an approval notification that includes a date in the Due column that is in the past. If the approver does not immediately approve the Solicitation Amendment, the system will send out a Reminder Notification and a notification that the original approval notification was cancelled. Each of these Workflow Notifications also sends an email to the approver.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.