Open freeheeling opened 9 months ago
Asked @sbwiley to do a bit of digging on this
Resources from 4/10/24 planning:
@juliepedtke - This is a Code Yellow ticket that looks like it needs to be reviewed by R&D first before we can implement a change. Will you please let me know if you agree or disagree and then we can decide what to do next. Thanks
Hi @lisacapaccioli - it looks like the Decision Reviews team had the same issue and already got their error text run by CAIA, so let's not reinvent the wheel and we can repurpose the copy from their Figma, which Scott linked above. Thanks!
Questions - how would a Veteran fix this kind of problem, is it possible? Non-disability team has the same issue and are wondering what the solutions for these are.
Exceeding document size and page size limits were the 2 categories of Lighthouse Benefits Intake API failures documented in Investigate non-zipcode LH failures #75296, with the majority of failures attributed to page size violations. If there's any requirement that neither the frontend nor backend seems to be validating, it's page size. This can, perhaps, be accomplished by reading the file content and extracting the image dimensions. The 'pdjs-dist' library (already installed) might be used to find a PDF's dimensions. If it was determined a file's page size dimensions didn't meet the given criteria, an error message could be returned to the user notifying them of the issue.
I was able to successfully upload a PDF with the following dimensions: 100" wide by 120" high (resolution: 7200x8640; for reference, a PDF unit is 1/72 of an inch), which exceeds the 78" wide by 101" high limitations imposed by the Lighthouse Benefits Intake service. Currently, EVSS does not have any restriction on page size. It seems prudent to implement a UI validation to prevent an initially accepted file upload from ultimately not being processed.
In the case of an upload exceeding the accepted page size limitation, a useful error message would need to be displayed. Input from design is requested, but following is a suggestion as to how this might be conveyed mentioned in this Slack thread covering the same page size validation issue:
Research and documentation of findings supporting this change request found here.