.webp)
Blog
Insights & updates from our experts
.webp)
.webp)
The data entered on a request form or task form is often also important for performing follow-up tasks. For that reason, many organizations in Xurrent® use automation rules for copying those custom fields to the successor tasks. Until now, that had to be done field by field, which is a time-consuming and maintenance-unfriendly process, especially for organizations that use very large UI extensions.
It is now possible to copy all custom fields from one form to another form at once. The following screenshot shows an example of an automation rule passing all custom fields to all successor tasks.
As an illustration, an automation rule that would have the same results but where all fields must be copied one by one would look like this.
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
News
Partners
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
Service Management
Enterprise
Integrations
