|
Date |
|
|
Version |
STS-3.14.1 |
Summary
V3.14.1 is a maintenance release centered on product quality and workflow reliability. The release resolves several issues affecting IID import flows, documentation generation, variable resolution and miscellaneous bugfixes.
Import
-
New IEDs were incorrectly considered locked during IID import.
-
Fixed misleading messaging when importing a new IID.
Documentation generation
-
Fixed crashes in the customized report selection dialog on some projects.
UI
-
InternalBindings dialog's IED to Specification did not properly open the ExtRef selection dialog
-
Communication Editor's Report matrix showed an Exception notification in some cases
Application templates
-
Updating a conducting equipment from the library did not trigger application templates to collect equipment functions with fitting application roles.
-
Deleted application roles left a remnant that could interfere with new application roles that use the same role.
Variable expressions and Extended Parameters
-
Changes to an element were not correctly propagated to children with descriptions attributes using a variable expression.
-
Fixed faulty infinite-recursion detection and message when names with variable expressions introduced name collisions and were renamed.
-
Custom Signal list definitions (.ptd files) could use incorrectly cached values for variable resolution in some configurations
-
Variables that recursively reference other variables could use outdated intermediate values
-
Formula editor now correctly exposes allocation role variables when editing ComConf parameters.
-
Extended Parameters Global Editor now supports creating and deleting missing parameters.
Communication configuration
-
Missing ClientServices in subscribing IEDs no longer block publishing.
-
Fixed detached object behaviour in repository object checks.
Miscellaneous
-
Datatypes that were unused during program start could cause resolution problems if they became referenced later. This could lead to unexpected failure for signals and logical nodes to resolve during normal workflow.
-
Reverse engineering GSE and SV applications did not properly resolve subscribing logical nodes that were created in the same reverse engineering step.
-
History item creation failed when the revision string did not start with a letter and the digits overflowed (i.e. 9->10).