As a developer of the Supplemental Claim app
I want to start building the frontend
So that it will be ready once Lighthouse completes the API
Background Context
After completing research on our Supplemental Claim prototype, we now want to implement these changes into the live Supplemental Claim form; but add it behind a feature toggle so that we can test and release the new form in stages.
The prototype was a completely separate app and did not involve any feature toggle code work, so implementing it in the main application will require extra caution to ensure that both versions can be submitted without issues.
Additionally, we may need to revisit our list & loop pattern. Consider switching over to the alternate list loop pattern developed by the forms team.
Outcome, Success Measure, KPI(S), and Tracking Link
Add here
Acceptance Criteria
[x] Feature toggle implemented
[ ] Data migration in place
[ ] All new pages added
[ ] Update confirmation page to show submitted data
Value Statement
As a developer of the Supplemental Claim app I want to start building the frontend So that it will be ready once Lighthouse completes the API
Background Context
After completing research on our Supplemental Claim prototype, we now want to implement these changes into the live Supplemental Claim form; but add it behind a feature toggle so that we can test and release the new form in stages.
The prototype was a completely separate app and did not involve any feature toggle code work, so implementing it in the main application will require extra caution to ensure that both versions can be submitted without issues.
Additionally, we may need to revisit our list & loop pattern. Consider switching over to the alternate list loop pattern developed by the forms team.
Outcome, Success Measure, KPI(S), and Tracking Link
Acceptance Criteria
Designs and Build Notes
Enablement team (if needed)
@ member of team
Out of scope
New API endpoint has not yet been implemented:
Open questions
Tasks
Definition of Ready
Definition of Done