[Epic] Resolve Errors

[angelcardoz]

Milestone: Resolve errors

Epic: Resolve Errors

Overview

• The Resolve errors page is the place where a user can look at all data errors for their uploaded file. The system will indicate what the errors are, where the errors are, and what they need to do about errors. The system will also allow the user to download a version of the validation report.
• A covered financial institution shall compile and maintain data regarding covered applications from small businesses. The data shall be compiled in the manner prescribed in 12 CFR § 1002.107 and the Filing Instructions Guide for the appropriate year. The data compiled shall include the items described in paragraphs (a)(1) through (20) of this12 CFR § 1002.107 .
• List item

Tasks

Use the following checklist to ensure each epic is built out properly. If needed, you can add or remove items.

• [ ] Pull together initial list of relevant user stories for this epic
• [ ] Make a list of the content requirements for this epic
• [ ] Make a list of the technical requirements for this epic
• [ ] Post current wireframes and mock-ups
• [ ] Review wireframes and mock-ups with FEWD, BEWD, Data, SBL Help, Content team members
• [ ] Refine user stories to prepare for development phase
• [x] Identify and capture tasks for user testing
• [ ] Conduct user testing

User stories

MVP (Beta release)

• [ ] https://github.com/cfpb/sbl-project/issues/111
• [ ] https://github.com/cfpb/sbl-project/issues/108
• [ ] https://github.com/cfpb/sbl-project/issues/185
• [ ] https://github.com/cfpb/sbl-project/issues/168
• [ ] https://github.com/cfpb/sbl-project/issues/167

Backlog (post-MVP)

• Story (link)

Requirements

Technical

• List item
• List item

Content

• Link item
• Link item

User testing

Research goals

• Learn when a filer would use the downloaded report and when they'd use the UI
• Determine how we can better organize errors on the page
• Capture expectations on needing to resolve errors before moving forward in the filing process
• Understand how filers go about resolving errors and what sort of support they need

Task ideation

• Review errors
• Upload a revised file
• Download the validation report
• For multi-field errors pagination, do users prefer 10 lines, 20 lines, or let user's choose (post MVP)?
• Do users know what a "record" is in a count label? Or should we use the word "row"?

Curent mock-ups

Updated: MM/DD/YYYY

Page name	Page name	Page name