Data gone missing? Protect your application with JamOps

We have added a feature to our JamOps tool to prevent data in a Mendix application being lost.

Autocommit in Mendix

When you save an object with data in an application, Mendix checks whether there is any related data that has not been saved yet. Mendix then saves that data automatically, to guarantee that the application works correctly.

It can happen that when the user logs out, the automatically saved data is deleted from the database. If that is not what you wanted, you have lost production data without noticing.

An example:

You fill in a form. The form consists of several parts, some of which you save explicitly. Mendix then saves the remaining parts automatically. At that moment it looks as though everything has been saved. When you log out, however, those remaining parts are deleted from the database. If you go back now, part of your data is missing. In this case, having the data go unsaved is not what you wanted.

JamOps

JamOps automates a range of tasks to improve the quality, security and efficiency of application development in Mendix. We recently added an extension that detects the scenario above.

The developers get a notification and the CI/CD pipeline is put on hold. They can then work out how the problem arose and change the model to solve it. After that the pipeline can continue. Read more about JamOps here.