V4.3.0.7.9 Release Notes
V4.3.0.7.9
This topic provides a list of product changes included in this patch.
Asset Strategy Implementation
| Description | Tracking ID |
|---|---|
| Previously, when a Work Management Item (WMI) was being updated, you could navigate to and access other sections of the associated ASI Package. This issue has been resolved. Now, in this scenario, you cannot access other sections of the associated ASI Package. | DE119903 |
Calibration Management
| Description | Tracking ID |
|---|---|
| Previously, if you accessed GE Digital APM using an Active Directory account (LDAP user ID), performed an automated calibration, and then attempted to receive data into GE Digital APM, an error occurred. This issue has been resolved. | DE120971 |
Inspection Management
| Description | Tracking ID |
|---|---|
| Previously, when accessing an Inspection that contained exactly 25 General Finding related records, when you scrolled through the General Findings in the left pane, the system performed an infinite scroll. This issue has been resolved. | DE120364 |
Policy Designer
| Description | Tracking ID |
|---|---|
| Previously, if an entity that was specified as a trigger for automatic policy execution was modified more than once within a short time span (that is, less than one second), only one policy execution was triggered. This feature, which was implemented to prevent unintended duplicate policy executions, resulted in some intended policy executions being skipped. This issue has been resolved. Now, policy execution is triggered each time an entity is modified, except for policies that are triggered by new Readings added to a Measurement Location. Note: For policies that are triggered by new Readings added to a Measurement Location, duplicate policy executions are still prevented because the insertion of new Readings using the Rounds Data Collection module results in multiple entity updates. | US371381 |
| You can now configure a policy to create an execution history log record for all the executions or only the executions that result in an error. For more information about how to enable the Execution History Log Error Only setting, refer to KBA: V4.3.0.7.9 – Policy Designer – How to Enable Execution History Log Error Only setting. | US358708 |
Reliability Analytics
| Description | Tracking ID |
|---|---|
| Previously, in a Reliability Recommendation record, if you selected the Create Work Request check box, and then saved the record, the SAP Notification that was created did not contain the Equipment and Functional Location values associated with the record. This issue has been resolved. | DE119878 |
Risk Matrix
| Description | Tracking ID |
|---|---|
| Previously, when calculating risk using a Risk Matrix, the values specified in the Weight boxes of the associated risk category records were not considered in the calculation. This issue has been resolved. | DE120519 |
Root Cause Analysis
| Description | Tracking ID |
|---|---|
| Previously, in an RCA Recommendation record, if you selected the Create Work Request check box, and then saved the record, the SAP Notification that was created did not contain the Equipment and Functional Location values associated with the record. This issue has been resolved. | DE119877 |
Strategy Macros
| Description | Tracking ID |
|---|---|
| Previously, if you did not have Administrator or Super User privileges and you attempted to execute strategy macros from an Associated Page URL, an error occurred. This issue has been resolved. | DE121359 |
Thickness Monitoring
| Description | Tracking ID |
|---|---|
| Previously, if the measurements of a Thickness Measurement Location was at a high loss, and if you attempted to organize the Thickness Measurement Locations from the Organize TMLs workspace, an error occurred indicating that the calculation failed. This issue has been resolved. | DE120290 |