Revert unwanted changes in ALM development lifecycle

Learn how to revert unwanted changes caused by production issues in your model. In any development lifecycle, issues or bugs can sometimes be introduced into production.

Before you revert any unwanted changes, make sure:

• You only fix production issues in development models. Issues fixed directly in the production model will make that model incompatible for future synchronization.
• That no new features are currently in development.

If a production issue is discovered in your model, there are a few different options you can take to resolve it (see options 1-3).

Fix the issue in the development model, then wait until the next planned update or release. At that time, promote the fix to your production model together with other development changes. Choose this approach if the issue doesn't seriously affect production users.

Revert the unwanted changes from the development model and then synchronize with production. If you choose this approach, be aware of the risk of losing work in progress, such as unfinished functionality.

To revert unwanted changes from a development model:

1. Restore the development model to a restore point ID that existed before the unwanted changes were made. For help, see History.
   Revision tags are not captured in the change history of a model. To help keep track, you might want to increment the version of your model in a separate "revisions" list in the source model. 
2. When the model restore is complete, add a revision tag to the development model.
3. To resolve the issue in the production model, synchronize the development model with the production model.

It is optional to restore the development model to an earlier point. If the issue is simple, you can make changes in the development model to resolve the issue, add a revision tag, and then synchronize it with the production model.

To avoid losing work in progress, follow the steps described in Fix production issues.