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.


A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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)














