Committing Autocommitted Objects - Shouldnt we (Mx developers) be able to dictate what happens to data associated to a current user session when that user logs out - Mendix Forum

Committing Autocommitted Objects - Shouldnt we (Mx developers) be able to dictate what happens to data associated to a current user session when that user logs out

1

Hi there,

In the earlier Mendix versions we could create objects and commit them later to the database.

But it now seems that any object that goes into an auto-committed state (creating object without committing) will inevitably go missing (auto-committed), even after explicitly committing the object (a number of times(There seems to be an issue with the commit action microflow activity on Mx version 7.23.2)), when the user logs out the auto-committed objects get deleted.

Even if we have an entity constrained not to be deleted by any user in the system (not even admin), these auto-committed states are causing these objects to still go missing! – in order to prevent this from happening I just include a commit in the create action in the microflow. Instead of the object going to auto-committed state it changes to normal and the object wont go missing – it remains in the database.

Could we please have some functionality on the Modeler/Studio that could allow developer to toggle the Operation (Commit/Delete) made on auto-committed objects when the user logs out?

So Instead of automatically deleting auto-committed objects: the user/(we) can then decide what should happen to auto-committed objects when a session is logged out.

also can you please include the object GUID on auto-committed objects console logging. When data goes missing we have no way of referencing these objects, and these auto-commits seem to be the only/last trace of the object on the system.

asked
0 answers