VACMS-18311: Limit Aging Content Email to Specific Users

[dsasser]

Description

Relates to #18311

Adds both a comprehensive whitelist (allow_delivery_only_to) , and a blacklist (restrict_delivery_to), to recipient delivery access checks in Aging Content's custom message delivery Job Type. The lists accept any number of user id's for which to restrict/allow.

Testing done

Tested using a combination of white and blacklisted users.

Screenshots

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

As a administrator

1. Visit /admin/config/workflow/eca/aging_content_expired_fwb/edit
2. Under 'Workflow options', check the 'Enabled' checkbox, and save the form
3. Visit /admin/config/workflow/eca/aging_content_expired_fwb/action/create_advancedqueue_job/edit
4. In the 'Payload', add these lines:

restrict_delivery_to:
  295

5. Save the form
6. Run cron
7. Go to /admin/config/system/queues

• Verify there is a job in the 'Queued' status

8. Disable the ECA workflow (reverse of step 2 to disable the checkbox). This prevents queuing a duplicate message.
9. Run cron
10. Go to /admin/config/system/queues

• Validate there is a job in the 'Failed' status with the message: Recipient is not on the allow list for message [xxx]

11. Visit /admin/config/workflow/eca/aging_content_expired_fwb/action/create_advancedqueue_job/edit
12. In the 'Payload', change the key 'restrict_delivery_to' to 'allow_delivery_only_to'.
13. Save the form
14. Perform step 2 (enable the workflow)
15. Run cron
16. Inverse step 2 (disable the workflow)
17. Visit /admin/config/workflow/eca/aging_content_expired_fwb/action/create_advancedqueue_job/edit

• Validate there is a job with the "success" status.

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

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

[jv-agile6]

Reviewed and approved