Hi,

It should be in test environment but it's depends on how many environment or sub environment you have so basically this should be just lower environment from that one where we have found bugs and need to fix urgent.

-Arun

Hello Monique, 

In a scenario where you have four environments as described—Development, QA, Pre-Production, and Production—the hotfix should be applied to the environment that is fully synchronized with Production.

Typically, and when you have 4 enviroments, this would be the Pre-Production one, which mirrors Production. However, there are cases where QA could be used if it has reliable test data and matches the current app version in Production.

The main goal here is to test and debug in an environment that is closely aligned with Production, ensuring the hotfix is in place and working correctly before deploying it to Production without causing downtime.

Of course, once the hotfix is applied, it needs to be propagated backward to other stages, such as Development and QA (if the fix was made in Pre-Production).

Here is the documentation page concerning Hotfixes:

• https://success.outsystems.com/documentation/11/deploying_apps/apply_a_hotfix/

Best regards, 
Ana Agostinho

Dear @Monique Gomes RIBEIRO 

Hotfixes are usually applied in Production (where the issue needs to be resolved immediately) and the Test/Acceptance environment to verify that the fix works as expected before applying it to production.

Certification Test Question:

Based on your test options, here's an analysis of each choice:

• Option A: Production

This is too limited. While the hotfix must be applied in Production, you should also test it before deployment.

• Option B: Pre-production, Production

This option includes Pre-production as a staging environment, which can be used for final validation before production, but it excludes QA or Test, where you might want to test earlier.

• Option C: QA, Pre-production, Production

This option suggests applying the hotfix in QA for testing, Pre-production for staging, and Production. This aligns with best practices where a fix should pass through multiple environments before reaching production.

• Option D: All environments (Correct)

Applying the hotfix in all environments (including Development) would ensure consistency across environments and prevent future regressions. This is often the safest route, ensuring that the fix is integrated into the codebase and does not get lost in future development cycles.