search

department-of-veterans-affairs / va.gov-cms

Editor-centered management for Veteran-centered content.
https://prod.cms.va.gov
GNU General Public License v2.0
99 stars 69 forks source link

Discovery: Document PDF Download use cases to test changes against #10284

Closed wesrowe closed 2 years ago

wesrowe commented 2 years ago

Description

Before we start tinkering with the seemingly unnecessary API calls in #10235 and #10236, we need to understand all the use cases that Find-a-form supports so that we can ensure we don't break them.

A starter list of possible differentiators between use cases:

Any other differentiators?? Clues to consider:

Acceptance Criteria

CMS Team

Please check the team(s) that will do this work.

jilladams commented 2 years ago

🕵️‍♀️ Find VA Forms - Product Use Cases updated 11/19/2021, which was launch timeframe for adding the download modal. This turned up via va.gov-team/31832

This design intent cycle was re: "Epic - Find a VA Form PDF Download Instructions" #26816.

Specifically re: the modal:

Note - this modal is the product of user research recommendations. After users failed to notice inline info-text and notes related to Adobe Reader, Marci met with Ryan Thurwell and Angela Fowler, and they agreed that this was a good use case for a modal to draw needed attention. In that meeting, a high-level design was agreed upon, and a https://github.com/department-of-veterans-affairs/va.gov-team/issues/29704. Marci took this design to Collab office hours on 9/29 for feedback.

https://github.com/department-of-veterans-affairs/va.gov-team/issues/31832#issuecomment-951315456

User downloads PDF, opens in a browser and prints. User downloads PDF, opens in a browser, fills out online and prints. User downloads PDF, opens in a acrobat reader and prints.

https://github.com/department-of-veterans-affairs/va.gov-team/issues/31832#issuecomment-954287574

Let's try to wrap this up! From what I'm hearing, it's most important to solve for the problem of the user trying to fill out the form in their browser or open the PDF on their mobile device. It's secondary to mention how to print it out, though good to mention for users who want to fill in their info by hand and mail in their form.

I checked with our stakeholder in disability comp and he said users can upload a claim through direct upload, which we link to from a handful of locations on our site. So explaining how to complete a fillable PDF on screen is important for users who want to type into the boxes rather than handwrite the info--and then either upload the form through direct upload or print it out.

Ticket pile, chrono

And:

jilladams commented 2 years ago

Next steps: summarize relevant use cases for FE tickets blocked by this issue.

wesrowe commented 2 years ago

Based on a meeting this morning, it sounds like form-hosting origin might be an additional wrinkle that is not covered by the linked use cases. I.e., Daniel said that only forms hosted in www.va.gov get pre-fetched (and thus have the pre-fetch point of failure).

Also of note – the use cases are all in TestRail. Not a tool we've used before now.

wesrowe commented 2 years ago

Closing since the documented use cases that Jill found meet the requirement. Adding link to use cases doc to the epic and relevant stories.