Environment Assignment Restrictions¶
When configuring the Template Release Pipeline, Bizmetry enforces strict rules that determine which template versions can be assigned to which environment types. These rules are based on the lifecycle state of the template version and are designed to protect higher environments from instability, enforce governance, and maintain a controlled promotion process.
Assignment Rules by Lifecycle State¶
| Lifecycle State | Assignable To |
|---|---|
| Draft | DEVELOPMENT only |
| Ready for Review | DEVELOPMENT only |
| Rejected | DEVELOPMENT only |
| Reviewed | DEVELOPMENT only |
| Published | Any environment (DEV, QA, UAT, Production, and any custom environment) |
| Retired | ❌ Cannot be assigned to any environment |
Non-Published Versions — Development Only¶
Template versions in the following states are considered non-production-ready:
- Draft
- Ready for Review
- Rejected
- Reviewed
👉 These versions can only be assigned to the DEVELOPMENT environment.
Why?¶
These versions are still:
- Under active configuration (Draft)
- Awaiting validation (Ready for Review)
- Requiring corrections (Rejected)
- Approved but not yet officially released (Reviewed)
Restricting them to DEVELOPMENT ensures that:
- Work-in-progress configurations remain isolated from higher environments
- Unvalidated changes do not impact QA, UAT, or Production
- Review and approval processes are fully respected before promotion
- Structural changes are tested safely before advancing
This creates a clear separation between experimentation and controlled deployment.
Published Versions — All Environments¶
Only versions in Published state are eligible for assignment to higher environments:
- QA
- UAT
- Production
- Any additional non-development environments configured in the release pipeline
A version must complete the full review cycle before it can be published. Once published:
- The version becomes immutable — its configuration cannot be changed
- It is considered validated and stable
- It can be safely promoted across all environments
Retired Versions — No Assignment Allowed¶
Template versions in Retired state:
👉 Cannot be assigned to any environment — including DEVELOPMENT.
A retired version is fully decommissioned. It cannot be referenced from any environment, business event, or any other area of Bizmetry that depends on an active template version. It exists exclusively as a historical record.
Governance & Risk Control¶
These assignment restrictions collectively enforce:
- Controlled, stage-gated promotion of changes through the pipeline
- Clear separation between draft work and stable, approved releases
- Reduced operational risk from premature or accidental promotion
- Strong lifecycle governance aligned with enterprise change management practices
- Compliance with structured review and approval workflows
Core governance mechanism
This assignment policy is a foundational part of Bizmetry's enterprise-grade change control model. By aligning lifecycle states with environment eligibility, Bizmetry ensures that only validated, approved, and stable template versions can reach production-level environments — and that retired versions are permanently excluded from the pipeline.