Insights & updates from our experts
Custom views can be used to let users select a specific option in a custom field when registering an RFC, for example. In the case of configuration items (CIs), a custom view that is linked to a custom-suggest field of a UI extension is by default searchable on several CI fields, such as Label, Name and Location. This means that if the user types in a few characters that match any of the values of any of those CI fields in the custom field, only the relevant options are presented. Two changes have been made to how the custom views for configuration items work.
The first change makes it possible to define which of the CI fields are searchable. When a custom view is created and the Record type field is set to ‘Configuration Items’, the Search fields field appears. In it, the default searchable CI fields are listed. It is possible to define which of the configuration item fields are searched for a search string given by the user, by linking or unlinking columns.

The second enhancement makes it possible to also search in custom fields. The Voltage field in the example above is added to the APC SYBT4 Batteries through a UI extension (configured as ‘Searchable’ and ‘Filterable’). In this example, those batteries exist in 24 volt and 36 volt variants. When the user types in ‘24’ in a custom suggest field ‘Battery‘ during request creation, made available via a UI extension on the request template, only the 24 volt batteries are presented.


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.

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)














