We have a view with a auto-edit and auto-save form, we have 1 editable field which is a barcode, after entering a barcode and hitting <tab> (which a barcode scanner does) in universal the focus goes onto the next object and does not save the record, is that intended? (2022.2.14 gui)
Focus is on the 3 dots, top right.
Also: When entering the screen, I cannot change records because of the form being in edit mode, we first have to cancel the row and select a new row. For us not a big problem for now, but I don't think this is intended?
Best answer by Erik Brink
No, I don't think this is going to change in the near future. The Universal GUI has a less focus-based setup in compare to the Windows interface. Leaving the edited subject now shows a message to save stuff. I think the auto-save mechanism should try to save in these cases too. So it will be saved whatever the user is going to do next.
“When entering the screen, I cannot change records because of the form being in edit mode, we first have to cancel the row and select a new row.” Sounds like the GUI didn't have the auto-save mechanism enabled for some reason.
Auto-save is currently being triggered after another action including switching to another record. Only moving focus away will not save the record indeed.
Not being able to switch records sounds like a bug. Wild guess: do you have model insides enabled? If so, it will be a known issue.
No, I don't think this is going to change in the near future. The Universal GUI has a less focus-based setup in compare to the Windows interface. Leaving the edited subject now shows a message to save stuff. I think the auto-save mechanism should try to save in these cases too. So it will be saved whatever the user is going to do next.
“When entering the screen, I cannot change records because of the form being in edit mode, we first have to cancel the row and select a new row.” Sounds like the GUI didn't have the auto-save mechanism enabled for some reason.
No, I don't think this is going to change in the near future. The Universal GUI has a less focus-based setup in compare to the Windows interface. Leaving the edited subject now shows a message to save stuff. I think the auto-save mechanism should try to save in these cases too. So it will be saved whatever the user is going to do next.
“When entering the screen, I cannot change records because of the form being in edit mode, we first have to cancel the row and select a new row.” Sounds like the GUI didn't have the auto-save mechanism enabled for some reason.
For a customer I have form in auto-edit/auto-save, but this doesn't work if I understand correctly. I will always have to hit the save button? It's a single form for a single record. How can I auto trigger a save?
In this case auto-save will be triggered when the subject is left or when any other action is triggered, like executing a task.
For the case Robbert described in the past you can now easily use the auto-commit logic on a particular field. In you example this might save the record after every field being edited.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
