Insights & updates from our experts
A new field for alternate names of software versions has been added to the configuration item form. Organizations that have used a discovery tool to populate their configuration management database (CMDB) with the software that they run on their PCs and servers will know that this causes an enormous number of configuration items to be generated for software versions from different products. Most of this software does not need to be tracked in the CMDB, however. That’s because their licenses do not need to be managed or it does not really help the specialists or service desk analysts when they initially try to get an idea of the server or PC for which an issue has been reported.
So instead of registering every discoverable piece of software in the CMDB, configuration managers have found that it is better to take the opposite approach. They let the discovery tool know which software versions they are interested in by registering them manually in the CMDB. The discovery tool then automatically links these software CIs with the machines on which they were discovered. But because a discovery tool may know a single software version by many different names, (e.g. due to different language editions or because of different patch levels that do not need to be tracked in the CMDB), it is important that these names can be registered in the CI record of each software version. For this reason, the Alternate names field has now been added to the Configuration Item form.

This field is only visible in configuration item records of which the product is of the software category. The field supports pasting multiple lines with alternative names.

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)














