Pre-Promotion Checklist

Promoting to Production is irreversible in the sense that changes go live immediately once promoted. Running through this checklist before every Production promotion reduces the risk of broken modules, failed integrations, and end-user impact.

This checklist applies to promoting any resource to Production. For routine promotions between lower environments (Staging to QA, QA to UAT), apply the relevant sections at each stage. Copy this checklist to your preferred task-tracking tool before each promotion.

Warning: The platform does not enforce a promotion sequence and does not block promotions based on missing dependencies. Verifying this checklist is the only safeguard.

Dependencies

• All services the module calls are promoted to the target environment and returning expected responses.
• All styles the module uses are promoted to the target environment and set as the default if required.
• All modules the module depends on (shared modules, entrypoints, linked forms) are promoted.
• All Express roles and groups referenced by the module are promoted to the target environment.
• The Locale module is promoted separately if the application has translations.
• Global Variables referenced by the module are defined in the target environment.

Environment Configuration

• Services in the target environment use the correct credentials and endpoints for that environment — not Staging credentials.
• Global Variables in the target environment reflect the correct environment-specific values.
• SSO configuration in the target environment is active and tested (if applicable).
• Session and security settings in the target environment match organizational policy.
• File upload limits in the target environment are configured correctly.

Testing Sign-Off

• QA has verified the build in the QA environment.
• UAT has accepted the build in the UAT environment.
• Any issues found in UAT have been resolved and re-verified.
• If Pre-Production is used, validation in Pre-Production is complete.

Production Readiness

• The promoting Creator has Production promote permissions.
• The promotion has been communicated to relevant stakeholders.
• The promotion is scheduled for a low-traffic window if the application is live.
• A rollback plan is identified: the known-good version is confirmed in a lower environment and can be re-promoted if needed.

After Promotion

• Verify the promoted resource is functioning correctly in Production.
• Confirm end-users can access the application without issues.
• If the promotion involved a style change, confirm the default style is set correctly in Style Administration.
• Monitor for unexpected issues in the first hour after promotion.

Recovery Steps

If something goes wrong after promoting to Production:

1. Do not attempt to fix the issue by making additional edits in Production.
2. Identify the last known-good version in a lower environment (Staging or UAT).
3. Promote the known-good version from the lower environment back to Production.
4. Verify the restored version before end-users encounter the issue.

See Working in Production for the full recovery process.