Insights & updates from our experts
A few useful features have been added to the Xurrent Change Calendar. These improvements were added to ensure that very large support organizations, which manage hundreds of services, are still able to make effective use of the Change Calendar.
The first enhancement is a scrollbar that allows the user to scroll down when there is not enough room to display all implementation tasks.

The second improvement is an additional view option. It is called ‘Changes for My Services’. When this option is selected, the user will see the implementation tasks that are going to affect one or more service instances and are linked to a change that is related to a service for which the user is the owner or the change manager.

The next feature that was added is a Search box above the list of services. Entering part of a service’s name filters this list down to the services which name includes the characters in the Search box. Since there are already quite a few Xurrent customers that support well over a hundred services, this makes it a lot easier to select or deselect a specific service.

The fourth new usability feature allows users to save their view options by simply adding a bookmark in their browser. Using this bookmark will then open the Change Calendar showing the implementation tasks of the changes that the user is interested in. That’s because the options that a user selects are now included in the URL.

Keep in mind that when a service is selected, the Change Calendar shows all implementation tasks that will affect a service instance and that are part of a change that is related to the selected service. In addition, the calendar shows any other tasks that could potentially conflict with these tasks.

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)














