V4.3.0.6.12 Release Notes

V4.3.0.6.12

This topic provides a list of product changes included in this patch.

Queries

DescriptionTracking ID
Previously, queries using DISTINCT or UNION operator were not sorted by columns other than the first column. This issue has been resolved.DE119828

RBI 581

DescriptionTracking ID
Previously, irrespective of the Unit of Measure (UOM) Conversion Set configured for your user account, the Consequence of Failure and Risk Values on the RBI 581 ISO-Risk Plot appeared in imperial units. This issue has been resolved.DE125905

Reliability Analytics

DescriptionTracking ID
Previously, when accessing a System Reliability Analysis in certain instances, an error message appeared, and the analysis failed to open. This issue has been resolved.DE127656
Previously, in System Reliability, you could not run a simulation for a System Analysis with frequent failures in risks or with a value in the Last Failure field. An error message appeared, stating that the p parameter must contain a value between zero and one. This issue has been resolved.DE125931

Root Cause Analysis

DescriptionTracking ID
Previously, when creating an Event diagram, the links between nodes were not retained after you saved the Event diagram. This issue has been resolved.DE126939

Rules

DescriptionTracking ID

Previously, when you created a Date Format rule, an incorrect date based on the rule was displayed in the UI. This issue has been resolved. Now, you can update the date format rule to return the date format that you want.

For example:

Old format:

Public Overrides Function FormatValue(ByVal value As Object) As String
    If value Is DBNull.Value Then Return String.Empty Else Return CDate(value).ToString("dd/MMM/yyyy")
End Function

New Format:

Public Overrides Function FormatValue(ByVal value As Object) As String
    If value Is DBNull.Value Then Return String.Empty Else Return "dd/MMM/yyyy"
End Function
DE122739