Blog
Insights & updates from our experts
.webp)
.webp)
.webp)
Up to now, most widgets that can be placed on the Xurrent Self Service homepage did not have built-in headings, but the ‘my_open_requests’ and ‘my_completed_requests’ widgets did. This inconsistency, in some cases leading to an orphaned header when there were no requests to display, has now been resolved: the built-in headings of the ‘my_open_requests’ and ‘my_completed_requests’ widgets have been removed.
This means that for a header to be displayed on these (and other) widgets, it has to be included in the snippet. This has the advantage that organizations can determine themselves what these headers should look like. An example of a snippet including the widgets ‘my_open_requests’ and ‘my_inbox’ including headers is given below.
Organizations that include widgets on their Xurrent Self Service homepage should verify if this change has affected their Self Service design.
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