[Forms] [SPIKE] Determine current checks/balances for forms upload and how we can improve upon and add additional checks

[FranECross]

Status

[2024-08-08] [Fran] Checking with Michelle via Slack if this should still be prioritized as it currently is.

Description

We currently have automation around forms being uploaded to the Forms DB to help mitigate broken links surfacing to Veterans.

This SPIKE is to list the current automated checks/balances around form uploads, as well as determine what other automations are possible to mitigate broken links.

For instance:

Questions

• Is it possible to use Drupal CMS as an intercept before it gets to LiteHouse to prevent errors?

User story

AS A Veteran, their family member, caregiver or survivor
I WANT to click a link for a form in VA.gov and have the form display/download correctly
SO THAT I can continue with the task at hand

AS AN editor who manages and uploads forms
I WANT ensure I'm following best practices and guidance, and if I run afoul of said best practices and guidance, causing a possible broken link
AND I WANT to receive notification to fix and that my form wasn't uploaded
SO THAT I can correct any errors and the Veteran won't encounter any broken links.

Engineering notes / background

Analytics considerations

Quality / testing notes

Acceptance criteria

• Are we currently validating all the fields we put out are complete?

Having to do with Files:

• Run a check for whether or not a file exists, and trigger a flag if it doesn’t.
  • Notification then goes to the author.
• Run a check to see if there’s a missing parameter
  • if so, create a feedback loop/notification to Nancy (or all four forms managers) that the form hasn’t been pushed due to the missing parameter.
  • Are we able to provide details in the feedback?
• Run a check check when a new file is created, and if there’s a missing parameter, trigger a flag.
• If so, create a feedback loop/notification to Nancy (or all four forms managers) that the form hasn’t been pushed due to the missing parameter.
• Are we able to provide details in the feedback?
• Run an automated check when an existing file is updated, and if there’s a missing parameter, trigger a flag.
  • If so, create a feedback loop/notification to Nancy (or all four forms managers) that the form hasn’t been pushed due to the missing parameter.
  • Are we able to provide details in the feedback?

Having to do with Forms:

• Run a check for whether or not a form exists, and trigger a flag if it doesn’t.
  • Notification then goes to the author.
• Run a check to see if there’s a missing parameter
  • if so, create a feedback loop/notification to Nancy (or all four forms managers) that the form hasn’t been pushed due to the missing parameter.
  • Are we able to provide details in the feedback?
• Run a check check when a new form is created, and if there’s a missing parameter, trigger a flag.
• If so, create a feedback loop/notification to Nancy (or all four forms managers) that the form hasn’t been pushed due to the missing parameter.
• Are we able to provide details in the feedback?
• Run an automated check when an existing form is updated, and if there’s a missing parameter, trigger a flag.
  • If so, create a feedback loop/notification to Nancy (or all four forms managers) that the form hasn’t been pushed due to the missing parameter.
  • Are we able to provide details in the feedback?

[FranECross]

Asked Michelle via Slack to please check/confirm prioritization of this ticket.