We currently have a multiple approaches on when the validations should be shown on our table forms (Requisition View, Proof of Delivery View, Shipment View, Adjustment, Issue and Receiver screens). All validation are fired with a slight delay due to the debounce setting we're using. This was done to improve the performance.
...
Example: Batch Approval screen
Recap
| # | Option | Level of Effort | User Benefit | Performance Impact | Screens which would change if this option is selected |
|---|---|---|---|---|---|
| 1 | Mimic what the other forms do. | Small | Consistency across the whole system | None |
|
| 2 | Make errors appear after the fields has been touched. | Medium | Instant error feedback | None |
|
| 3 | Make errors appear after we leave (focus on something outside) the table row. | Large | When fields within a lineItem are dependent on each other the error won’t show until they focus away from the LineItem (row) | None |
But, this approach will also require changing how pagination shows the page errors, it now is inconsistent with this approach and might require noticeable amount of work to make it happen |
| 4 | Same as 3, but also highlight the table header. | Large | When fields within a lineItem are dependent on each other the error won’t show until they focus away from the LineItem (row) | None |
|
Programming approaches
Currently we have a couple of different approaches on how to deal with validations from the coding side.
...