Our business heavily relies on scheduling BI reports to ensure timely delivery and accurate data availability. A key part of this process involves managing the Schedule Job End Date. However, we've encountered a limitation when attempting to adjust the end date to an earlier time on an existing scheduled report job.
Currently, when we edit the Schedule Job End Date to an earlier date and use the "Submit" option, the change does not take effect. We understand from your guidance that this is expected behavior, and the recommended workaround is to use "Submit As New" instead. While this workaround is functional, it creates an inconsistent user experience because:
- The "Submit" option successfully applies edits for changes such as message content or frequency.
- Only the End Date adjustment requires using "Submit As New" to take effect.
From a usability and operational standpoint, it would be beneficial if the "Submit" functionality fully supported all edit scenarios, including changes to the Schedule Job End Date. This alignment would simplify the workflow, reduce potential confusion, and improve overall efficiency in managing scheduled reports.
We kindly request that Oracle consider enhancing this functionality so that editing the Schedule Job End Date can be handled seamlessly via the "Submit" button, in line with other editable fields. We believe this would greatly improve the user experience and operational flexibility for many customers.
