Insights & updates from our experts
Since the release of the enhancement that made it possible to add people to the watchlist of a request, while also being able to see who is watching that request, the use of the Watchlist functionality has grown rapidly.
So far, it has only been possible to manually add people to watches. In many cases, the need to have a specific person following the updates around a request arises spontaneously. In other cases, though, it can be helpful to add someone to a watch from the start. This can be the case for top level incidents, for example. In such a case, or any other case where a specific set of rules can be defined for involving a specific person, it can be helpful to be able to add them automatically.
Automation rules can now access the watches for a request, as illustrated by the following example:

Watches can also be added, updated, and removed by API.

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)














