In any development lifecycle, issues or bugs can sometimes be introduced into production.
If a production issue is discovered in your model, there are a few different approaches you can take to resolve it:
- 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.
- As explained below, 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 avoid losing work in progress, follow the steps described in Fix production issues.
Warning: Regardless of your chosen approach, you must only fix production issues in development models. Fixing issues directly in the production model will make that model incompatible for future synchronization.
To revert unwanted changes from a development model:
- Restore the development model to a restore point ID that existed before the unwanted changes were made.
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.
Note: Make sure that no new features are currently in development.
- When the model restore is complete, add a revision tag to the development model.
- To resolve the issue in the production model, synchronize the development model with the production model.
Restoring the development model to an earlier point is optional. If the issue is simple, you can resolve it by making changes in the development model, adding a revision tag, and then synchronizing with the production model.
