Open TroyCMSSupport opened 3 days ago
@TroyCMSSupport I'm changing this to BOLO and removing the "Awaiting Redirect" until it actually comes off the Facilities API.
We should confirm with the editor that they have contacted VAST to have this closed.
Intake
[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Helpdesk Ticket
[x] Link to associated JIRA help desk ticket (if applicable) Help desk ticket: https://va-gov.atlassian.net/browse/VAHELP-7627
[x] Name of submitter (if applicable) Submitter: Stephen Westerfield
[v] If the submitter is an editor, send them a link to the KB article: How to archive a closed facility
[ ] Link to facility in production: Facility CMS link: Facility Link Facility API ID: vha_673QC
Acceptance criteria
VAMC facility closure
CMS Help desk steps
Note: If the help desk is waiting on information from the facility staff or editor, add the "Awaiting editor" flag to the facility with a log message that includes a link to this ticket. Remove the flag when the ticket is ready to be worked by the Facilities team. Be sure to preserve the current moderation state of the node when adding or removing the flag.
[@TODO: Update email template]
Email template
``` SUBJECT: