Share
 
 

Release Notes in version 2026.0

This document lists product fixes which have been made in InfoWorks WS Pro 2026.0.

See Known Limitations and Issues for a list of limitations that we are aware of.

The fixes listed here are those that are viewed as likely to impact on users in an unexpected way, mainly changed simulation results, or differences in behaviour that might not be obvious.

Ruby method WSRunScheduler.wsma fails to launch script with specific names

When running wsma from a ruby script, certain characters in the action name and run name could cause a failure. Any illegal characters are now replaced to avoid a failure of this type.

Updating Demand Diagram

Sometimes updating the Demand Diagram from the Demand Area Analysis did not work. This is fixed.

Hydrant Testing GMR runs

The test case names were incorrect in Hydrant Testing GMR runs. Also, the hydrant diameter parameter did not work. This is fixed.

Transient Validation - Multiple pumps in a pump station

There was an issue where Transient runs with multiple pumps in a pump station were not correctly failing validation checks. This is fixed.

EPANET Import Error Message

When importing a model from an EPANET v2 file, an error message could sometimes be shown due to a long comment. Consequently the network/control changes were not automatically committed. This is fixed.

Incorrect Water Quality Help Links

When launching the help for Water Quality (MSQ) properties, users were being directed to the wrong help page. This is fixed.

Pipe Materials Dialog

When the pipe materials were exported, edited in Excel, and imported again, the pipe materials would be corrupted. The export has been improved so that the file can be edited in Excel.

Unable to Enable Multiple VSP Regulation

When editing Pump Station Control Data, there was an issue where Multiple VSP regulation could not be enabled for some scenarios. This is fixed.

TS Scenarios - not saving the control object in run set up

When configuring a non-base scenario TS run, the control object could sometimes get removed in error. This is fixed.

Ruby scenarios

After changing scenarios in Ruby, sometimes the script would not finish properly. This is fixed.

GMR Configuration dialog

On the GMR Configuration dialog, it was not possible to put in values in the left grid. This is fixed.

Repeat profiles

One day repeat profiles that started and ended exactly at midnight put the second midnight values at the end of the repeated profile. This is now fixed - the second midnight value is now ignored.

SQL Spatial Search

Sometimes spatial search did not work properly when combined with normal fields. This is fixed.

Transient Simulations

Setting the PRD Exit pressure to 0 resulted in an error, although this setting is allowed to be zero. This is fixed.

Transportable databases

When copying to a transportable database, sometimes error 15 would be displayed. This indicates that the software cannot open the zip file for writing. The software now tries writing several times before displaying error 15.

Check For Updates

The 'Check For Updates' link was targeting the wrong webpage. This is fixed.

Spatial bookmarks

When clicking the last item in a long list of spatial bookmarks, a different bookmark would be selected. This is fixed.

Pump curves

Right-clicking a row in the Pump Data grid for a Pump Station and selecting Pump Curve only worked for pump curves in the base scenario. This is fixed.

Working folder

Removing unused files in the working folder for databases with version 2025.3 and earlier did not work. This is fixed.

Demand Diagram

Pasting a profile into a Demand Diagram did not always work properly. This is fixed.

Control Time Interval

When changing the control time interval, profiles in other scenarios were not updated. Profiles in other scenarios can now be updated.

Check-in/Check-out simulations

Sometimes the engine would fail after changing the geometry in the network and doing a rerun for check-in/check-out simulations. This is fixed.

Forced Fire Flow

Picking a hydrant test location for forced fire flow did not work properly. This is fixed.

Was this information helpful?