Product Update

Xurrent ITSM - May 2026 Product Updates

Jacob Roscoe
May 31, 2026
2 Min Read

Table of contents

Downward-pointing chevron dropdown arrow icon in black.
Heading 2
Heading 3

This post is a living document, updated throughout the month as new product releases roll out. Each update listed here is released to our QA environment on the date shown and typically promoted to production the following week. Along the way, customers can review changes, share feedback, and help shape what ships next. Xurrent delivers product updates on a weekly cadence to keep enhancements moving continuously.

May 7, 2026

Specialist UI: Inline Rating Replaces Modal on Completed Requests

The rating prompt for completed requests now appears inline in specialist, matching the experience in self-service.

After clicking thumbs up or thumbs down, a short prompt appears above the note editor (encouraging for thumbs up, asking what could be improved for thumbs down).

Shows the inline feedback prompt appearing above the note editor after a thumbs up rating, with options to Post or Skip.

While rating, the editor is focused on public feedback: the Internal Note tab, email tabs, and time-spent row are hidden. Rich text formatting, inline images, and file attachments remain available.

To save a rating with feedback, users type a note and click "Post". To skip the comment, they click "Skip" (thumbs up) or "Cancel" (thumbs down), which clears the editor without saving. "Reopen" (thumbs down) still requires a note, since reopening a completed request is a meaningful change.

Shows the inline feedback prompt for a thumbs down rating, with Cancel, Reopen, and Post buttons, asking the user to describe how support could be improved.

Asset Management: CMDB Health Naming and Layout Refresh

The CMDB Health dashboard has been refreshed with clearer, more consistent naming as part of preparing the section for general availability.

The four KPI tiles and their section headers have been renamed: "Potential Duplicates" is now "Duplicate candidates", "Stale Records" is now "Check-in freshness", "Field Completeness" is now "Field population", and "Orphan CIs" is now "Relationship coverage". "Supporting Views" is now "Lifecycle & financial".

The "Configuration Items by status" tile (formerly "CI By Status") has moved from Check-in freshness into the new Lifecycle & Financial section, where it joins "Configuration Items by warranty status", "Configuration Item age distribution", and "Total Configuration Item value" as descriptions of the estate rather than its health.

Tile names now use sentence case with the full "Configuration Item(s)" instead of "CI(s)", and lowercase "by", as in "Field population by Configuration Item type".

REST API: People and Relationship Endpoints Accept Node IDs

The REST API now accepts node IDs (the base-64 strings returned by the GraphQL API) on the People endpoint and on relationship endpoints. If you pipe GraphQL results into REST calls, you no longer need to convert IDs first. This matches how every other record type already works.

Two cases were previously broken and have been fixed:

  • People endpoint. A shortcut for "give me the current user" treated any non-numeric value as a request for the caller. Because node IDs are base-64 strings starting with letters, node-ID lookups were silently returning the caller instead of the intended person. The shortcut is now limited to three explicit values: empty, 0, and "me" (which is now a supported alias). Any other ID flows through to a normal lookup.
  • Relationship endpoints (for example, attaching a calendar to a holiday, or linking a user to a configuration item). These take two IDs in the URL: one for the parent record and one for the related record. The parent ID was already handled correctly, but the related-record ID was being read as a plain integer, which silently turned every node ID into zero. Both IDs now accept node IDs and numeric IDs interchangeably.