-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
58745 VAMC optional fields #12996
58745 VAMC optional fields #12996
Conversation
We discovered that these newly optional fields are required in EVSS. Do not proceed with this PR until after EVSS has made corresponding changes. Currently scheduled for 7/12/23. |
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This PR has been closed because it has had no activity for 37 days |
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This PR has been closed because it has had no activity for 37 days |
Summary
vets-json-schema
(once that PR has been mergedvets-json-schema
is merged, a new commit with the updated reference must be pushed to this PR. Then, it will be taken out of Draft mode. DO NOT MERGE UNTIL THENRelated issue(s)
Acceptance criteria
Requested Feedback
(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?