Blog

Managing 1000s of Relations

May 22, 2016

Carlyn Manly

1 Min Read

Click To Explore

Many of the organizations that use Xurrent have enormous infrastructures to manage. The numbers they deal with on a daily basis can be dazzling. In such environments it is critical that the service management application remains responsive despite the amount of data that is maintained in it.

To make it practical to manage records that may have thousands of relations with other records, a performance enhancement was recently implemented. This enhancement ensures that when such records are opened, only the first few of their relations get downloaded for display in the form.

The service instance in the above example is made up of over 2,000 configuration items. After opening this service instance, the user can browse through the related configuration items using the Next (>) button. To quickly jump to a specific CI, its label and/or name can be entered in the search box.

This new feature, which allows users to page through a record’s relations, is available in several places within the application (e.g. for the covered people of an SLA and the requests that are linked to a change). To ensure that this features does not become an unnecessary distraction, however, it only shows up when there are many related records.

Partners

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

Service Management

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