Insights & updates from our experts
When someone is editing a record using the Xurrent App or Xurrent Self Service and then navigates away from this record without first saving the changes, a warning will now be displayed. The warning gives the user the opportunity to return to the record so that the updates can still be saved.

The warning pops up only when there are changes to save. If a user, for example, updates the Impact field of a request and subsequently sets it back to its original value, there are no changes to save. In such cases, or when no changes were made, the warning dialog will not be displayed when the user decides to go back or selects another option from the menu.

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.

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)











