Insights & updates from our experts
Automation rules are used to automatically update Xurrent records when specific conditions have been met. They are triggered by events, such as the creation of a request or task, or an update of a specific record. With this release, a new trigger option has been added. Automation rules can now be executed whenever the service instance is updated, or when a specific SI is related to a new request, for example.

Of course there are many more applications for automation rules triggered by service instance updates, such as providing detailed information about a certain configuration item, or emailing a team when there is an urgent incident related to a business-essential service instance.

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)














