What's new in this version

Ruby scripts stored in database with editor

Ruby scripts can be stored within the database as Ruby script objects. This allows users to store, review, test, and share scripts across teams.

A sample library of Ruby scripts is available to load into any database as a set of examples to learn from. These can be accessed when creating a Ruby Script Group from a Model Group and check on “Load factory Ruby scripts”.

In addition, ruby scripts support bulk import and export, calling scripts through custom actions, calling methods from other scripts in the same ruby script group, and validation of scripts. Read About Ruby Scripts to learn more.

Ground model TIN import from LandXML

LandXML format is now supported when importing Ground Model TIN objects. This enables easier sharing of elevation data from Civil 3D.

DWG import supports 3D polylines with elevation data

The DWG importer now includes elevation data for lines and 3D polylines. Lines with start and end Z coordinates will have these values assigned to the nodes created at each end. 3D polylines will be divided into multiple pipe segments, with a node placed at each vertex that has a Z coordinate indicating elevation. Additionally, network connectivity after import has been enhanced.

Reserved Runs in cloud no longer lock associated data

Objects used in Reserved Runs will no longer become read-only. Data becomes read-only after the run is unreserved and shared with others. This applies to the following objects:

• Demand Diagram
• Generalised Multi-Run Config
• Fire Flow Config
• Demand Scaling
• Electricity Tariff
• UPC Scenario

Customer point fields are now available from nodes within SQL and Ruby

SQL Queries and Ruby scripting can now access the customer_points fields for Nodes objects. This allows better review and reporting of customer point demands associated across junctions throughout the network.