Implement auto save of current tab
Description
Environment
Attachments
- 02 Mar 2022, 03:23 PM
Activity
Carlos Ruiz March 3, 2022 at 3:04 PM
Hi @Heng Sin Low - I don’t expect too many exceptions, but anyways I implemented a simple mechanism to exclude Request and _Request (all)_ from the feature with pull request 1221
Can you please check if you like that approach?
Regards,
Carlos Ruiz
Heng Sin Low March 3, 2022 at 2:04 PM
As it is, this is off by default and any issue (I do expect we will have some) in the implementation is harmless.
The objective is to make it works everywhere. If later we found that’s not possible/practical, I will rather we just revert the whole thing.
Carlos Ruiz March 3, 2022 at 1:52 PM
Hi @Heng Sin Low
Testing I found a use case where this feature doesn’t work, I think it is important to implement some sort of include or exclude certain windows.
Test case as GardenWorld Admin:
enable auto save
open Request (all) window
must show maybe request 10000002
in Mail Template select Order Confirmation
Problem: because the way how this window behaves, the field Result is saved, moved to updates and immediately cleared
Without auto-save the user is sent to the Result field to complete the information before saving.
Heng Sin Low March 3, 2022 at 6:16 AM
The always re-produce able test case:
Focus to comment/help field
Type a single character (for e.g 9) and press tab immediately (as fast as you can)
Details
Assignee
Heng Sin LowHeng Sin LowReporter
Heng Sin LowHeng Sin LowComponents
Fix versions
Priority
Major
Details
Details
Assignee
Reporter
Components
Fix versions
Priority
Major
Implement experimental auto save of current tab. The auto save should happens for non-sort tab after user have enter all the mandatory fields.
Since it is experimental at this point, it will be off by default and you can turn it on by setting the tenant level ZK_AUTO_SAVE_CHANGES to Y. In addition to that, auto save will not happens if current tab has commit warning message or the auto commit user preference is turn off.