Product Updates May 2026

In this update, we have gathered several improvements that make it easier to follow up, plan and quality-assure work in Workorder.

Among other things, there are updates for service agreements, inquiries, workplace notes, transport planning and time reports.

This time, the May release takes a small step into June, as we have another release planned later in the month.

The update will be released on Wednesday, June 3 at 15:00.
​
​

Those of you who work with service agreements now get a clearer overview that makes it easier to follow up on planned service and inspection visits.

In Service agreement overview, you can see all service agreements registered in the system. Among other things, you can see the latest completed visit, the next planned visit and whether there are any errors or deviations that need to be addressed.

For example, this could be a work order created from a service agreement that has been manually deleted, which may affect the continued planning of upcoming service visits.

The overview is available under Registers → Service agreements → Service agreement overview.

Read more in the article about service agreements.

For those of you who work with requests, it is now easier to identify, follow up on and refer to a specific request.

Each request now gets an automatically incremented number, in the same way as estimates already do. This makes it easier to keep track when several requests are handled at the same time.

A request is often the first step towards a work order. It can be processed further into an estimate, which can then become a work order. Or it can be converted directly from a request into a work order for planning and execution.

Existing requests have also been assigned sequential numbers, to give you a consistent history. The numbering is based on when the requests were created, with the oldest request having the lowest number.
​

It is now easier to see when there are notes linked to the workplace for a work order.

In the web interface, the work order dialog is shown under the Dialog tab. This can include both dialog linked to the work order and notes linked to the workplace.

Tabs that contain information are already marked with underlined tab text, for example for order rows, reports and costs. The same marking is now also shown when there are workplace notes, even if the work order itself has no dialog.

This makes it easier to discover important information about the workplace before or during the work.

We have improved the printout of time reports so that the summary now better reflects the content that is actually printed.

Empty rows are no longer shown in the summary when an employee has no time rows for a specific unit. We have also improved the selection before printing. Users without printable time rows are therefore no longer shown in the list.

To print a time report, at least one of the options Internal time or External time must now be selected.

For those of you who work with transport orders from Hyrma, the Date column has been updated to show more clearly which date applies in the transport planning.

When a transport is created, the transport date from Hyrma is shown. If the transport is later replanned in Workorder, the date shown will instead be the date the transport is planned for in Workorder.

This makes it easier to see the current planning when a transport needs to be carried out on a different date than the original transport date.

If you want to see the original transport date from Hyrma, you can add the Transport date column via Manage columns. You can also add the Planned column to show the planned date as a separate column.
​

In the previous release, we added support for filling in forms for all or selected installed units at a workplace.

We have now fixed an issue where a completed form could, in some cases, get the serial number from a previously selected unit.

Forms filled in per installed unit are now saved with the correct information.

We have fixed an issue in the Ahlsell EDI flow where delivery note numbers could, in some cases, be matched incorrectly.

The reason is that Ahlsell sometimes reuses delivery note numbers when their number series runs out. This means that a newly received EDI file can have the same delivery note number as an older file.

Workorder now takes this into account. If the same delivery note number already exists in the system, but the previous file is more than one year old, the new file is handled as a new delivery note.

This reduces the risk of incorrect matching and makes the handling of EDI files from Ahlsell more reliable.