Insights & updates from our experts
When importing records into Xurrent, the Source and SourceID fields are checked to see if a record already exists. This is also true when importing automation rules, which is done to transfer them between Xurrent environments, for example. When exporting automation rules, multiple export files are created; one for each automation rule type (request, request template, problem, etc.). When filling in the Source field, a unique SourceID must be chosen as well.
Until now, these SourceID values had to be unique across all the automation rule export files. If not, a Request Template automation rule may be overwritten by a Task Template automation rule, for example. To avoid such problems, the combination of Source and SourceID for automation rule imports do no longer have to be unique for different automation rule types.

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)














