Insights & updates from our experts
When an organization has set up a Xurrent® account that is used only as an integration point for one of its external providers, it is important to know how requests are identified in the ticketing system of the provider. For this, the Supplier and Supplier request ID fields can be used. A few changes have been made to the way that these fields are handled within Xurrent.
Most notably, this information is now stored per account, and no longer per request. This means that every account that is involved in the creation and resolution of a request can now maintain the supplier and request identification for that supplier independently. This also means that this information is no longer automatically overwritten whenever a request was passed to another, trusted account. The values of the Supplier and Supplier request ID fields are now visible to everyone who can view the request.

Exports of requests only contain the supplier and supplier request IDs that are defined within the account from where the export is created.

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)














