Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
User Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
As an Submitter I want to be able to create & save a pre-populated template for a given form. This can be done in two different ways:
A Submitter submits the form once which generates a submission that they can go back to whenever they want. The new feature would be that if they want to submit the form again (i.e. new quarter) then they can start from the previously completed submission to have the field pre-populated from that previous submission
A Submitter simply generates an actual “template” type submission which can then be used to create a new submission which would be pre-populated with the values set in the template.
At this point, both solutions should be explored, as they can both serve their own purpose.
Business Rationale:
Priority: Could Have
Some forms are filled out on a regular basis and some data points will have the same value from one submission to another. Having them pre-filled can simplify the user experience and help with data consistency by limiting the load on the user.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
3 | #3: (Submitters) Field Pre-population from previous submission | Child |
23 | #23: (Submitter) Assign External/Custom Validation Rules to Forms | Parent |
|
| |
|
|
Technical Details:
Custom feature
Solution options:
This can be at the submitter level to save specific pre-filled drafts or re-use previous submissions to start a new one
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
Contact(s):
Table of Contents
| Table of Contents | ||||
|---|---|---|---|---|
|