Question

How to avoid the there are unsaved changes message

2

Is there any (doesn't matter how dirty) way of disabling the mechanism that throws the message 'there are unsaved changes, please save or cancel the changes'? We are using a lot of custom 'save' and 'apply' buttons, but if we save an object using a microflow, the client will still show the message 'there are unsaved.....' as it doens't 'pick up' that the changes already have been saved. This results in inconsistent behaviour where the user doesn't understand why his / her changes aren't saved (they are, but the client tells them different)

asked 2010-01-11

Michel Vermeer

2 answers

Herbert Vuijk · Answer 1 · 2010-01-19

You have to do a rollback (from 2.4.x there's a object / rollback microflow activity) in your custom cancel microflow before the close form action, otherwise the client would (justly) give the message you described. I guess you only close the current form in your microflow.

This have to fix your problem, it also works for me.

@N.b: You said you use a custom save button that doesn't close the screen, but only saves the object. In that case be sure you checked the "Refresh in client" box in your commit action. Let me know if this solves your problem.

Michel Vermeer · Answer 2 · 2010-01-20

The problem is that we also have an 'apply' button that saves the changes but doesn't close the form. If the user then tries to navigate to another form or e.g. uses the 'back' button, then the message appears (and subsequently, the user thinks that the 'apply' button isn't functioning properly...