Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 7.1.1 and later
Information in this document applies to any platform.
***Checked for relevance on 11-Jul-2013***
On 7.1.1 in Production:
Find that on various occasions when users need to move regularly scheduled workflows out to a
later date for system downtime, the process will still start when it was originally scheduled
even if the start date was moved to following week. This doesn't happen every time, but has
happened enough to prove it is a true issue and not user error. Seems to happen most when process
is rescheduled on the same day when it is scheduled to run even if the reschedule is done hours
in advance of original start time. Bouncing the server after reschedule does not resolve issue.
One example, the process was rescheduled to start two days later and the process ran three times
on the same day of the original schedule though it was only scheduled to run once. Users have
also seen workflows start on their own even if they were not scheduled in the first place
User are seeing this on the weekly schedule. They have not noticed it on the other types of
schedules, but weekly is the one they use most frequently.
They have confirmed that the front end changes made to the schedule does get reflected in the
database. After making the changes to teh scheduler the wf_scheduler table's timing column does
reflect the change. The start date and day of week changes
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms