Using Versions to Avoid Enforcement Gaps in Policies and Lifecycle Models
CentraSite does not permit you to modify a policy (design/change-time or run-time) or a lifecycle model while it is active. To modify an active instance of these types of objects, you must first deactivate it. However, doing this results in a period of time during which the policy or lifecycle model will not be enforced.
To avoid a gap in enforcement, you can use the versioning feature to modify these types of objects. Instead of deactivating the existing policy or lifecycle model, you generate a new version of the object and make your changes to the new version. When you are ready to put the updated policy or lifecycle model into effect, you simply switch the new version to the “Productive” state. When you do this, CentraSite automatically deactivates the old policy or lifecycle model and activates the new one.
For more information about versioning policies and lifecycle models, see
Modifying a Design/Change-Time Policy and
Versioning or Replacing Lifecycle
Models.