1. Quarterly Update Preparation Guide
  2. The First Day after Your TEST CADENCE Environment is Updated

The First Day after Your TEST CADENCE Environment is Updated

Remember, you have a two week window in which to validate an update and resolve any issues in your test cadence environment, before your production environment is updated.

Note: For testing purposes, and with each quarterly update, the customer is responsible for keeping their 3rd party hardware and software up-to-date. Please ensure you have connected physical devices (handheld scanners, printers) to your non production instance and tested WMS functionality.

It is strongly recommended to complete the following:

  • Run through your test plans in the first few hours to make sure that the environment was updated with no unexpected impact to your current business processes.
    • Integration tests confirming APIs (such as XML, REST) still work and exercise your agents and back end processes
    • Third party external systems (such as rating, distance and service time engines)
    • Key business process flows for different roles in your organization
    • Critical custom reports
    • UI tests that cover users day-to-day activity and address screens that trigger agent actions
    • Custom workflows including saved queries and direct SQL updates
    • Automatically available UI
    • New enhancements that will apply to you.
  • We strongly encourage customers to create automated tests to maximize coverage and streamline the test process.
  • If you find anything that worked before the update, but doesn’t work after it, log a Service Request so you can engage Oracle Support. Do this by the end of the first business day after the update. If you do find such an issue, make sure that when you log your Service Request, you:
    • Indicate that the issue didn’t exist before the update
    • State the date that the update will be applied to production or other environments
    • File a separate Service Request for each issue
  • Perform any post-update tasks that are recommended in the Post-Update Tasks section of the What’s New guide.
  • Remain engaged with Oracle Support as we work to validate and correct any issues that you found. Since Quarterly Updates can’t be rescheduled, we need to work together to resolve everything before your production environment update begins.