Before
A patch coordinator manually copied the implementation plan, maintenance window, ownership, and other change details into a change record. They also searched for existing changes and repeatedly looked up and attached affected configuration items and services before handing the record to the change advisory board.
How it works
- Receive the approved remediation wave and search for an active change beginning with its planning key.
- Return the matching change when found; otherwise create a new change using the requested change model and supplied details.
- Attach the affected assets and services, capture any failed links, and return the change record for approval.
Workflow details
- Request intake: The flow receives an approved change request containing a planning key, change details, affected configuration items, and impacted services.
- Duplicate prevention: It searches for an active change whose title begins with the same planning key. If one exists, the flow returns its number and identifier instead of creating another record.
- Change creation: When no matching change is found, the workflow creates a change request using the requested change type and its corresponding model, while carrying over the supplied schedule, ownership, plans, priority, risk, and justification details.
- Scope attachment: The workflow links the affected configuration items and services to the new change, processing multiple entries concurrently and continuing while recording attachment failures.
- Review handoff: The result includes whether a change was created, the change number and identifier, and counts of successful or failed attachments; approval remains with the change advisory board. The provided website demonstration uses simulated integration responses.
What changed
Each remediation wave is checked against existing active changes automatically before any record is created. New changes are populated and scoped in the same workflow, while the board receives one identifiable change with attachment results and retains the approval decision.
Work removed
Searching for duplicate active changes, manually creating and populating change records, copying affected asset and service lists, creating individual scope attachments, and counting attachment failures.
Expected outcome
Each wave is expected to maintain one active change record and remove at least three recurring manual action types: duplicate checking, change creation, and scope-list copying and attachment.
