Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
A helpful feature has been added that gives service desk analysts and specialists another way to quickly find a specific configuration item (CI).
For example, when an end user calls to report that the network printer PRT00127 is out of toner, this CI can now be found by entering only the number at the end of the CI’s label. The leading zeros should be ignored, so in this example the number that should be entered is ‘127’. The result is a list of CIs which labels end with ‘127’.
The same trick can be used when filtering a configuration items view.
And it can also be used to find CIs using Xurrent’s Search functionality.
Note that it is also still possible to use the name, label, site and location to quickly relate a CI to a request, task, service instance, etc.
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