Best Practices for testing New Configuration or Upgrading EcoSys Versions - EcoSys - 9.4 - Installation & Upgrade - Hexagon

These practices represent the company's standard approach and should be applied to both on-premise and Smart Cloud hosted EcoSys environments where applicable.

Environment Structure

Maintain the following three environments:

• DEV – development & configuration sandbox

• TEST – integration, regression, and UAT

• PROD – live production environment

All environments should have access to consistent and relevant production data.

Scenario 1: Promoting App Configuration Changes

Purpose: Safely introduce and validate configuration changes (e.g., spreadsheets, action/action batches, reports, etc.).

Promotion Flow:

1. Refresh DEV with latest PROD data.

2. Modify app configuration in DEV.

3. Promote configuration changes from DEV > TEST.

4. In TEST:

   1. Perform regression testing.

   2. Conduct user acceptance testing (UAT)If all tests pass, promote configuration to PROD.

5. If all tests pass, promote configuration to PROD.

Scenario 2: Testing and Promoting New App Version / Build

Purpose: Safely test new versions or builds before production rollout.

Upgrade Flow:

1. Refresh TEST with latest PROD data.

2. Deploy new app version/build in TEST.

3. In TEST:

   1. Perform regression testing.

   2. Conduct user acceptance testing (UAT).

4. If all tests pass, deploy the same version/build to PROD.