Skip to content

526 Submission Disabilities Size must be between 1 and 150 #44200

Open
@michelpmcdonald

Description

@michelpmcdonald

Value Statement

As a 526 Disability Comp Claimant
I want to have form guidance business rule enforcement required number of issues
So that I can properly enter between 1 and 150 issues per claim so my claim can be submitted


Background context

We are saw this 526 submission rejection error around 9 times in June 2022:

count:      9(  0.18%), Error: [{"key"=>"form526.disabilities.Size", "severity"=>"ERROR", "text"=>"size must be between 1 and 150"}]

Sev-3:
Users that enter an invalid number of issues will have their claim submission rejected, however the error is not happening too frequently, around 15 times in June 2022.

Front End - Back End Devs might need to work together to try to reproduce and fix, typically BE provides the form data to reproduce via Form 526 InProgressFormJson and the FE adds or expands the form rules to enforce and provide an errors message so the user can self correct before submitting the form.

526 users can select from existing issues or write in new issues, between 1 and 150 are required. In the form JSON between vets-api and vets-web, 2 issues list are used ratedDisabilities for the existing ones, and newPrimaryDisabilities for added ones, however EVSS refers to the disabilities field, so at this point, I'm not sure, but I think perhaps the 2 vets api form fields are combined into 1 disabilities when we send the data to EVSS for submission.

Acceptance Criteria

  • _Validate Disabilities List size rules within the 526 form, provide form error message so users can self correct

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    526v 1 and 2HLRHigher Level Reviewbackendfront endsev-3Lowest severity triage incident

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions