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.
An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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