V4.3.0.7.13 Release Notes
V4.3.0.7.13
This topic provides a list of product changes included in this patch.
Action Management
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to send actions to ASI from Action Management, an error occurred. This issue has been resolved. | DE132292 |
| Previously, when you performed state assignments for multiple recommendations in bulk, it was not assigned to all the selected recommendations. This issue has been resolved. | DE131762 |
Asset Strategy Management
| Description | Tracking ID |
|---|---|
| Previously, in the Risk Analysis workspace, when using a risk matrix with Max Risk Rank enabled, the proposed risk rank was incorrectly calculated. This issue has been resolved. | DE131323 |
| Previously, when using a risk matrix with a combination of non-financial category with a protection level and a financial category, an error occurred. This issue has been resolved. | DE130647 |
Family Management
| Description | Tracking ID |
|---|---|
| Previously, in some cases, if you attempted to delete custom fields (i.e., non-baseline) in a family, an error occurred. This issue has been resolved. | DE129386 |
Policy Designer
| Description | Tracking ID |
|---|---|
| Previously, the input values of a policy instance that were of string data type appeared incorrectly in the Validation workspace. This issue has been resolved. | DE132300 |
Production Loss Analysis
| Description | Tracking ID |
|---|---|
| Previously, in PLA Loss Reconciliation datasheet, the Equivalent Downtime Hours field would fail to populate the value in the loss datasheet. This issue has been resolved. | DE132680 |
| Previously, when you searched for Production Loss records using the global search box, and then attempted to open a loss record, an error message appeared. This issue has been resolved. | DE132676 |
Queries
| Description | Tracking ID |
|---|---|
| Previously, if you specified a value near to zero in the search criteria, after UOM conversion it was rounded to 0. It was also applicable to non-zero values. For example, 10.0000000001 was rounded to 10. This issue has been resolved. Now, the value remains as specified. However, you may see exponential values (i.e., power of x). | DE131953 |
| Previously, when a user ran the query and used GETDATE function, the time value displayed the time zone associated with the user who was logged in. This issue has been resolved. Now, a new UTC function is added to avoid date field conversion. |
|
Reliability Analytics
| Description | Tracking ID |
|---|---|
| Previously, when generating a comparison plot across several Reliability Growth Analyses (RGA) or Production Analyses, the colored chart lines indicating each source analysis were using the same shape symbol on the line. This was in conflict with the chart legend and was difficult for the user to differentiate by color. This issue has been resolved. | DE131883 |
| Previously, in System Reliability, when adding Global Events, the field titles and check boxes were misaligned. This issue has been resolved. | DE131550 |
| Previously, in Reliability Analytics, the charts from many of the diagrams did not contain the legends when they were printed or viewed in HTML format. This issue has been resolved. Now, all charts in the reports show the corresponding legends. | DE130663 |
Reports
| Description | Tracking ID |
|---|---|
| Previously, while generating SQL Server Reporting Services (SSRS) report, when you selected the check box for multiple parameters, an error occurred. This issue has been resolved. Now you can generate reports with multiple parameters. | DE125461 |
Rounds Data Collection
| Description | Tracking ID |
|---|---|
| Previously, when a route tried to load Rounds Data Collection (RDC) on an Android device, it failed due to the combination of the route size and structure, and an error "Uncaught RangeError: Invalid array length" appeared. In a few other cases, the route was unable to load, and the application would close. This issue has been resolved. Now, the app allows the route to load RDC without producing any error or crashing the device. | DE133373 |
| Previously, in the GE Digital APM mobile application, GIS timeout settings were handled incorrectly which caused a delay in taking the readings, even when the timeout was set to zero. This issue has been resolved. Now, the timeouts are being recorded correctly when the GE Digital APM mobile application is either offline or online. | DE131628 |
Single Sign-On
| Description | Tracking ID |
|---|---|
| Previously, when you attempted to log in to GE Digital APM through windows devices using Single Sign-On (SSO) authentication, an error occurred. This issue has been resolved. Now you can login through windows device using SSO authentication. | DE130604 |
System Requirements
| Description | Tracking ID |
|---|---|
| Previously, if you accessed GE Digital APM using Chrome browser version 80 or higher, you may have experienced some issues. These issues have been resolved. | DE128759 |
Thickness Monitoring
| Description | Tracking ID |
|---|---|
| Previously, the TM Dataloggers page could not load large amount of data while sending Thickness Measurement Locations (TMLs) to the datalogger. This issue has been resolved. Now, to avoid issues related to saving and analyzing large amount of TML data while receiving, the operation has been moved to scheduler. | DE131736 |
| The performance of the Analysis Overview workspace and the TMLs section has been significantly improved. To facilitate this enhancement, the Based on field now appears as a hyperlink that allows you to access the Thickness Measurement Locations (TMLs) associated with the analyses in the Based on window. | DE130887 |
| Previously, in the TM Dataloggers page, when you selected the check box in the header of the Send To or Receive From sections, only the TMLs available in the current page were selected and the TMLs in other pages were not selected. This behavior did not allow you to send or receive all the TMLs at a time. This issue has been resolved. Now, if you do not select any TML in the grid and select the Send (in the Send To section) or Save (in the Receive From section) button, all the TMLs are sent or received respectively. | DE130886 |
Units of Measurement
| Description | Tracking ID |
|---|---|
| Previously, if you specified a value near to zero in the search criteria, after UOM conversion it was rounded to zero. It was also applicable to non-zero values. For example, 10.0000000001 was rounded to 10. This issue has been resolved. Now, the value remains as specified. However, you may see exponential values (i.e., power of x). | DE131953 |