> For the complete documentation index, see [llms.txt](https://docs.theconfigteam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.theconfigteam.com/prebilt-for-public-cloud/upgrading/recommended-upgrade-process.md).

# Recommended upgrade process

{% stepper %}
{% step %}

### Disable Automatic Upgrades

Before beginning any testing activities, disable automatic application updates within your Mobile Device Management (MDM) platform.

This ensures production users do not receive the new version until validation has been completed.
{% endstep %}

{% step %}

### Download the Test APK

Obtain the APK for the version you wish to evaluate.

Install the APK within your QA or test environment only from the APK page on the admin portal.

Do not deploy the release to production devices at this stage.
{% endstep %}

{% step %}

### Validate in QA

Execute testing against your key business processes, including:

* Goods receipt
* Putaway
* Picking
* Packing
* Stock movements
* Physical inventory
* Any customer-specific processes or enhancements

You should also verify:

* User authentication
* Device compatibility
* Scanner functionality
* Printing and label generation (where applicable)
* Integration with SAP Public Cloud

Document any issues identified during testing and share with your installation provider for resolution before proceeding.
{% endstep %}

{% step %}

### Production Upgrade

Once QA testing has been successfully completed and business stakeholders are satisfied with the results:

1. Approve the release for production.
2. Initiate the upgrade on the production application by pressing "upgrade" on the AppStore or Play Store.
3. Verify successful deployment.
4. Perform smoke testing of critical business processes.
   {% endstep %}

{% step %}

### Rollout via MDM

After production validation:

1. Upgrade deployment through your MDM platform.
2. Roll out the approved version to end-user devices.
3. Monitor adoption and support tickets during the initial deployment period.
4. Address any unexpected issues promptly.
   {% endstep %}
   {% endstepper %}