Replace obsolete rules without losing their uses
Purpose
Administrators need a controlled path away from an obsolete rule. Retirement preserves dependent decisions while they move to a replacement.
How It Works
The administrator reviews dependencies and selects a replacement when appropriate. Deprecation discourages new uses while existing consumers keep working. A transfer report distinguishes moved uses from those needing attention. Pinned dependencies remain a deliberate choice for their owners. Referencing expressions are released again when replacement is valid. The administrator clears remaining dependencies before archive. Restoration makes an archived rule available again. Deletion is reserved for unused work that was never released. Stale lifecycle requests require another read. The product should expose individual-version withdrawal if that remains the intended retirement action.
Relationships
- Release, schedule and restore rule versions releases replacement expressions in rules that include the retired definition.