Submit FOI Request Screen - Personals Flow - Records about me

[m-prodan]

• As an applicant
• I want to be able to submit a request for my personal information
• so that I can receive records/information about myself

Assumptions & Scope This story reflects the need to eventually replace the angular web form with our own application. Forms.io will be used due to its ease of customization and low-code updates. For the BCSC sign in, we will use the existing BCSC Integration with the angular app - team does not need to customize the BCSC sign in, just direct the user to the ID verification and receive the token when confirmed. Note - there are no application fees for personal FOI requests.

What is IN scope? Pathway for submitting a personal FOI request Pathway to submit an "other" request This story will be limited specifically to the use case where a user selects "Requests about me"

What is NOT in scope? Pathway for submitting a general FOI request Introductory screens/new user walkthrough Child under 12, and Other person screen - covered under separate user story Specific Ministries Selected Based on Reason Covered Under Separate Story

Acceptance Criteria

Scenario 1: Information Collection Notice

• GIVEN an applicant is on the type of request submission page (https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097406)
• WHEN the user clicks on either submit general request
• OR they click on submit personal request
• THEN a modal will open with an information collection notice, with a button to continue or to cancel, similar to this:https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/937172886

Scenario 2: Cancel Activation

• GIVEN the information collection notice has activated
• WHEN the user clicks cancel

• THEN the modal will close and the user will remain on the types of requests/submission page

  Scenario 3: Continue Activation

• GIVEN the information collection notice has activated
• WHEN the user clicks Continue
• THEN the modal will close and the user will be taken to the submission page selected

Scenario 4: Submit Personal Request

• GIVEN the user has selected "Submit a personal request"
• AND the user is on the information collection notice
• WHEN the user clicks Continue
• THEN the modal will close and the user will be taken to the BC Services Card SIgn in Page: https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097396
• AND when the process is complete, will be taken to the specified individual page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097413
• AND the continue button will be disabled

Scenario 5: Personal Request - Specification

• GIVEN the user is on the specified individual page
• WHEN any of the boxes are checked
• THEN the continue button will become active
• AND the user can select other checkboxes (up to 3) https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097415

Scenario 6: Personal Request - Continue Activation

• GIVEN the user is on the specified individual page, and the continue button is active
• WHEN the user clicks continue
• THEN they will be taken to the personals reasons page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097414

Scenario 7: Select Reason

• GIVEN a user is on the personals reasons page
• WHEN they click on a reason box (eg. Your Time in Foster Care)
• THEN the box will be highlighted
• AND the continue button will be active

Scenario 8: Reasons Limit

• GIVEN a user is on the personals reasons page and has selected at least one reason
• WHEN they click on another reason box
• THEN that box will also be highlighted
• AND the user can do this to select a maximum of 3 reasons

Scenario 9: Continue Activation or Other

• GIVEN a user is on the personals reasons page and the continue button is active
• AND they have checked off that they are making the request for themself
• WHEN they click on the continue button
• OR the other button
• THEN they will be taken to the request description page(https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097407)
• AND the next button will be disabled

Scenario 10: Mandatory Fields

• GIVEN a user is on the request description page
• WHEN they have entered a valid date range
• AND have entered characters into the request description field
• THEN the next button will be active

Scenario 11: Calendar Date Picker - Dates cannot be in future

• GIVEN a user is on the request description page
• WHEN they have activated the calendar picker
• THEN they will be unable to pick a date in the future

Scenario 12: Calendar Date Picker - End Date Cannot Exceed Start Date

• GIVEN a user is on the request description page
• WHEN they have activated the calendar picker for end date
• THEN they will be unable to pick a date that precedes the start date

Scenario 13: Request Description - Activate Next

• GIVEN a user is on the request description page
• AND the user has filled out required fields (description, start/end dates)
• WHEN they have click on next
• THEN they will be taken to the select public body page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097417
• AND the next button will be disabled (if no public bodies are selected)

Scenario 14: Select Public Body

• GIVEN a user is on the request description page
• WHEN they have click on a box next to a public body
• THEN the next button will become active
• AND they can select other public bodies (maximum - all)

Scenario 15: Select Public Body - Activate Next

• GIVEN a user is on the select public body page and the next button is active
• WHEN they click next
• THEN they will be taken to the contact page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097408

Scenario 16: Select Public Body - Activate Next

• GIVEN a user is on the select public body page and the next button is active
• WHEN they click next
• THEN they will be taken to the contact page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097408

Scenario 17: Contact Details - Mandatory Fields

• GIVEN a user is on the contact information page
• WHEN they enter an email address
• OR a complete mailing address
• THEN the next button will become active

Scenario 18: Contact Details Activate Next

• GIVEN a user is on the contact information page, and the next button is active
• WHEN they click next
• THEN they will be taken to the review request page https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097409

Scenario 19: Review Request Page

• GIVEN a user is directed to the review request page
• WHEN the page loads
• THEN they will see a layout of the information they have provided in the prior screens
• AND there will be a captcha field
• AND the submit request button will be inactive

Scenario 20: Enable Submit Request

• GIVEN a user is directed to the review request page
• WHEN they successful enter the captcha
• THEN the submit request button will be enabled

Scenario 21: Submit Request

• GIVEN the submit request button is active
• WHEN they click on submit request
• THEN they will be taken to the confirmation page (https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/937172887) https://jacklyn808742.invisionapp.com/console/share/RSBDPXJGKAW/936097412 (placeholder)

Scenario 22: Back Button (all screens)

• GIVEN an applicant is on any screen of the online form
• WHEN they click the back button
• THEN they will be taken back to the page prior to the one they are on

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

Definition of Done

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

[m-prodan]

@JHarrietha-AOT @KaraBeach - this one's a doozy - I think we need to capture this whole flow in one story, despite how many AC's we have right now. That said - I limited this one to just the personals flow, with the following assumptions:

• Records being requested about themselves
• Applicant is submitting "Other" instead of reasons (separate stories)
• The on-behalf ofs, and the "Reasons" should be covered under separate stories

@JHarrietha-AOT - I want to bring your attention to:

• Scenario 1-3 -> Information Collection Notice from our current webform
• Scenario 5 -> Users should be able to select multiple choices (myself, my kid, and someone else). While rare, we do sometimes have parents making a request about themselves, and also their kids or partner (or sometimes all 3). I've written the AC to allow for this
• Scenario 7 -> Reasons - since we thought we could allow for up to 3, I wrote out the AC here to allow for this. I'm having second thoughts about allowing multiple reasons, because I feel like our ideas might be too complicated for the average user. Can discuss more at refinement or ahead of time!
• Scenario 19 - I added a captcha field here prior to submitting a request, since this is a personals it doesnt need to go through payment, so slightly different design needed
• Scenario 21 - Will need an updated design for submit successful for personals, since there is no receipt that will be mailed

[JHarrietha-AOT]

@m-prodan I have included updated designs based on the points you listed above. The only one I havn'y updated is the CAPTCHA, I will leave that to the devs to decide which we should include and how it will look.

Let me know if you have any additional updates you would like me to make