Prerequisites and assumptions

This section aims to document the steps required for you to upgrade your PreBilt solution from a previous version to a new version, considering any customisations made during the original project. The goal is to retain necessary customisations, review and remove unnecessary ones, and activate new functionalities introduced in the new release. Upgrading can be done at no extra cost unless consultancy services are required.

The upgrade process applies to the entire PreBilt product and includes bug fixes, new functionalities, and general enhancements. It is important to note that this process does not involve upgrading the SAP system itself, but only the software provided by The Config Team. The extent of changes can range from minor adjustments to major overhauls, depending on the nature of the new functionalities and any existing customisations. Priority is given to reviewing and activating new features, while ensuring that essential customisations are retained and any that have been superseded by new core functionality are removed.

The timeline for preparation and execution can vary significantly based on the number of customisations, the complexity of new functionalities, and the availability of data and experienced testers. It can range from a day to several weeks, depending on the experience and cohesiveness of the team.

Main stakeholders and responsibilities

• Basis Team: Responsible for transporting the new version into the system.

• Functional Teams: Responsible for regression testing and validating new functionalities.

• Development Teams: Review and adjust customisations as needed.

Tools required

• GitLab, GitHub, Atlassian Bitbucket, or any service that supports Git functionality.

Before you start...

• Check for any repairs done in the system and back them out if necessary to avoid transport failures.

• Ensure data setup and access for all involved stakeholders.

• Refresh memory on system changes to review their necessity post-upgrade.