Transaction Line Details are Not Validated when Expense Report (Classic(+)) is Saved For Later (Doc
We are currently on Image 40, PeopleTools 8.58.15. Our users are asking that this be fixed. We have delegates enter expense reports on behalf of employees and use the save for later to check for any errors before having the employee go in and submit the expense report for approval.
The document notes that Oracle will now support all Classic features slated for de-support from the end of 2020 through the end of 2021.
Is this still the case? The majority of our users prefer Classic vs. Fluid. I am wondering if we need to start moving them to Fluid.
Will there be no enhancements or fixes for Classic at the end of this year? Do I assume Oracle will not fix the above issue?