Insights & updates from our experts
In Xurrent, organizations can specify how long records that could contain personally identifiable information (PII) should be retained. A retention period can be specified for such records, to ensure that they are moved automatically to their account’s archive, and from there to their account’s trash. Once a record has been trashed, it is automatically erased after 28 days. This life cycle support has now also been added to configuration items (CIs).

A record that is in its end state and is left unchanged for the specified archive retention period, gets moved to the Archive. Similarly, if a record is left unchanged for the trash retention period, it gets moved to the Trash. Archived records can be viewed by specialists in the ‘Archive’ section of the Settings console, trashed records can be viewed by administrators in the ‘Trash’ section of the Settings console. Once a record has been in the Trash for 28 days, it is irrevocably erased. A configuration item is in its end state when its status is ‘Archived’, ‘To be removed’, ‘Lost or stolen’, or ‘Removed’.
Note, that the ‘Archived’ status for CIs is different from this new life cycle action to archive configuration items; CIs with the status ‘Archived’ will not show up in the ‘Archived’ view if no retention period is set. As this may cause confusion, it is likely that the ‘Archived’ status will be phased out in the future.

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)














