.png)
Blog
Insights & updates from our experts
.webp)
.webp)
People who are colorblind had trouble distinguishing between the gray impact icon ‘Low’ and the red impact icon ‘Medium’. They had the same issue when Xurrent showed them with the gray impact icon ‘High’ and the red impact icon ‘Top’.
To make it easy for them to see the difference, the solid gray bars of the impact ‘Low’ and ‘High’, which signify a service degradation, are now hollow.
The solid red bars of the impact ‘Medium’ and ‘Top’, which indicate a service outage, have not changed.
Because a green hollow bar was used to indicate that there was no impact, this icon also had to change to avoid confusion. In the header bar, the ‘None’ impact icon has simply been removed.
In the Service Hierarchy Browser (SHB) the health indicator that is displayed when there are no open incidents has been replaced with a green dot.
Keep in mind that one bar is displayed for incidents that affect only 1 person; two bars indicate that multiple users are affected. The long names of the impact levels are:
- None – Service Not Degraded
- Low – Service Degraded for One User
- Medium – Service Down for One User
- High – Service Degraded for Several Users
- Top – Service Down for Several Users
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
