saderagsdale
commented
5 months ago Note:
When a 526 is submitted by mail, it seems that someone manually scans and uploads the documents that were submitted. I wonder if we can use this approach as an "offramp" for evidence that gets rejected downstream.
Value Statement
As a Veteran who has submitted evidence that, without my knowledge, fails to make it through all systems downstream of VA.gov. I want VA to have a last-resort backup process for such failures So that my evidence is considered along with my appeal.
Background Context
Coming out of https://github.com/department-of-veterans-affairs/va.gov-team/issues/71451, we have created several tickets to follow up on downstream evidence submission errors we have seen on the NOD and SC forms. But, inevitably, there will be errors we can't handle, or future errors that we haven't considered yet. In these cases, we need to have some kind of backup process to ensure that all evidence is submitted successfully, or to at least inform the Veteran that the evidence was not submitted successfully.
Fortunately, Lighthouse sends a daily and weekly report of downstream errors for evidence submissions on the NOD and SC forms, with the guids we need to identify and investigate the failed submissions, and identify the submitting Veteran. We also have the ability to query statuses of evidence submissions (and appeal submissions) on our own. See https://github.com/department-of-veterans-affairs/va.gov-team/issues/76819.
But we have yet to come up with a backup process, manual or automated, to deal with unhandled failed submissions. The aim of this ticket is to come up with ideas for such a process.
Tech Tasks
Acceptance Criteria
Definition of Ready
Ready now.
Definition of Done