Insights & updates from our experts
Most organizations that use Xurrent also make use of UI extensions to add custom fields to the user interface for specific types of requests, tasks, configuration items, etc. When they get comfortable with this, they want to focus not merely on adding fields, but making it easier for users to fill out these fields.
For example, you may have prepared a UI extension that allows end users to order peripherals like an external hard disk or a monitor. You may want to initially keep the fields hidden in which the user can specify the storage capacity and the screen size. It would best if those fields become visible only when they are needed.

It is not so hard to define this logic in the JavaScript of a UI extension. Still, to make things a little easier for people who are not so comfortable with web development, we have prepared a set of useful UI extension examples. These examples can be found in the Xurrent Developer documentation. There, you can find code examples that you can incorporate in your UI extensions to optimize their user-friendliness.
So go ahead, see if some of these examples can be applied for your organization. It may help your end users and it will surely impress your colleagues.

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)














