Closed omahane closed 3 weeks ago
@ian-sears @TroyCMSSupport The facility redirect has been deployed. No other Veteran-facing work remains. This ticket can be closed by the Help Desk after informing the editor.
Flags removed. Page archived. Closing.
Intake
[x] What triggered this runbook? (Flag in CMS, Help desk ticket, Product team, VHA Digital Media) Trigger: Flag in CMS
[x] Link to associated JIRA help desk ticket (if applicable) Help desk ticket: VAHELP-7488
[x] Name of submitter (if applicable) Submitter: Stefen.Westerfield@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: https://prod.cms.va.gov/tampa-health-care/locations/winners-circle-va-clinic Facility API ID: vha_673QF
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:18135
CMS Engineer steps
(Redirects deploy daily except Friday at 10am ET, or by requesting OOB deploy (of the revproxy job to prod) in #vfs-platform-support. Coordinate the items below and canonical URL change after URL change ticket is merged, deployed, and verified in prod.)
Drupal Admin steps (CMS Engineer or Helpdesk)
Help desk will complete these steps or escalate to request help from CMS engineering.
Removed from source
, add a revision log that explains the change, with a link to github issue, and change moderation state to archive. (Note: any remaining health services, non-clinical services and events for the given facility will be archived automatically when these changes are saved.)CMS Help desk (wrap up)