VACMS-14816 Add Vet Center outdated content email (#15232)

* VACMS-14816 Clarify name of notification logger.

* VACMS-14816 CS cleanup of OutdatedContentNotification.

* VACMS-14816 Add Vet Center email content to template.

* VACMS-14816 Align method names with what they do.

* VACMS-14816 Make queue functions more DRY.

* VACMS-14816 Cleaning up doc blocks.

* VACMS-14816 Prepare for releasing cron run.

* VACMS-14816 Make OutdatedContent more ready to support other products.

* VAMC-14816 Add ability to test with specific users.

* VACMS-14816 Add support for different email subjects.

* VACMS-14816 Update vet center outdated content email.

* VACMS-14848 Add documention to module and update existing docs.

* VAMC-14816 Move preprocess to message fields.

* VACMS-14816 Update documentation to included editing the section term.

* VACMS-14816 Remove blocked users if they are called explicitly.

* VACMS-14816 Update VAMC email to use message content template and scalable.

* VACMS-14816 Fix broken link in vet center email.

* VACMS-14816 Add caveat notes to documentation.

* VACMS-14816 Releasing the task to run on cron.

* VACMS-14816 Remove image height to fix display on mobile.

* VACMS-14816 Minor template tweaks to fix mobile.

* VACMS-14816 Update KB url in vet center template.

Author: swirtSJW

READMES/cms-editor-notifications.md

@@ -2,21 +2,24 @@
 
    1. CMS Helpdesk
      Used to notify an editor(s) directly via email.
-   2. [Site Alert](#site-alert)
-   3. CMS Notification System (non-existent at this time)
+   2. [Sitewide Alert](#sitewide-alert)
+   3. [CMS Notification System](https://github.com/department-of-veterans-affairs/va.gov-cms/tree/main/docroot/modules/custom/va_gov_notifications/README.md)
 
 
 ## Sitewide Alert
 
-Sitewide Alerts (formerly Site Alerts) appear onscreen for ALL CMS users in real time.  They do not require
-a page reload.  They are refreshed on a 15 second AJAX interval. This leverages the Drupal [Sitewide Alert](https://www.drupal.org/project/sitewide_alert) module.
+Sitewide Alerts (formerly Site Alerts) appear onscreen for ALL CMS users in real
+time.  They do not require a page reload.  They are refreshed on a 15 second
+AJAX interval. This leverages the Drupal [Sitewide Alert](https://www.drupal.org/project/sitewide_alert) module.  These only show in the CMS.  They do not ever appear on VA.gov.
 
 Sitewide alerts are managed in two places:
 
 - [/admin/config/sitewide_alerts](https://prod.cms.va.gov/admin/config/sitewide_alerts) for global settings
 - [/admin/content/sitewide_alert](https://prod.cms.va.gov/admin/content/sitewide_alert) for individual alerts
 
-These can be added by humans but are also added and removed by our [Build-Release-Deploy System](devops/deploy-process.md).
+These can be added/edited by humans but are also added and removed by our [Build-Release-Deploy System](devops/deploy-process.md).
+
+CMS Helpdesk has guidance on when and how to use them.
 
 ----
 

READMES/drush.md

@@ -36,7 +36,5 @@ See [MetricsCommands.php](../docroot/modules/custom/va_gov_backend/src/Commands/
 
 ### Outdated Content
 See
-[OutdatedContent.php](..docroot/modules/custom/va_gov_notifications/src/Service/OutdatedContent.php
-).
-- `drush php-eval "print_r(\Drupal::service('va_gov_notifications.outdated_content')->checkForOutdatedVamcContent());"` -- Check for outdated VAMC content and queue notifications for any found.
-- `drush php-eval "print_r(\Drupal::service('va_gov_notifications.outdated_content')->checkForOutdatedVetCenterContent());"` -- Check for outdated Vet Center content and queue notifications for any found.
+[CMS Notification System](https://github.com/department-of-veterans-affairs/va.gov-cms/tree/main/docroot/modules/custom/va_gov_notifications/README.md) for commands to test or
+execute the various outdated content sends.

config/sync/core.entity_form_display.message.vamc_outdated_content.default.yml

@@ -3,7 +3,9 @@ langcode: en
 status: true
 dependencies:
   config:
+    - field.field.message.vamc_outdated_content.field_editor_username
     - field.field.message.vamc_outdated_content.field_subject
+    - field.field.message.vamc_outdated_content.field_webhost
     - message.template.vamc_outdated_content
 id: message.vamc_outdated_content.default
 targetEntityType: message
@@ -12,13 +14,13 @@ mode: default
 content:
   created:
     type: datetime_timestamp
-    weight: 10
+    weight: 1
     region: content
     settings: {  }
     third_party_settings: {  }
   field_subject:
     type: string_textfield
-    weight: 11
+    weight: 2
     region: content
     settings:
       size: 60
@@ -27,7 +29,7 @@ content:
     field_name: field_subject
   uid:
     type: entity_reference_autocomplete
-    weight: 5
+    weight: 0
     region: content
     settings:
       match_operator: CONTAINS
@@ -38,3 +40,4 @@ content:
     '#group': advanced
 hidden:
   field_editor_username: true
+  field_webhost: true

config/sync/core.entity_form_display.message.vet_center_outdated_content.default.yml

@@ -3,7 +3,9 @@ langcode: en
 status: true
 dependencies:
   config:
+    - field.field.message.vet_center_outdated_content.field_editor_username
     - field.field.message.vet_center_outdated_content.field_subject
+    - field.field.message.vet_center_outdated_content.field_webhost
     - message.template.vet_center_outdated_content
 id: message.vet_center_outdated_content.default
 targetEntityType: message
@@ -12,13 +14,13 @@ mode: default
 content:
   created:
     type: datetime_timestamp
-    weight: 10
+    weight: 2
     region: content
     settings: {  }
     third_party_settings: {  }
   field_subject:
     type: string_textfield
-    weight: 11
+    weight: 1
     region: content
     settings:
       size: 60
@@ -27,7 +29,7 @@ content:
     field_name: field_subject
   uid:
     type: entity_reference_autocomplete
-    weight: 5
+    weight: 0
     region: content
     settings:
       match_operator: CONTAINS
@@ -38,3 +40,4 @@ content:
     '#group': advanced
 hidden:
   field_editor_username: true
+  field_webhost: true

config/sync/core.entity_view_display.message.vamc_outdated_content.default.yml

@@ -5,6 +5,7 @@ dependencies:
   config:
     - field.field.message.vamc_outdated_content.field_editor_username
     - field.field.message.vamc_outdated_content.field_subject
+    - field.field.message.vamc_outdated_content.field_webhost
     - message.template.vamc_outdated_content
   module:
     - user
@@ -19,15 +20,21 @@ content:
     settings:
       link_to_entity: false
     third_party_settings: {  }
-    weight: 1
+    weight: 0
     region: content
   field_subject:
     type: string
     label: above
     settings:
       link_to_entity: false
     third_party_settings: {  }
+    weight: 1
+    region: content
+  partial_0:
+    settings: {  }
+    third_party_settings: {  }
     weight: 2
     region: content
 hidden:
+  field_webhost: true
   search_api_excerpt: true

config/sync/core.entity_view_display.message.vamc_outdated_content.mail_body.yml

@@ -6,6 +6,7 @@ dependencies:
     - core.entity_view_mode.message.mail_body
     - field.field.message.vamc_outdated_content.field_editor_username
     - field.field.message.vamc_outdated_content.field_subject
+    - field.field.message.vamc_outdated_content.field_webhost
     - message.template.vamc_outdated_content
   module:
     - layout_builder
@@ -19,11 +20,16 @@ targetEntityType: message
 bundle: vamc_outdated_content
 mode: mail_body
 content:
+  partial_0:
+    settings: {  }
+    third_party_settings: {  }
+    weight: 0
+    region: content
   partial_1:
     weight: 0
     region: content
 hidden:
   field_editor_username: true
   field_subject: true
-  partial_0: true
+  field_webhost: true
   search_api_excerpt: true

config/sync/core.entity_view_display.message.vamc_outdated_content.mail_subject.yml

@@ -6,6 +6,7 @@ dependencies:
     - core.entity_view_mode.message.mail_subject
     - field.field.message.vamc_outdated_content.field_editor_username
     - field.field.message.vamc_outdated_content.field_subject
+    - field.field.message.vamc_outdated_content.field_webhost
     - message.template.vamc_outdated_content
   module:
     - layout_builder
@@ -27,10 +28,9 @@ content:
     third_party_settings: {  }
     weight: 0
     region: content
-  partial_0:
-    weight: 0
-    region: content
 hidden:
   field_editor_username: true
+  field_webhost: true
+  partial_0: true
   partial_1: true
   search_api_excerpt: true

config/sync/core.entity_view_display.message.vet_center_outdated_content.default.yml

@@ -5,6 +5,7 @@ dependencies:
   config:
     - field.field.message.vet_center_outdated_content.field_editor_username
     - field.field.message.vet_center_outdated_content.field_subject
+    - field.field.message.vet_center_outdated_content.field_webhost
     - message.template.vet_center_outdated_content
   module:
     - user
@@ -19,14 +20,27 @@ content:
     settings:
       link_to_entity: false
     third_party_settings: {  }
-    weight: 1
+    weight: 0
     region: content
   field_subject:
     type: string
     label: above
     settings:
       link_to_entity: false
     third_party_settings: {  }
+    weight: 1
+    region: content
+  field_webhost:
+    type: string
+    label: above
+    settings:
+      link_to_entity: false
+    third_party_settings: {  }
+    weight: 3
+    region: content
+  partial_0:
+    settings: {  }
+    third_party_settings: {  }
     weight: 2
     region: content
 hidden:

config/sync/core.entity_view_display.message.vet_center_outdated_content.mail_body.yml

@@ -6,6 +6,7 @@ dependencies:
     - core.entity_view_mode.message.mail_body
     - field.field.message.vet_center_outdated_content.field_editor_username
     - field.field.message.vet_center_outdated_content.field_subject
+    - field.field.message.vet_center_outdated_content.field_webhost
     - message.template.vet_center_outdated_content
   module:
     - layout_builder
@@ -19,11 +20,16 @@ targetEntityType: message
 bundle: vet_center_outdated_content
 mode: mail_body
 content:
+  partial_0:
+    settings: {  }
+    third_party_settings: {  }
+    weight: 0
+    region: content
   partial_1:
     weight: 0
     region: content
 hidden:
   field_editor_username: true
   field_subject: true
-  partial_0: true
+  field_webhost: true
   search_api_excerpt: true

config/sync/core.entity_view_display.message.vet_center_outdated_content.mail_subject.yml

@@ -6,6 +6,7 @@ dependencies:
     - core.entity_view_mode.message.mail_subject
     - field.field.message.vet_center_outdated_content.field_editor_username
     - field.field.message.vet_center_outdated_content.field_subject
+    - field.field.message.vet_center_outdated_content.field_webhost
     - message.template.vet_center_outdated_content
   module:
     - layout_builder
@@ -27,10 +28,9 @@ content:
     third_party_settings: {  }
     weight: 0
     region: content
-  partial_0:
-    weight: 0
-    region: content
 hidden:
   field_editor_username: true
+  field_webhost: true
+  partial_0: true
   partial_1: true
   search_api_excerpt: true

config/sync/field.field.message.vamc_outdated_content.field_webhost.yml

@@ -0,0 +1,24 @@
+uuid: d38436f4-13bf-4a21-9944-0f2cc88aa5ce
+langcode: en
+status: true
+dependencies:
+  config:
+    - field.storage.message.field_webhost
+    - message.template.vamc_outdated_content
+  module:
+    - tmgmt_content
+third_party_settings:
+  tmgmt_content:
+    excluded: false
+id: message.vamc_outdated_content.field_webhost
+field_name: field_webhost
+entity_type: message
+bundle: vamc_outdated_content
+label: webhost
+description: ''
+required: false
+translatable: true
+default_value: {  }
+default_value_callback: ''
+settings: {  }
+field_type: string

config/sync/field.field.message.vet_center_outdated_content.field_webhost.yml

@@ -0,0 +1,19 @@
+uuid: 4d8fac85-d28e-4d18-aafa-c7f7f5965b97
+langcode: en
+status: true
+dependencies:
+  config:
+    - field.storage.message.field_webhost
+    - message.template.vet_center_outdated_content
+id: message.vet_center_outdated_content.field_webhost
+field_name: field_webhost
+entity_type: message
+bundle: vet_center_outdated_content
+label: webhost
+description: ''
+required: false
+translatable: false
+default_value: {  }
+default_value_callback: ''
+settings: {  }
+field_type: string

config/sync/field.storage.message.field_webhost.yml

@@ -0,0 +1,21 @@
+uuid: b3523b22-1aa3-4a36-b739-7c1a8e725d23
+langcode: en
+status: true
+dependencies:
+  module:
+    - message
+id: message.field_webhost
+field_name: field_webhost
+entity_type: message
+type: string
+settings:
+  max_length: 255
+  case_sensitive: false
+  is_ascii: false
+module: core
+locked: false
+cardinality: 1
+translatable: true
+indexes: {  }
+persist_with_no_fields: false
+custom_storage: false

config/sync/language/en/message.template.vamc_outdated_content.yml

@@ -0,0 +1,4 @@
+text:
+  -
+    value: "<p>VA Directive 6102 requires that VA content be reviewed yearly to ensure information is still relevant. Outdated content will need to be updated or removed to be compliant.&nbsp;<a href=\"https://prod.cms.va.gov/help/va-directive-6102\" target=\"_blank\">Learn more about VA Directive 6102.</a></p>\r\n\r\n<hr />\r\n<p>To assist with getting your content 6102 compliant within the next year, we are sending you this monthly reminder to view your outdated content report. To view this report, log in to the Drupal CMS or click “Review” below to go directly to the outdated content tool.</p>\r\n\r\n<p>For more information, you can read this <a href=\"https://prod.cms.va.gov/help/cms-basics/outdated-content-audit-tool\">Knowledge Base article on using the outdated content tool</a> to manage compliance.</p>\r\n\r\n<p>By reviewing an average of at least 25 pieces of content per month, your site will become compliant with VA Directive 6102 within the next year. Continuing to review your content at this rate will also help to ensure that you maintain compliance going forward without feeling overwhelmed.</p>\r\n"
+    format: rich_text

config/sync/language/en/message.template.vet_center_outdated_content.yml

@@ -0,0 +1,4 @@
+text:
+  -
+    value: "<p>VA Directive 6102 requires that VA content is reviewed yearly to ensure information is still relevant. RCS recommends a minimum quarterly review as a best practice. All content will need to be reviewed, and outdated content will need to be edited to remain compliant with VA Directive 6102.&nbsp;<a href=\"https://prod.cms.va.gov/help/va-directive-6102\">Learn more about VA Directive 6102.</a></p>\r\n\r\n<hr />\r\n<p>To assist with getting your content compliant, we are sending you this monthly reminder to log into Drupal, review and update your website content, and attest that your content is up-to-date.</p>\r\n\r\n<p>Reviewing your website top to bottom at least quarterly will help you to maintain updated and accurate location and service information and keep the website compliant with VA Directive 6102. For more information, you can read this <a href=\"https://prod.cms.va.gov/help/vet-centers/vet-center-content-review\">Knowledge Base article</a>&nbsp;for tips and best practices to manage compliance.</p>\r\n\r\n<p>Need help?</p>\r\n\r\n<ul>\r\n\t<li>If you are a Vet Center Director or Outreach Specialist who needs assistance accessing Drupal CMS, please email the CMS Support Team at&nbsp;<a href=\"mailto:[email protected]\">[email protected]</a>.</li>\r\n\t<li>If you want to refresh your skills, need ideas, or have questions about creating content for your webpages, you can find How to Guides and Training videos in the&nbsp;<a href=\"https://prod.cms.va.gov/help/vet-centers\">Drupal CMS Knowledge Base</a>&nbsp;or drop in during office hours.</li>\r\n\t<li>If you received this email and no longer have a role at a Vet Center, please inform us by emailing the CMS Support Team at&nbsp;<a href=\"mailto:[email protected]\">[email protected]</a>.</li>\r\n</ul>\r\n\r\n<p dir=\"auto\">Please note that before the end of the calendar year a formal suspense will be sent to ensure 100 percent compliance. We encourage you to make use of the resources and tools available before then to ensure your success and the success of information delivery on your page!</p>\r\n"
+    format: rich_text

config/sync/message.template.vamc_outdated_content.yml

@@ -1,11 +1,16 @@
 uuid: 69ae3597-f3f0-4ed5-ad51-42c608ba54d2
 langcode: en
 status: true
-dependencies: {  }
+dependencies:
+  config:
+    - filter.format.rich_text
 template: vamc_outdated_content
 label: 'VAMC Outdated Content'
 description: 'Email for VAMC section members, notifying them of outdated content. '
-text: {  }
+text:
+  -
+    value: "<p>VA Directive 6102 requires that VA content be reviewed yearly to ensure information is still relevant. Outdated content will need to be updated or removed to be compliant.&nbsp;<a href=\"https://prod.cms.va.gov/help/va-directive-6102\" target=\"_blank\">Learn more about VA Directive 6102.</a></p>\r\n\r\n<hr />\r\n<p>To assist with getting your content 6102 compliant within the next year, we are sending you this monthly reminder to view your outdated content report. To view this report, log in to the Drupal CMS or click “Review” below to go directly to the outdated content tool.</p>\r\n\r\n<p>For more information, you can read this <a href=\"https://prod.cms.va.gov/help/cms-basics/outdated-content-audit-tool\">Knowledge Base article on using the outdated content tool</a> to manage compliance.</p>\r\n\r\n<p>By reviewing an average of at least 25 pieces of content per month, your site will become compliant with VA Directive 6102 within the next year. Continuing to review your content at this rate will also help to ensure that you maintain compliance going forward without feeling overwhelmed.</p>\r\n"
+    format: rich_text
 settings:
   'token options':
     clear: false

config/sync/message.template.vet_center_outdated_content.yml

@@ -1,11 +1,16 @@
 uuid: 2d03776a-25fb-4a0c-a447-52cd5d99e430
 langcode: en
 status: true
-dependencies: {  }
+dependencies:
+  config:
+    - filter.format.rich_text
 template: vet_center_outdated_content
 label: 'Vet Center Outdated Content'
 description: 'Email for Vet Center section members, notifying them of outdated content. '
-text: {  }
+text:
+  -
+    value: "<p>VA Directive 6102 requires that VA content is reviewed yearly to ensure information is still relevant. RCS recommends a minimum quarterly review as a best practice. All content will need to be reviewed, and outdated content will need to be edited to remain compliant with VA Directive 6102.&nbsp;<a href=\"https://prod.cms.va.gov/help/va-directive-6102\">Learn more about VA Directive 6102.</a></p>\r\n\r\n<hr />\r\n<p>To assist with getting your content compliant, we are sending you this monthly reminder to log into Drupal, review and update your website content, and attest that your content is up-to-date.</p>\r\n\r\n<p>Reviewing your website top to bottom at least quarterly will help you to maintain updated and accurate location and service information and keep the website compliant with VA Directive 6102. For more information, you can read this <a href=\"https://prod.cms.va.gov/help/vet-centers/vet-center-content-review\">Knowledge Base article</a>&nbsp;for tips and best practices to manage compliance.</p>\r\n\r\n<p>Need help?</p>\r\n\r\n<ul>\r\n\t<li>If you are a Vet Center Director or Outreach Specialist who needs assistance accessing Drupal CMS, please email the CMS Support Team at&nbsp;<a href=\"mailto:[email protected]\">[email protected]</a>.</li>\r\n\t<li>If you want to refresh your skills, need ideas, or have questions about creating content for your webpages, you can find How to Guides and Training videos in the&nbsp;<a href=\"https://prod.cms.va.gov/help/vet-centers\">Drupal CMS Knowledge Base</a>&nbsp;or drop in during office hours.</li>\r\n\t<li>If you received this email and no longer have a role at a Vet Center, please inform us by emailing the CMS Support Team at&nbsp;<a href=\"mailto:[email protected]\">[email protected]</a>.</li>\r\n</ul>\r\n\r\n<p dir=\"auto\">Please note that before the end of the calendar year a formal suspense will be sent to ensure 100 percent compliance. We encourage you to make use of the resources and tools available before then to ensure your success and the success of information delivery on your page!</p>\r\n"
+    format: rich_text
 settings:
   'token options':
     clear: false