Change Management
Lynx Change Management - Status Page
Publish approved changes as planned maintenance on the status page
lynx_change_management_status_page
· v19.0.1.1.0
· Standard
What this solves
Lynx Change Management - Status Page
Publishes an approved change request to the public status page as a planned maintenance, so customers read about the window in the place they already go to ask whether something is down.
Why a bridge and not a second public page
lynx_status_page already has the record (lynx.status.maintenance: a title, a window, the components affected, a state derived from the dates) and lynx_status_page_website already renders it. A separate public page inside change management would be a second surface to style, translate and keep in step, describing the same event in two voices.
Key Features
Publish / withdraw - one action each way, from the change request.
Stays in step - renaming the change or moving its window updates the published maintenance; cancelling the change withdraws it.
Services become components - a component carries the lynx.cmdb.service it stands for, and the published maintenance names the components behind the services the change affects.
Nothing is published by accident - a change is only announced when somebody asks for it, and only once it is approved.
Integrates With
lynx_change_management - the change requests and their services.
lynx_status_page - the page, the components and the maintenance record.
Depends on
Try Lynx Change Management - Status Page on your team.
Free trial, no credit card. Talk to sales when you're ready.