When dealing with a long form with a lot of input fields, it was determined that there was a need to auto-save progress on a given form and/or table.
This would be to enable the user to leave or stop working on the form without worrying that their progress would be lost.
This can be done in a number of ways, including validation per input:
As well as globally, telling the user that changes have been saved (seen below in the header).
We need to work with the Housing team to understand this need and determine if it is something that is useful and unique, and bring it through the contribution process to determine priority.
No matter the outcome of if it will be a part of the design system, it’s important to track this as something that a service team is doing so that when the next team comes looking for the same thing, we can connect those teams and adjust our evaluation based on the criteria.
Spark450
commented
1 month ago
When dealing with a long form with a lot of input fields, it was determined that there was a need to auto-save progress on a given form and/or table.
This would be to enable the user to leave or stop working on the form without worrying that their progress would be lost.
This can be done in a number of ways, including validation per input:
As well as globally, telling the user that changes have been saved (seen below in the header).
We need to work with the Housing team to understand this need and determine if it is something that is useful and unique, and bring it through the contribution process to determine priority.
No matter the outcome of if it will be a part of the design system, it’s important to track this as something that a service team is doing so that when the next team comes looking for the same thing, we can connect those teams and adjust our evaluation based on the criteria.