-
Notifications
You must be signed in to change notification settings - Fork 214
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
Spike | Failing Award Service API #76465
Comments
CC: @steele-lm from zoom chat |
There is a logic failure that was mentioned by Dewayne in that #73696 ticket. There is no check done to see if the net worth is greater/equal/less than the $130,773 limit. All that is need is to add in that check for that value |
Ignore the above mentioned logic issue. The check that is being done returns a boolean true/false. I'm think there may have been some confusion as the form key is 'household_income' but it returns true or false, not a number of any type. |
@sanjabaj2 I've twice now reached out to our contacts on this issue. Hopefully I see a response, but I may need help in escalating this further. |
I am not sure it is clear what is your question? Today's email is asking them to check your test from today. Also, did you check that service award Swagger link? |
@sanjabaj2 no need to worry as I think we have some more eyes on this. Update: Linda Ciston gave me the contact to give info on connecting to the PRODTEST db instead of the LINKTEST db. However, I'm not sure what exactly to do with the info I was given. Maybe @evansmith can give some further insight tomorrow |
Adding in some of my own research on available back-end data: |
Issue Description
Original epic to implement the values associated with the net income question: #7759
Currently, all dependency pension claims submitted to RBPS SHOULD off-ramp for manual processing because a person must review income and net worth information. (We need to validate this is happening.)
Until this information is submitted to RBPS from VA.gov, these pension claims cannot be processed through RBPS and will continue to be off-ramped for manual processing.Research done in #73696 determined that a flipper in production is preventing this information from being passed to RBPS. The flipper controls code that calls an outside service, and that service is currently failing for an unknown reason. RBPS may also have had issues accepting the new values.
Suspicion is that this service may return the current net worth limit and indicate if the Veteran is eligible of or in receipt of pension,
which would mean they need to answer the net worth question at the end of the 686/674 form flow (and the "did this student have income" question?). If the Veteran is receiving a pension benefit, VA.gov should set the claim for manual processing (and not send it to RBPS) and label the claim.The call is an Oracle call as follows:
ws_award_data_prc. vetIsEligCplPension, will always return one row.
PROCEDURE vetIsEligCplPension (pi_vet_id IN NUMBER
,po_isEligibleForPension OUT VARCHAR2
,po_vet_found OUT VARCHAR2
,po_isInReceiptPension OUT VARCHAR2
,po_net_worth_limit OUT NUMBER
) IS
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: