Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
A new trigger option has been added for automation rules on configuration items (CIs). ‘On source update’ triggers when the Source field of a configuration item is updated.
This can be useful when using discovery tools that provision assets to Xurrent. Often these discovery tools have site specific attributes: an asset discovered in a site in Munich will get another attribute than an asset discovered in Berlin. When the integration with the discovery tool includes the site attribute in the source of the discovered CI in Xurrent, it becomes possible for an automation rule to link this CI to the correct Xurrent site.
Given our site-based SLA coverage, this enables dynamic coverages. When someone with a laptop moves from Munich to Berlin, for example, their laptop is covered by the SLA for the Berlin Desktop Services and the request is automatically assigned to the correct local team.
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