You can use Deployed mode in your Application Lifecycle Management (ALM) process.

Deployed mode is used to prevent modifications from being made to the structural information in models. This ensures compatibility in ALM between the test and production models

Use Deployed mode with production and test models, not development source models. When you need to update a production model, do the following:

  • Make the structural changes in a compatible development (source) model, in Standard mode.
  • Use Compare and Synchronize to move structural changes from the development (source) model to the production (target) model (do not disable Deployed mode).

For security reasons and data integrity, we recommend that you only store production data in models that are in Deployed mode. This also avoids the duplication of data and helps to reduce the overall size of the model.

Since Deployed mode blocks any changes from being made to a model’s structural information, you’re not allowed to add revision tags to models in Deployed mode. In Deployed mode, it's still possible to create a model from a revision tag.

We recommend you always enable Deployed mode in synchronization target models.

Warning: Don't disable deployed mode in production models or sync target models. If structural changes are made after disabling Deployed mode, the model will become incompatible for synchronization with previously compatible source models. In some circumstances, you can recover a sync incompatible model by reverting to the most recent revision tag. For help, see Revision tags overview.