V4.3.0.7.2 Release Notes

Asset Health Manager

Description	Tracking ID
Previously, because time stamp values for health indicator readings were truncated, health indicator readings were sometimes duplicated, and sometimes health indicators erroneously appeared to be out of sync. This issue has been resolved.	DE106890
Previously, in the Health Summary page, sometimes a No Status icon () erroneously appeared next to health indicators that had a valid status. This issue has been resolved.	DE106606
Previously, if you specified that you wanted to store zero readings in the GE Digital APM database, the PDI service stored a reading and then deleted it, which caused performance degradation. This issue has been resolved. Now, the PDI service no longer adds and deletes extraneous readings, and, as a result, database performance is significantly improved. This issue has been resolved.	DE107755

Asset Hierarchy

Description	Tracking ID
Previously, in the Group section of the Asset Finder window, when you attempted to add a group of assets, an error occurred. This issue has been resolved.	DE107347

Catalog

Description	Tracking ID
Previously, after you upgraded an Oracle data source, certain custom folders did not appear in the catalog under Public > Meridium. This issue has been resolved.	DE106796

Family Policies

Description	Tracking ID
Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur: If one of the variable names contains an underscore after the string, no notification appears in the notification bar. If one of the variable names contains a numeric value after the string and if there is a possibility of conflict between the variable names during the execution of the policy, a warning appears in the notification bar.	DE107317
Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value which is same as the default value of the corresponding field, the execution of the policy failed, and an error message appeared in the Node Execution Details window for the node, indicating that the index size is incorrect. This issue has been resolved.	DE106599

Description

Tracking ID

Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur:

If one of the variable names contains an underscore after the string, no notification appears in the notification bar.
If one of the variable names contains a numeric value after the string and if there is a possibility of conflict between the variable names during the execution of the policy, a warning appears in the notification bar.

DE107317

Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value which is same as the default value of the corresponding field, the execution of the policy failed, and an error message appeared in the Node Execution Details window for the node, indicating that the index size is incorrect. This issue has been resolved.

DE106599

Graphs

Description	Tracking ID
Previously, when you accessed a heat map graph that was based on a query that contained hyperlinks, the hyperlinks on the graph did not work as expected. This issue has been resolved.	DE106778

Policy Designer

Description	Tracking ID
Previously, when you started the Policy Execution Service or Policy Trigger Service, if the Microsoft Message Queuing (MSMQ) stopped responding or could not be accessed, the service failed to start. This issue has been resolved.	US341549
Previously, in the Properties window for a Math node, when you specified the names of some variables, an error message appeared in the notification bar, indicating a conflict between variable names, even when there was no apparent conflict in the specified names. This issue occurred when two variable names contained the same string and one of them contained an underscore or numeric value after the string. This issue has been resolved. Now, in these scenarios, the following events occur: If one of the variable names contains an underscore after the string, no notification appears in the notification bar. If one of the variable names contains a numeric value after the string and if there is a possibility of conflict between the variable names during the execution of the policy, a warning appears in the notification bar.	DE107317
Previously, in the Properties window for a Create Entity node, in the Value box, if you specified a value which is same as the default value of the corresponding field, the execution of the policy failed, and an error message appeared in the Node Execution Details window for the node, indicating that the index size is incorrect. This issue has been resolved.	DE106599

Reliability Analytics

Description	Tracking ID
Previously, when running a simulation on a complex analysis with a large number of buffer components in System Reliability, the simulation did not complete. This issue has been resolved.	DE106782

Rounds Data Collection

Description	Tracking ID
Previously, when attempting to create an Operator Rounds Recommendation, if you selected the Create EAM Work Request? checkbox prior to saving the recommendation, an error occurred, and the recommendation record would not be created. This issue has been resolved.	DE105520

Rounds Designer

Description	Tracking ID
Previously, if you attempted to use a data loader to add a checkpoint to a Route, the sequence of existing checkpoints on the Route was unintentionally modified. This issue has been resolved.	DE106752
Previously, loading a small number of records using the Rounds Routes Data Loader would occasionally result in timeout errors. This issue has been resolved.	DE106749
Previously, if you attempted to move a checkpoint node by dragging and dropping it into a header, an error occurred. This issue has been resolved.	DE106403

Schedule Logs

Description	Tracking ID
Previously, a policy was not executed as per the schedule until you updated the policy, if the following changes had been made to the GE Digital APM database that contained the policy: The GE Digital APM database had been restored and connected to another data source. The GE Digital APM server associated with the GE Digital APM database had been restarted. This issue has been resolved.	DE102150

Thickness Monitoring

Description	Tracking ID
Previously, if you used the TM Equipment or TM Functional Location data loaders to load data that consisted only of measurements, the Analysis Required check box in the TML Corrosion Analysis datasheet was not selected, and the Calculate button () did not turn orange. If you tried to calculate the analysis, the newly loaded measurements were not included in the calculation. This issue has been resolved. Now, when you load measurements, the Analysis Required check box is selected, and the Calculate button () turns orange, indicating the analysis is ready to be calculated. When you calculate the analysis, the newly loaded measurements are included in the calculation. Also, the affected assets are available in the Assets Requiring a Calculation section of the Thickness Monitoring Overview page, ready for bulk calculation.	DE106600

Description

Tracking ID

Previously, if you used the TM Equipment or TM Functional Location data loaders to load data that consisted only of measurements, the Analysis Required check box in the TML Corrosion Analysis datasheet was not selected, and the Calculate button (

) did not turn orange. If you tried to calculate the analysis, the newly loaded measurements were not included in the calculation. This issue has been resolved. Now, when you load measurements, the Analysis Required check box is selected, and the Calculate button (

) turns orange, indicating the analysis is ready to be calculated. When you calculate the analysis, the newly loaded measurements are included in the calculation. Also, the affected assets are available in the Assets Requiring a Calculation section of the Thickness Monitoring Overview page, ready for bulk calculation.

DE106600