Overview

To ensure minimal disruption during the upgrade, the process should be planned during periods of low activity, with stakeholders informed in advance to maintain awareness and alignment. Progress will be closely monitored during the cutover to production to confirm a successful promotion, and feedback will be gathered on both the upgrade process and the performance of the new version.

Key risks include underestimating the effort required for regression testing, limited engagement from experienced testers, and challenges around version compatibility and managing customisations. These risks can be mitigated by involving experienced testers, ensuring proper data setup, and planning the upgrade thoroughly while maintaining clear communication with stakeholders. In the event of issues, the preferred contingency approach is to address problems during development regression testing and release patches as needed, rather than rolling back the upgrade.

Upgrade execution

1

Transport the new version

• Import the new version transports into the development system.

• Run reports to identify modified apps or classes with enhancements.

2

Review customisations

• Validate if custom code is still necessary or if it has been incorporated into the standard product.

• Remove unnecessary customisations and ensure remaining customisations are still valid.

3

Activate new functionalities

• Review and activate new functionalities by adding necessary configurations or AMD.

• Update training documents as needed.

4

Move through the landscape

• Promote changes from development to QA and then to production, following the customer's predefined windows for transport imports.

• Ensure minimal disruption by planning the upgrade during low activity periods.

Frontend installation

1

Prepare the environment

• Ensure the necessary versions of UI5 and Android are supported.

• Verify compatibility with Neptune or other frontend frameworks used.

2

Fetch and merge updates

• Fetch the latest release from the releases repository to the customers cloned repository.

• Merge the updates into the customer project, ensuring custom code and extensions are preserved.

3

Test and validate

• Perform regression testing to ensure the frontend functions correctly with the new version.

• Validate that customisations and new functionalities work as expected.