Insights & updates from our experts
When a specialist navigates to the ‘Automation Rules’ section of the Settings console, all generic automation rules are listed by module. This makes it easy to see which rules are executed on request templates, which on task templates etc. For MSPs, that are sometimes tasked with the verification of many automation rules sent as URLs by their customers, it can be a bit cumbersome to find out on which module the automation rule should be executed. They would have to see that in the audit trail. For this reason, for generic automation rules, the module on which the rule is executed is now shown on the rule in View mode.


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)












