Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Workflow transaction using date submitted as effective start date rather than date selected
Content
We have noticed that since 21B was applied, that some of our workflow transactions are using the date submitted as the effective start date for the change rather than the effective date entered on the transaction. This has occurred with Change Working Hours and Change Manager. We can delete the change on the assignment and re-enter with the correct date without any error.
I have logged a SR with Oracle, but have not heard anything. I searched on this site and couldn't find anything. We have the workflow notifications with the approvals to show that the transactions were submitted and approved with the correct date, but when it was committed to the database, the effective start date changed to the date the transaction was submitted. This has occurred for changes in the future and changes in the past. It's occurred with a date change of 1 day and a date change of 7 days.