1. Application Lifecycle Management
  2. Model Modes and ALM
  3. Considerations when Enabling Deployed Mode
Warning: Do NOT 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 Working with Revision Tags.

Consider the following when enabling deployed mode in a model.

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

  1. Make the structural changes in a compatible development (source) model, in standard mode.
  2. Use Compare and Synchronize to move structural changes from the development (source) model to the production (target) model (do not disable deployed mode).

For reasons of security and data integrity, we recommend 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.