Plan
Validate the path before the forge runs.
Plan checks scope, dependencies, risks, promotion path, and evidence requirements before build, seed, retrieve, deploy, or promotion work begins.
Dependencies
Relationship intelligence
Account -> Contact -> Opportunity
Satisfied
Why: Business data must keep parent records available before child records move.
Product2 -> Pricebook2 -> PricebookEntry
Recommended
Why: Revenue and CPQ flows require products, price books, and entries together.
Owner and Queue references
Needs Review
Why: Ownership changes can affect security, notifications, and validation rules.
Risks
What needs review?
Reference data freshness
Medium
Training is eight days behind Production.
Approval not complete
Medium
Summer Release approval is still pending.
Validation rules
Low
Three possible issues found during metadata review.
Promotion Path
How work will move
CPQ
Promotion path for CPQ Rollout
Developer SandboxCPQ Demo OrgUATProduction
- Approvals
- Human approval before production-like stages
- Evidence
- Metadata diff, tests, approval, rollback plan
- Tests
- Regression tests for impacted systems
- Rollback
- Rollback supported when evidence package is complete
Standard Path
Default template: Developer -> QA -> UAT -> Production
DeveloperQAUATProduction
- Approvals
- Configurable per stage
- Evidence
- Configurable per stage
- Tests
- Configurable per stage
- Rollback
- Configurable
Evidence Required
Proof package
Metadata Diff
Validation Results
Test Evidence
Approval Decision
Rollback Plan