Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
The status option ‘Being Created’ has been added for change records. Change managers will see this status only briefly whenever they save a new change.
As soon as all the tasks of a new change have been registered, the managers will see that the status automatically updates to ‘Registered’.
The advantage of this adjustment becomes clear when you consider a user saving a request after applying a request template that, in turn, is linked to a change template. If this change template is made up of a large number of task templates, it can take several seconds for all tasks to be created for the new change. Until that moment, the user would previously be waiting for the request to save. Now the request is saved immediately after its change is saved, allowing the user to continue working in Xurrent while the tasks get generated in the background.
An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations