2018 Release 4 - Release Notes
Hydraulics & Hydrology Enhancements
- This version uses OpenFlows SewerGEMS version 10.02.00.52.
- The performance of the Extract Utility from Graphics tool has been improved. Previously, each pair of points along the path of the conduit was represented as a two-point line - each of which had associated rules. Now, the points along the path are represented as bends along a single line.
- Publishing an iModel from a DGN that contains Subsurface Utilities data can now be automated using the iModel Composition Service in ProjectWise.
- The availability of the various licences that can be activated in Subsurface Utilities (e.g. CivilStorm, SewerCAD) can now be configured by the Site Administrator, using CONNECT Licensing. Previously, Subsurface Utilities didn't know whether a licence for one of these products was available or not, so a generic message telling you that usage would be logged, and additional charges might occur, was displayed. Now, availability is controlled by CONNECT Licensing, which means that you can see exactly what product licences and feature levels (number of inlets or links) are available.
- The ability to set the parent catchment for a Low Impact Development is now available, meaning that these types of elements can be set up correctly in Subsurface Utilities.
- The Composite Outlet Structures and Low Impact Development icons on the Components ribbon have been made larger, to make them easier to find.
Defects Resolved
- Referenced DGNs that contain Subsurface Utilities data were being loaded as if they were activated, causing prompts to synchronize the data, followed by an exception.
- Changing scenarios could cause the graphical data and the corresponding data in the database to become out of synchronization.
- A utility project created in a DGN without using the correct seed file caused problems when publishing an iModel. This situation is now tested, and an error message is displayed if the SUDA_SEED_FILE and SUDA_SEED_MODEL variables do not provide a suitable seed.
- Cells for nodes could be rotated incorrectly in the 2D model if their construction class elements used Bylevel, as opposed to specific, symbology.
- The results of a query were not being highlighted in the 2D model.
- A hang in the Set Feature Definition tool that occurred when it was being used on a larger number of nodes.
- Performance was negatively impacted by a large terrain model, if it was set active.
- Conflict Detection was not finding conflicts if one of the conflicting elements was in a reference file.
- An exception which occurred when using Reconnect Link to move a link between nodes if only one of the two nodes had a feature definition.
- An issue with deleting and creating profile runs when a view of the profile run was open.
- An issue with inserting a node in a conduit, and splitting the conduit in two. This could cause an exception, or could result in the new piece of conduit losing its profile.
- An exception that occurred if the feature definition for a storm or sanitary conduit did not have a hydraulic prototype is now error trapped.
- A hang that occurred when using the Flood Fill method to create a catchment.