Insights & updates from our experts
Request Templates, Known Errors & Recent Changes
The Service Hierarchy Browser (SHB) provides information that could be relevant for the request that you are working on. For example, it lists the child service instances and configuration items (CIs) that the service instance of the request relies on. It also lists the request templates that could be applicable to the request, as well as open requests, known errors and recently implemented changes for the service.
In the past, when the service instance of the request had many CIs, the request templates would no longer fit on the screen. And when many similar requests are still open, the known errors and recent changes would not be visible unless you scrolled down to the bottom of the SHB.
To ensure that all types of information are visible when the SHB opens, the number of items in each section is now restricted when the SHB opens. The lists of CIs, open requests and known errors are initially limited to 5 items. The request templates are limited to 10.
You can click on the more… link to see the rest of the items.
The most relevant items are immediately visible without requiring any action from the user. That’s because the request templates that have been applied the most get listed on top. Similarly, the open requests and known errors with the highest impact level show up first in their respective sections.

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)














