Versioning or Replacing Lifecycle Models

If you need to make changes to a lifecycle model after the model has been activated (that is, after you place it in the Productive state), you must either create a new version of the existing model or replace the existing model with a completely new model. You cannot modify a lifecycle model directly after it has been activated.

The easiest way to apply changes to a lifecycle model is to generate a new version of the model. This task involves the following basic steps:

1. Creating a new version of the model. During this step, CentraSite creates an exact copy of the existing lifecycle model.

2. Updating the new version of the lifecycle model as necessary (for example, adjusting its state permissions, inserting additional states, removing states, modifying transition paths, applying it to additional object types).

3. Activating the new version. This step automatically activates the new version and retires the old version.

When you activate a new version of a lifecycle, instances of assets that were created under the old lifecycle model will automatically switch to the new lifecycle model if they are in a state that exists in the new model. Otherwise, they will continue to follow the old lifecycle model until they are switched to a state that exists in both models. At that point, they will switch to the new lifecycle model. For more information about how CentraSite maps the states between old and new versions of a lifecycle model.

You can also apply changes to a lifecycle by defining an entirely new lifecycle model. To put the new model into effect, you must retire the existing model and then activate the new model. When you change a lifecycle this way, the objects that were created using the old model will complete their lifecycles under the old model. Objects that are created after the new model is activated will follow the new model.