Blog

Transform incident management from reactive firefighting to a continuous improvement cycle with Zenduty and Xurrent's Virtuous Cycle approach—reducing disruptions and building IT resilience.

Exploring Generative AI's role in Xurrent's ITSM platform, including AI-powered virtual agents, request summaries, and automation builders that boost productivity across 90% of customers.

Struggling with IT support? These 7 service desk tips will change how you work — fast.

Discover why MSPs need to protect their business with modern ITSM solutions. Learn how Xurrent's platform helps reduce the 12% customer churn rate through AI automation, incident management, and customer satisfaction tracking.

We’ve added enhanced functionality to Xurrent with added capability building on the recent StatusCast platform acquisition.

The ‘Automation Rule Executions’ section is added to the Settings console, providing an overview of all rule executions.

Xurrent Auto-Translation is a new feature available to all customers, at no additional cost, enhancing collaboration, efficiency, and accuracy.

It is now possible to do a global search in Xurrent using automation rules.

Just by dragging lines to another position within the actions of automation rules, the order of the actions can now be changed at will.

Using GraphQL or Import API to synchronize products and configuration items discovered with external tools with Xurrent.

In a move to better facilitate smooth workflow automation across enterprises and easy integration with third-party systems, Xurrent has teamed up with leading iPaaS (Enterprise Integration Platform as a Service) vendor Workato to introduce the Xurrent Workflow Automator. The Xurrent Workflow Automator is now live.

Automation rules have just been made a bit more powerful for operations on arrays. So far, it was only possible to select the first (array[first]), last (array[last]), or a specific (array[3]) item in an array. It is now possible to access array items using variables (array[var]). Designers and administrators are likely to use this for […]

It is now possible to retrieve the full name of the country, when querying a person record with automation rules.

It is now possible to access the configuration items that are related to a product with automation rules.

Automation rules can now access the team of the template, when that template is related to a request.

The Support ID field on the person record is now accessible using automation rules.

It is now possible to copy all custom fields from one form to another form at once in Xurrent using automation rules.

Automation rules can now access the watches for a request. Watches can also be added, updated, and removed by API.

It is now possible to suppress the ‘Note Added’ notifications when adding a note via the API or via automation rules.

In a move to better facilitate smooth workflow automation across enterprises and easy integration with third-party systems, Xurrent has teamed up with leading iPaaS (Enterprise Integration Platform as a Service) vendor Workato to introduce the Xurrent Workflow Automator.

A new category for workflow tasks has been added to tasks and task templates: Automation tasks.

Request template automation rules can now be edited either on the request template or on the request itself.

The new ‘Copy NodeID’ action for account administrators copies the GraphQL NodeID of the selected record to the clipboard.

It is now possible to use automation rules to retrieve information from configuration items that are related to another configuration item.

It is now possible in Xurrent to build automation rules on person records.

Automation rules can now access calendars in Xurrent, such as work hours or support hours calendars, or any other calendar.

An enhancement of the in and not in operators of the automation rules have been made.

The new ‘On source update’ trigger option has been added for automation rules on configuration items (CIs).

It is now also possible to discern with an automation rule whether a reservation is one-time only, or recurring.

It is now possible to read the permissions and roles on a person record with automation rules.

The detect function in automation rules returns the first item in an array that matches the condition.

The Managing section on the person record can now be accessed with automation rules.

For generic automation rules, the module on which the rule is executed is now shown on the rule in View mode.

When an automation rule is executed in a different account, an account postfix is now shown in the automation trail.

It is now possible to check and update the value of the Analysis target field of a problem record using an automation rule.

The combination of Source and SourceID for automation rule imports do no longer have to be unique for different automation rule types.

It is now possible to access the creation date of a configuration item with automation rules.

From a workflow it is possible to start a project. It is now also possible for an automation rule to access the workflow that started the project.

Automation rules can now access the child service instances of a service instance.

It is now also possible to update customer representatives of a service level agreement using automation rules.

Several fields of project records that could previously not be accessed by automation rules are now available for automation.

Generic automation rules can be added to project tasks, for example to assign a project task to a person, team, or agile board.

It is now possible to create automation rules on workflows and on workflow templates at the workflow level.

It is now possible to request the contact information of an organization via an automation rule.

The ‘Automation Rules’ for requests, tasks and project tasks have been moved to the Actions menu on the toolbar.

It is now possible to use automation rules to update the members of a skill pool, and conversely to link a skill pool to a person.

It is now possible to create an automation rule that looks up the people of an organization, or the time zone of a site.

Automation rules can now be executed whenever the service instance is updated, or when a specific SI is related to a new request.

Organizations can now automatically apply a request template to a new or existing request using automation rules.

The ability to use automation rules to look up the service provider of the service of the service instance of a request has been added.