Comment 2 for bug 1693563

Hi Scott,

I see the behavior you described, but I see the same behavior in the XUL client. See the screencast at https://drive.google.com/file/d/0B74gDMUDwDXqOWFGdUxSWmRMRDg/view.

I think the intended workflow here is that the invalidate button automatically saves the record, and staff therefore should not click Save if that is the only change made to the record. However, I didn't see any documentation on this feature, and I could be wrong.