Insights & updates from our experts
A minor usability improvement has been released that makes it possible for users to recognize the purpose of a field more quickly. Whenever another record can be looked up in a field, the search icon (the magnifying glass) is now visible inside the field.

This should avoid misunderstandings like the ones reported by a few organizations where specialists, who were new to Xurrent, would start to enter a problem description in the Problem field of a request. Which is actually completely logical for people who have not gone through an ITIL training in which the relationship between incident and problem management was explained.
The search icon in the Problem field of a request should now make it clear that this field can be used to look up an existing problem in order to relate it to the request. The search icon is displayed in the other search select fields as well so that their use is more intuitive.
While the development team was working on this improvement, they also slightly modernized the styling of the fields that are visible when a record is placed in Edit mode within the Xurrent Specialist Interface.

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.

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.















.webp)
.webp)


.webp)











