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.

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

Xurrent has acquired Zenduty to lead the future of IT Operations Management. Read the blog post to find out more.

Discover how ITxM unifies ITSM, ITOM, and ITIM to break the incident management doom loop. Learn how modern IT teams are evolving to serve digital enterprises and prevent costly downtime through unified service management.

For a person who is assigned to a request with status Workflow Pending, the toolbar actions which can change the status are now grayed out.

A new Maintenance window field has been added to the Service Instance form, in which a calendar can be selected.

It is now possible to print Gantt charts to paper or PDF. To do this, first open a workflow or project and press the Gantt Chart button.

It is now possible to set an approval task in the status ‘Waiting for Customer’ (WFC) to ask for clarification.

If a request has been some time in ‘Waiting for Customer’ without answer, a notification with an AI summary can now be sent.

It is now possible to save the applied filters and ordering on the change calendar in a personal view.

The approval feature involving delegates has been improved, so that essential approvers can never be bypassed.

When a calendar is selected on a recurring workflow or other record, the recurrences will only happen during calendar hours.

A 'Change Calendar without Conflicts' view has been added to the Change Calendar, showing none of the possibly conflicting tasks.

It is now possible to send emails from problems, releases, workflows, tasks, projects, project tasks and risks using the user interface.

It is now possible to create custom views on workflows, enabling organizations to expose their workflows to users through a UI extension.

It is now possible to create a rework loop directly in the Gantt chart of a workflow, repeating a part of the workflow until a task succeeds.

It is now possible to create an exception flow within a workflow, by defining tasks that are executed in case a previous task fails.

A new setting ‘Assign related requests and problems to workflow manager’ is added to the Workflow Template form.

Changes and change-related concepts in Xurrent are now renamed to workflows and workflow related concepts.

To prevent specialists from accidentally completing requests that have open tasks, a warning and a new filter have been added.

The start date and time is now included in the warning message when the assignee should not yet start to work on a task.

When people are looking at an agile board, they are now able to see which items are in the status 'Waiting for…' or 'Waiting for Customer'.

The dropdown fields for selecting a change template have been upgraded to suggest fields to make it easier to find the right template.

Many of the actions available in the Xurrent toolbar can now be used to update multiple records at the same time.

The Forward button in the Xurrent toolbar can now also be used to pass a request, problem or task to a different team.

After opening a task in Xurrent Self Service or in the Xurrent App it is now possible to review the Gantt chart of the task's project or change.

Organizations can now automatically include a link for starting a Microsoft Teams chat session in each Xurrent person record.

The minimum planned effort for the completion of a task that is part of a change or project has been reduced from one minute to zero.

The status of related service instances is now displayed when a task template, change template, task or change is opened in View mode.

Organizations that are using release records to group changes are now able to filter the views and reports for changes and tasks by release.

A few more date range filters have become available to create more specific views and reports of several record types.

A unique new collaboration feature makes it possible to include tasks in change workflows that automatically generate new requests.

When a specialist saves a record with a new note and a value in the Time spent field, the note gets linked to the time entry that Xurrent generates.

Going forward, Xurrent will prompt specialists to specify how much time they spent after they entered information in the Note field.

Two new filters have become available for the change views in the Records console and for the change reports in the Analytics console.

Xurrent no longer makes the Note field required for a specialist if the same specialist added the previous note less than an hour ago.

Xurrent's demo instances now include example data to show how organizations can use Xurrent to manage the security and privacy of their services.

Specialists are now also able to open the Change Calendar from the Actions menu after they opened a record in the Records console.

A system note now gets added whenever someone marks a request, problem or task as urgent so that it is easier to see who did this and when this was done.

To provide an even more complete overview of changes and projects, Xurrent now presents the current status of each task in the Gantt chart.

A set of time spent reports has become available that makes it easier to identify requests that specialists have spent a significant amount of time on.

Xurrent’s Service Navigator could already be opened from requests, problems, changes, releases, projects and SLA reports. Now it is also possible to open the Service Navigator from change tasks and project tasks.

Finished tasks now have their own separate view in the ‘My Inbox’ section of Xurrent Self Service and the Xurrent App.

Two more reports have been added to the 'Reports' section of the Analytics console for the change and project management processes.

To facilitate more precise resource planning, Xurrent now allows the planned duration and planned effort to be specified in hours and minutes.

A helpful Inbox feature has been added to help specialists distinguish between assignments that are assigned to them and assignments that still need to be assigned to a team member.

The report ‘Completed Changes by Completion Reason‘ has been added to the 'Reports' section of the Analytics console.

The source of a note is now displayed whenever it was automatically copied from another record. This should make it clear where the note came from.

The formatting bar of the Note fields now offers the ability to add references to other Xurrent records, such as requests, problems, changes and tasks.

The 'Member' filter has become available for the request and task views in the Records console and for the request and task reports in the Analytics console.

Xurrent’s Inbox console has undergone a major makeover. The new Inbox console offers a whole set of helpful usability features.

Project, change and release managers are now able to see the time that their colleagues spent on the on the work they coordinate.

The status option 'Being Created' has been added for change records. Change managers will see this status only briefly whenever they save a new change.

The order in which the requests that are linked to a change are presented within that change has improved. In the past, the requests would be sorted by their ID. Now they are sorted first by their status and then by their ID. This improved sorting also affects the sorting of: Requests within a problem […]

The ‘Attachments’ and ‘Notes’ sections of a change are no longer available to specialists, unless they have the Specialist or Auditor role of the account in which the change is registered. This ensures that, when someone added sensitive information to a change, this information can be seen only by specialists or auditors of the account […]

Automation rules can now be added directly to task templates.

Change managers are going to appreciate this usability improvement. When someone starts to register a new change and selects a change template, Xurrent is now going to remember this selection. The benefit is that the next time the change manager needs to create a change, the template is presented in the ‘Recent Selections’. This is […]

When you open a change or project in View mode and you click on a task within the small Gantt chart that is presented at the bottom of the screen, this task is presented in a popup over the change or project. If you have the access rights to edit this task, you can then […]

To ensure that change managers do not unintentionally affect a change template when they update a task template, they are now warned when this could happen.

Change managers have provided useful feedback that has been used to perfect the Gantt Chart interface they use to plan their changes.

Change managers can now plan their changes using a Gantt chart that offers of graphical representation of their implementation plans.

Xurrent's Change Calendar has been improved specifically to assist organizations that implement hundreds of changes each week.

The Xurrent Change Calendar is improved to ensure that large support organizations that manage hundreds of services are still able to make effective use of it.

A minor, but useful, enhancement has been made available for change managers. When you open a change in View mode, you will notice that the graphical workflow representation no longer shows the start of the implementation plan when the implementation has already progressed beyond this point. Instead, Xurrent now detects how far the implementation has […]

Sometimes it is important that a change does not get implemented before a certain date. Change managers can use the ‘Start no earlier than’ field of implementation tasks to specify the moment at which the implementation is allowed to start. To make sure that the team member to whom the task is assigned does not […]

The experience has become a little different for change managers when they edit a change. When they click on one of the change’s tasks, this task no longer opens inside the change form. Instead, it opens in its own screen. This makes for a more tidy experience. It also ensures that changes open noticeably more […]

The Service Hierarchy Browser (SHB) provides information that could be relevant for the request that you are working on. For example, it lists the child service instances and configuration items (CIs) that the service instance of the request relies on. It also lists the request templates that could be applicable to the request, as well […]

Xurrent now shows you a warning whenever you are working in the Inbox console on a request, problem or task, and someone else updates that same record.

Xurrent delivers real-time updates in your inbox. When a request, problem or task gets assigned to you, you will see it immediately in the Inbox console.

For a while now, it has been possible to assign an approval task to multiple approvers. When the minimum number of approvals have been given, or when one of the approvers rejects the task, the remaining approvers are no longer able to approve or reject it. This caused some confusion with some approvers. To explain […]

Most tasks are generated automatically from a task template and do not get updated by the change manager. The context for the work that someone is asked to perform is typically provided by the related change, requests and problems. These are all visible in the task as long as it is in View mode. As […]

End-users are now able to use their smartphones to submit and track their requests. Their managers are also able to approve changes. And all users can review the broadcast messages that are targeted at them. The best thing is that no one needs to do anything to get Xurrent Mobile. When a user receives an […]

More and more, organizations are using UI extensions to ask their users to define their requirements by filling out some required fields. That can dramatically improve the efficiency with which standard service requests get processed. When a standard service request triggers a workflow, the specialists will not work on the original requests, however. They will […]