VACMS-14699: Adding a Entity Field Fetch fields for VBA Centralized content

[omahane]

Description

Relates to #14699

Testing done

Manually

Screenshots

node:view

node:edit

QA steps

Reviewing node:view of a VBA facility

• As an admin, visit to a VBA facility in node:view
• Confirm that the following fields are being fetched:
  • Benefit office overview
  • Benefits hotline
  • Benefit office hours may vary
  • National spotlight 1
  • National spotlight 2
  • National spotlight 3
  • Can't find benefits
  • Get updates from VBA
• Confirm that each fetched field is in a grey box
• Confirm that each fetched field has a tooltip that pops up when hovering over the question mark

Reviewing node:edit of a VBA facility

• As an admin, edit [a VBA facility]https://pr15528-0squmrsgqim6fn8sjpgkwzrlslxcq25u.ci.cms.va.gov/node/61682/edit)
• Confirm that the following fields are being fetched:
  • Benefit office overview
  • Benefits hotline
  • Benefit office hours may vary
  • National spotlight 1
  • National spotlight 2
  • National spotlight 3
  • Can't find benefits
  • Get updates from VBA
• Confirm that each fetched field is in a grey box
• Confirm that each fetched field has a tooltip that pops up when hovering over the question mark
• Make a change to the facility
• Save
• Confirm that the fetched fields and change you made are showing on node:view

Editing VBA Centralized Content

• As an editor, edit the National VA benefit office content
• Make a change to the content in the "Rich text - char limit 1000" paragraph under the "Benefit office overview" Centralized content descriptor
• Save
• Visit to a VBA facility in node:view
• Confirm that your change is reflected in the "Benefit office overview" field

Select Team for PR review

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

[swirtSJW]

One set of suggested changes to make the machine name more friendly and meaningful for front end.

[swirtSJW]

This placement seems odd putting the centralized content inside the facility data section

Because it is not facility data and makes it look like it is coming from elsewhere.

[swirtSJW]

Is it intentional that we are only showing the last updated date on once of the CC fields but not the other?

The date it going to be the same for all of them.. but it shows the source of each segment of the data.

[swirtSJW]

Strikes me odd that these are rendering as separate link title and urls. It is going to be based on the default view mode for that paragraph.... which might not have had any attention when it was built.

I think it is unrelated to this ticket. Just noting it is odd.

[omahane]

This placement seems odd putting the centralized content inside the facility data section

Because it is not facility data and makes it look like it is coming from elsewhere.

I was trying to follow the layout from the FE, which sandwiches this number right after the main number and before the hours for editor clarity, but if this is confusing, I could put it elsewhere. After?

[omahane]

Is it intentional that we are only showing the last updated date on once of the CC fields but not the other?
The date it going to be the same for all of them.. but it shows the source of each segment of the data.

This was unintentional. @davidmpickett I think I should include the updated date. What do you think?

[davidmpickett]

Is it intentional that we are only showing the last updated date on once of the CC fields but not the other?
The date it going to be the same for all of them.. but it shows the source of each segment of the data.

This was unintentional. @davidmpickett I think I should include the updated date. What do you think?

I agree so heartily that I fleshed out a whole ticket about how I think this should be the default pattern: #4055

[swirtSJW]

I agree so heartily that I fleshed out a whole ticket about how I think this should be the default pattern: #4055

It is all about ticking all the boxes 😀

[swirtSJW]

Looks awesome. Nice work and thanks for sticking it out through all the changes.

[swirtSJW]