.webp)
Blog
Insights & updates from our experts
.webp)
.webp)
An interesting feature has been added to the Service Hierarchy Browser (SHB). It has always been possible to click on a child service instances in the SHB to go down a level in the service hierarchy. Then the ability to reset the SHB was introduced, which essentially offered the ability to jump all the way back to the top of the service hierarchy. The new feature that has been added, allows specialists to move up a single level in the service hierarchy.
When a specialist opens a request, the SHB now presents a single left chevron ( < ) next to the service instance (SI) that is linked to the request. When the specialist clicks on it and the SI has only one parent that the specialist is allowed to see, then this parent becomes the new SI that is selected in the SHB.
The reason why this feature was not previously available is that SIs can have multiple parents. It took some time, but we believe we found an intuitive solution. In cases where there are multiple parents, the SHB simply offers up each of these parent SIs that the specialist has access to.
After selecting a parent, the specialist can either select one of its child SIs, or go up another step in the service hierarchy.
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.
3 Mins
July 1, 2026
News
Partners
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.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations
