Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
In October 2017 a new version of Xurrent Self Service was released. Since then, several enhancements have been added to that version of Self Service, like the Watchlist, the Notification Center and the Refine Search option.
To stop having to support two separate Self Service versions, classic Self Service will be switched off completely on June 01, 2019 (update: this has been postponed until August 01, 2019 to give customers a little more time).
Existing Xurrent customers that are still using classic Self Service can easily switch to the regular Xurrent Self Service interface. Their Xurrent administrators can do this by going to the Settings console, opening the ‘Self Service Settings’ section and de-selecting the option ‘Use classic Self Service’.
Next, they can go to the ‘Self Service Design’ section to make their Self Service portal look good for their employees. Be sure to do this first in QA before switching to to the regular Xurrent Self Service interface in production.
An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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