[EPIC] ECA Framework expansion to other types of actions

[FranECross]

Status

[2024-11-07] [Fran] The evaluation of other types of actions has been completed, and Michelle M/Fran have reviewed. Michelle created tickets. [2024-08-09] [Fran] The ticket to evaluate other types of actions is in the Ready pipeline. Other tickets will shake out and be linked to this epic.

Description

The ECA Framework was recently used to implement Aging Content Notifications. We want to explore using this framework for other types of actions.

The following are scenarios that will be explored in a Spike, which might spin off stories for actual implementation.

Scenarios for evaluation

• Moderation state as a trigger for a notification

  • example: when an editor saves content as "in review", a supervisor/approver is automatically notified by email
    • assume the recipient exists at a different level than the editor (not identical sections)
  • example: editor or supervisor/approver is notified when content has been stagnant (no moderation state change for x period)

• Outdated content iteration

  • example: VHA editors are reminded to update/review and validate certain content (such as a mental health number) with different cadence from other outdated content notifications

• Automating processes

  • flagged facility processes
    • example: new facility can be published once editor does x - when x is complete, node is auto published
  • forms processes
  • when new form seen following migration, CAIA is notified
  • content meeting certain criteria (i.e., time since creation) is auto archived
  • content is auto-archived or replaced on defined date/time
  • example: Vet Centers have spotlights they use to promote outreach activities. If the date of the event has passed, the spotlight could be auto-archived or automatically replaced by evergreen content which is not time sensitive

• User management

  • example: generate list of editors who have not accessed Drupal in x period of time and email it to leadership (or remove access)
  • example: editor who has completed training is automatically assigned role/permission

• Content delay notifications

  • example: when content build is delayed by x period of time, post Drupal banner
    • when delayed by y period, send an email to notify editors

• Publication of KB article or release notes node triggers notification on dashboard (or email to specific editor type)

Acceptance criteria

For each use case, indicate whether the framework is possible, a rough estimate of time/difficulty, and factors or dependencies which should be considered

[FranECross]

Associated tickets added as sub-issues.