Skip to content
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

VACMS-16300: Update audits/views for service location changes #17479

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

Becapa
Copy link
Contributor

@Becapa Becapa commented Mar 11, 2024

Description

Relates to #16300.
This can't be merged until after the integration-service-location branch is merged into main and validated.

Removes the fields that will no longer be included on the facility services content type.

Testing done

Manually Tested

QA steps

As an administrator

  1. Browse to the Service Locations Detailed Audit (/admin/content/audit/service-locations-detailed)
    • Validate that the following columns have been removed:
      • field_hservice_appt_intro_select ('OLD: Appointment intro text')
      • field_hservice_appt_leadin ('OLD: Appointment lead-in text')
      • field_online_scheduling_availabl ('OLD: Is online scheduling available for this service?')
      • field_walk_ins_accepted ('OLD: Are walkins accepted?')
      • field_phone_numbers_paragraph ('OLD: Phone number for appointments')
  2. Browse to the VAMC Facility Health Services view (/admin/content/facilities/vamc-facility-health-services)
    • Validate that the following columns have been removed:
      • field_walk_ins_accepted ('Walkins accepted')
      • field_online_scheduling_availabl ('Online scheduling')
    • Validate that the following exposed filters have been removed:
      • field_walk_ins_accepted_value ('Walkins accepted')
      • field_online_scheduling_availabl_value ('Online scheduling')

Definition of Done

  • Documentation has been updated, if applicable.
  • Tests have been added if necessary.
  • Automated tests have passed.
  • Code Quality Tests have passed.
  • Acceptance Criteria in related issue are met.
  • Manual Code Review Approved.
  • If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

  • CMS Team
  • Public websites
  • Facilities
  • User support
  • Accelerated Publishing

Is this PR blocked by another PR?

  • DO NOT MERGE

Does this PR need review from a Product Owner

  • Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

  • Yes, and it's written in issue ____ and queued for publication.
    • Merge and ping the UX writer so they are ready to publish after deployment
  • Yes, but it hasn't yet been written
    • Don't merge yet -- ping the UX writer to write and queue content
  • No announcement is needed for this code change.
    • Merge & carry on unburdened by announcements

@Becapa Becapa added the DO NOT MERGE Do not merge this PR label Mar 11, 2024
@va-cms-bot va-cms-bot temporarily deployed to Tugboat March 11, 2024 17:16 Destroyed
@github-actions github-actions bot added the Facilities Facilities products (VAMC, Vet Center, etc) label Mar 11, 2024
@va-cms-bot va-cms-bot temporarily deployed to Tugboat March 12, 2024 13:07 Destroyed
@Becapa Becapa force-pushed the VACMS-16300-update-audits-for-service-location-changes branch from bee16f7 to 197fc89 Compare March 12, 2024 15:34
@va-cms-bot va-cms-bot temporarily deployed to Tugboat March 12, 2024 15:35 Destroyed
@omahane omahane self-requested a review March 14, 2024 16:34
Copy link
Contributor

@omahane omahane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks right and meets the ACs.

I noticed that the "New:" in the column headers of the first view are no longer relevant after the old fields are removed. Should we change those labels?

Screenshot 2024-03-14 at 11 25 05 AM

@Becapa
Copy link
Contributor Author

Becapa commented Mar 14, 2024

This looks right and meets the ACs.

I noticed that the "New:" in the column headers of the first view are no longer relevant after the old fields are removed. Should we change those labels?

That makes sense to me! I'll fix those up right quick.

@va-cms-bot va-cms-bot temporarily deployed to Tugboat March 14, 2024 16:48 Destroyed
Copy link

GitHub Workflows (.github/workflows/*.yml)

Have you...

  • pinned all affected GitHub Actions at a specific commit by SHA?
  • reviewed the source code of the action at the commit you are pinning?
  • confirmed that no GitHub security measures are being bypassed?
  • checked for any injection of user content into protected contexts?
  • reviewed Security hardening for GitHub Actions?
  • reviewed GitHub Workflows?

@va-cms-bot
Copy link
Collaborator

va/tests/status-error:


entity_update
Title Entity/field definitions
Severity Error
Sid 2
Description The following changes were detected in the entity type and field definitions.
.... Content

         * The /node.field_address/ field needs to be updated.                        
         * The /node.field_mailing_address/ field needs to be updated.                
         * The /node.field_vamc_med_records_mailing/ field needs to be updated.       
                                                                                      
        .... Paragraph                                                                
                                                                                      
         * The /paragraph.field_address/ field needs to be updated.                   

Value Mismatched entity and/or field definitions

Copy link
Contributor

@omahane omahane left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks great.
Screenshot 2024-03-14 at 4 05 39 PM

We'll need to rebase this branch once integration-service-location is merged.

omahane and others added 6 commits May 13, 2024 11:50
* VACMS:14704: Adding service modalities

* VACMS-14704: Adds vocabulary

* VACMS-14704: Adds free-text fields.

* VACMS-14704: Update langage around service delivery

* VACMS-14704: Updates taxonomy label and description
* VACMS-14704: Adding service location fields (#15599)

* VACMS:14704: Adding service modalities

* VACMS-14704: Adds vocabulary

* VACMS-14704: Adds free-text fields.

* VACMS-14704: Update langage around service delivery

* VACMS-14704: Updates taxonomy label and description

* VACMS-16348: Removes unnecessary and undesired fields

* VACMS-16348: Adds service options, office hours and virtual support

* VACMS-16348: Adds appointment fields

* VACMS-16348: Adds online scheduling field

* VACMS-16348: Adds a necessary question mark

* VACMS-16348: Updates description for office visits
* VACMS-14704: Adding service location fields (#15599)

* VACMS:14704: Adding service modalities

* VACMS-14704: Adds vocabulary

* VACMS-14704: Adds free-text fields.

* VACMS-14704: Update langage around service delivery

* VACMS-14704: Updates taxonomy label and description

* VACMS-16348: Removes unnecessary and undesired fields

* VACMS-16348: Shows Custom text when Customize text is selected

* VACMS-16348: Trying to get the default text

* VACMS-16348: Adds default text to Service Locations for VAMC facility health and Service region

* VACMS-16348: Removes VAMC Facility Health Service-level appointment code

* VACMS-16348: Adds VBA Facility service appt lead-in default text

* VACMS-16348: Adds VBA FAcility service appt default text UX

* VACMS-16348: DRYing off this code for the different content types and fields

* VACMS-16348: Adds nonclinical service default text field

* VACMS-16348: Restores the errant revision_log and adds right field for vba_facility_service

* VACMS-16348: Moves work out of backend and vamc and into facilities

* VACMS-16348: Trying to get paragraph validation to work

* VACMS-16348: Adds required state to custom text

* VACMS-16348: Removes text validation, as not working, for now

* VACMS-16348: Removing commented out code
…tion (#17225)

* VACMS-17142: Update cypress test to use phone number in service locations

* VACMS-17142: Hide VAMC Facility Health Service fields that are no longer in use.

* VACMS-17142: Have the view_display mirror the form_display.

* VACMS-17142: Add revision_log back.

* VACMS-17142: Update service location paragraph view display to mirror form display.
@omahane omahane force-pushed the VACMS-16300-update-audits-for-service-location-changes branch from 2ae7b13 to cc52be8 Compare May 13, 2024 17:08
@va-cms-bot va-cms-bot temporarily deployed to Tugboat May 13, 2024 17:08 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat May 13, 2024 17:31 Destroyed
@omahane omahane force-pushed the VACMS-16300-update-audits-for-service-location-changes branch from f3501f4 to 19e1933 Compare May 13, 2024 17:36
@va-cms-bot va-cms-bot temporarily deployed to Tugboat May 13, 2024 17:36 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat May 13, 2024 17:41 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat May 13, 2024 18:00 Destroyed
@va-cms-bot va-cms-bot temporarily deployed to Tugboat May 14, 2024 16:38 Destroyed
@jilladams jilladams removed the DO NOT MERGE Do not merge this PR label May 15, 2024
@jilladams jilladams requested a review from dsasser May 15, 2024 16:48
Copy link
Contributor

@dsasser dsasser left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Screenshot 2024-05-15 at 10 23 38 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Facilities Facilities products (VAMC, Vet Center, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants