Version: 2025.11.26.2 1683
In these November 2025 release notes, you can read which new features and improvements are available in Maintenance Planning and which issues have been resolved.
Note: some functionalities depend on your licence and user permissions.
In brief
- Generate reports in the background: you can continue working while a report is being created. You can then find the report on the new Generated reports page.
- Performance and text: performance has been improved and text has been adjusted in various places.
- Object codes: object codes are now transferred correctly during a ZIP import from O-Prognose and when copying a building component.
- Permissions: users with the Viewer role no longer have access to the indexation options.
- Findings and prices: the condition score and markup factor are now displayed correctly.
New and changed
Generate reports on the reporting page
Report generation has been updated and expanded. Previously, reports were generated immediately using the Preview button. They are now generated in the background.
- Select a report, set the desired options and click the new Generate button.
- You can continue working in Maintenance Planning while the report is being generated.
- You will automatically receive a notification when the report is ready.
- You can find the report on the new Generated reports page. There, you can view or download it.
- This page also contains previously generated reports. You can download these again.
Improved performance
Due to changes in the application, Maintenance Planning now works faster.
Textual changes
Text has been adjusted in various places in the application.
Resolved issues
Incorrect object code during ZIP import
When you imported a ZIP file from O-Prognose, an incorrect object code was sometimes created. This happened when the original object code contained a hyphen (-).
This has been resolved. Object codes are now transferred correctly during the import. Does a code already exist? A sequence number is then added automatically (-01, -02, and so on). The related message only appears if the code is actually already in use.
Viewer had access to indexation options
In some situations, users with the Viewer role had access to the indexation settings on the System administration page. These options are intended for administrators only.
This has been resolved. Viewers no longer have access to the indexation options.
Condition score appeared to be editable when adding a finding
When you added a finding for which a condition score is calculated, it appeared as though you could manually adjust the condition score. The field looked editable, but a changed value was not saved. This caused confusion because you are not allowed to overwrite the condition score.
This has been resolved. The field can no longer be edited.
Object code was not used when copying a building component
When you entered a new object code yourself while copying a building component, this code was not used. Instead, a different code was created automatically, for example with an incrementing sequence number.
This has been resolved. The object code you enter yourself is now used. Does this code already exist? A unique sequence number is then added automatically (-1, -2, and so on) until an available code is found.
Markup factor displayed incorrectly in the price tooltip
The tooltip with the price calculation displayed the markup factor, even when it had been disabled for the activity. As a result, the explanation of the price calculation showed an incorrect value.
This has been resolved. A disabled markup factor is now correctly ignored everywhere in the price calculation and is no longer displayed in the tooltip.
More information
Do you have questions about this release? Please contact us.
We wish you every success with Maintenance Planning.