Appointment Request - Check user for requestappointment authorizedService

[MekoHong]

Description

As a user, I want to initiate my appointments request using the mobile app.

As part of this story we want to:

• Check /v1/user to determine if a user is eligible for scheduling appointments (scheduleAppointments)

Data schema

Documentation: https://department-of-veterans-affairs.github.io/va-mobile-app/api/#operation/v1/user.getProfile

"meta": {
"availableServices": [
"appeals",
"appointments",
"claims",
"directDepositBenefits",
"lettersAndDocuments",
"militaryServiceHistory",
"userProfileUpdate",
"scheduleAppointments"

Acceptance Criteria

1. - [ ] Check get /v1/user service to determine if scheduleAppointments is an available for signed in user 2. - [ ] Verify when a user selects 'Request appointment' from the appointment list and the user is NOT eligible to schedule appointments that error screen 'We can't find your facility registration' (see sketch below) is displayed 3. - [ ] Verify when user selects 'Back' on the error screen they are directed back to the appointment list screen* 4. - [ ] Verify when user selects 'Find health facility' button that they are directed to the va.gov Find a VA location screen **Accessibility Requirements** Standard: 1. Everything on the page should be read by the screen reader. - If anything is being conveyed visually only (buttons, menu items, list, tables, images, headings, forms, etc) the component type needs to be announced by the screenreader. (Include name (title), role, value) Each page should support text resizing based on the OS font scaling settings without loss of content, content overlap, or horizontal scroll. 2. Each touch target must be at minimum 44px by 44px 3. All elements on a page should be able to be traversed by an auxiliary keyboard. As a user uses the keyboard to navigate a page, its focus element should be clear. 4. The app needs to support operability by tap (no gestures) or voice control only. In cases where gestures occur, e.g. scroll, ensure these simple gestures are operable through the OS’ built-in capabilities. Wireframe: [Can't Find Your Registration Error Screen](https://www.sketch.com/s/806417fd-3d64-4da6-9529-0eef4fd48e2e/a/WKV0O32#Version) ) ## Test Accounts vets.gov.user+14 vets.gov.user+189 ## Notes & Open Questions - Confirm with Lauren, when user selects Back from the error screen should we land user to the Health Care screen or Appointment List screen - Dependencies/Roadblocks: - Any internal/external dependencies? - Test accounts needed? - Does this require QA? - Dev Notes: ## Ticket Checklist - [X] Acceptance criteria defined - [X] Labels added (front-end, back-end, feature) - [X] Linked to an Epic

[digitalken]

Test case added: https://dsvavsp.testrail.io/index.php?/cases/view/19330

[MekoHong]

Closing ticket, feature not being currently worked and due to lapse in time it was decided to close all scheduling tickets. No testing of tickets and will revisit in future