Feature Story Description:
| Anchor | ||||
|---|---|---|---|---|
|
Admin want the ability to save a form before publishing it.
The user should be able to create a new form and click the Save button to save their progress. They should be able to navigate back to any saved forms and continue to edit/complete the form, and click the Save button as many times as they like (there should be no limit on the number of saves/versions). Question - is Submit = Publish?
Business Rationale:
top page
This functionality will allow for staged publishing of forms, where a user can update the form periodically as opposed to all at once. This will encourage more error validation checks before final form is published
Priority (MoSCoW): N/A
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency (parent/child) | 1 | 2 | 3 | 4 |
6 | Parent | |||||
|
Technical Details:
OOTB feature.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
5 |
|
|
Prototype/Mockups
Provide high fidelity prototype or mockup
Out of Scope:
the setup of a Save button from the form designer is not part of this user story 
validation piece…?
Contact(s):
this story will likely be needed in and built for all four business areas.
Table of Contents
| Table of Contents |
|---|