Source

Change, problem & release management — found from sitemap — Xurrent ITSM

Checked for Xurrent ITSM on 1 Nov 2026

Technical details

type: page
http status: 200
content hash: sha256:49284d121064bb740bafc816eadc5df09d34e57063b6f8ccc0930a4b1a6ddb7d
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Change starts as rfc request Report an error

“A change starts as a Request whose Category is RFC, Request for Change, and it is carried out by a Workflow”
Change record renamed workflow Report an error

“the Workflow record, which was renamed from Change in January 2022”
Workflow engine generalized Report an error

“the same engine now also drives non-ITIL processes such as HR onboarding, facilities, and finance, while change management remains one specific use of it”
Rfc API category value Report an error

“The API category value is rfc. RFCs carry an RFC Type field to subclassify the kind of change, and a Workflow field that links the request to the workflow implementing it.”
Workflow type subtypes Report an error

“Its Type field most commonly has the value Change, which customers subtype further, for example Application Change, Infrastructure Change, or Documentation Change.”
Change template rename Report an error

“Change Template Workflow Template”
Change manager rename Report an error

“Change Manager (on the record) Workflow Manager”
Change pending rename Report an error

“change_pending (request status) Workflow Pending”
Release management Report an error

“See Release for coordinating multiple related workflows, and Risk for risk assessment on changes.”
Workflow holds tasks approvals Report an error

“The Workflow is the container of Tasks, their ordering, and any automation that together implement the change.”