Conditional logic for Service Locations fields

[davidmpickett]

User Story or Problem Statement

One of the logical follow up iterations to consider for Service Locations is implementing conditional logic on the Drupal side to make certain sections of the form visible/hidden required/not required based on initial selections and other factors.

@davidmpickett in #17515

Service Options fieldset

• This fieldset should always show
  • (except on Non-clinical services?)
• Choices in this fieldset should impact later fieldsets
  • (except on Non-clinical services?)

    Appointments fieldset

• This fieldset should never show on Non-Clinical Services?
• This fieldset should only show if the user has made a selection in Service Options fieldset that indicates appointments are possible.
• See chart in VBA content specs

Address fieldset

• This fieldset should only show if user has selected something other than NO for Office Visits
• This fieldset should always show on non-clinical services? Contradiction in logic?

• 17380

Hours fieldset

• This fieldset should always show
• Future proofing - what about online self-service modality or submit by mail modality?

Contact Info

• This fieldset should always show
• Future proofing - what about online self-service modality or submit by mail modality?

Acceptance Criteria

• [ ] Testable_Outcome_X
• [ ] Testable_Outcome_Y
• [ ] Testable_Outcome_Z
• [ ] Requires design review
• [ ] Requires accessibility review

[jilladams]

@Agile6MSkinner added this to the Pilot epic but if it's not actually MVP launch blocking (it's not) we need to put it somewhere else.

[Agile6MSkinner]

For non-launch-blocking items, we are using the VBA National Rollout epic. I've added this ticket to it.