Add validation to the Operating Status Details to make it required when non-normal (not launch blocking)

[omahane]

User Story or Problem Statement

As an editor, I want to ensure that I have filled out the Details section of the Operating status when the status is anything but normal.

Implementation steps

Constraint validation using PHP (VBA)

We have done something like this on VBA facility banners. If the editor chooses Display a banner alert on this facility, then subordinate empty fields will throw a validation error.

Javascript validation (Campaign Landing Page)

We have another pattern on Campaign Landing Page which prevents the user from submitting the form if they have enabled a given section, such as Events, but have not filled out the required fields for those sections.

This is done using form states.

Events: Registration info

Has similar validation. Choose Registration method, and exposed fields are required, using custom JS. There is no server-side mechanism for this.

Design principles

For background, the field appears to be required, showing with an asterisk.

Acceptance Criteria

• [ ] When trying to save a page with a non-normal operating status, an empty Details field triggers a validation error. On all content types:
  • [ ] VAMC
  • [ ] Vet Centers
  • [ ] CAPs
  • [ ] Outstations
  • [ ] VBA
  • [ ] NCA

We don't necessarily expect markup to change, as fix is likely to be in PHP or JS, so we did not list a11y review as an AC. If markup does change, A11y review becomes required.

[jilladams]

Per Laura / Michelle discussion: Editors seem to think it's required and only leave it blank for CAPs. Leaving it blank doesn't break FE. The blank field does pipe through to FE.

A good example of handling, per Daniel, may be the Registration Info field on Events.

[jilladams]

@omahane wlll take a look at the JS solution on Events to determine path forward. That's necessary before we can refine and point.