.webp)
Blog
Insights & updates from our experts
.webp)
.webp)
Last week’s release introduced the ability for a provider to stop the SLA clocks under certain conditions, using automation rules. This temporarily removes the accountability of a provider, for example when a workflow has to wait for an approval of the customer. This functionality can now also be enabled from the task templates.
A checkbox ‘Provider not accountable’ has been added to task templates, which – when enabled – stops the SLA clocks of the requests that are linked to the workflow of this task. The checkbox is available to workflow managers, account administrators and designers.
In the ‘Task’ view, it is indicated for which tasks the provider is made not accountable for SLA breaches.
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.
3 Mins
July 1, 2026
News
Partners
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
