Open TroyCMSSupport opened 3 weeks ago
Slack discussion on this: https://dsva.slack.com/archives/C0FQSS30V/p1725579266542309
Editor is aware and working on changes under Dublin to finish "closing" the facility.
According to VAST, we don't see the old API ID for this being closed. @TroyCMSSupport will reach out to the Editor to get the VAST change handled.
Intake
[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Help Desk Ticket
[x] Link to associated JIRA help desk ticket (if applicable) Help desk ticket: Helpdesk link
[x] Name of submitter (if applicable) Submitter: Megan.Kon@va.gov and Frank.Jordan2@va.gov
[x] If the submitter is an editor, send them a link to the KB article: How to archive a closed facility
[x] Link to facility in production: Facility CMS link: Facility link Facility API ID: vha_557GE
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: