V3.6.1.7.0 Release Notes
V3.6.1.7.0
This topic provides a list of product changes released for this module on the dates listed below.
Advanced Search
Description | Tracking ID |
---|---|
Previously, if you entered values in the Search In, Linked To, and Through boxes and added one or more field conditions to an advanced search, an error occurred when you selected a hyperlink in the Linked To column in the search results. This issue has been resolved. | TFS351297 |
Asset Criticality Analysis
Description | Tracking ID |
---|---|
Previously, when sorting the records in an ACA System, the sort function erroneously interchanged the values in the System ID and Equipment ID columns. This issue has been resolved. | TFS345594 |
Previously, when accessing an ACA system from the pane in the page for the selected Analysis, if you expanded that system and then collapsed that system, if you expanded that system again, the records contained within that system were erroneously duplicated. This issue has been resolved. | TFS340038 |
Previously, when using the ACA module, Security Users with Read-Only permissions for the Risk Rank family encountered errors when the Not Applicable check box was selected on a Risk Matrix. This issue has been resolved. | TFS343384 |
Previously, if you deleted an ACA record from the Asset Criticality Analysis Summary page, the relationship between that record and the Functional Location was not properly deleted, and the record would still appear in search results. This issue has been resolved. Now, when you delete an ACA record from the Asset Criticality Analysis Summary page, the record and the relationship are deleted, and the record does not appear in search results. | TFS333963 |
Asset Health Manager (AHM)
Description | Tracking ID |
---|---|
Previously, when you took a reading for an asset using the GE Digital APM mobile application, the Health Indicator record associated with the asset was not correctly updated with the last reading date. This issue has been resolved. | TFS343365 |
Asset Strategy Management
Description | Tracking ID |
---|---|
Previously, when you attempted to apply an Asset Strategy Template as a master to your assets, the process to apply the template appeared to start, but the status progress bar did not reach 100 percent. This issue has been resolved. | TFS349305 |
Previously, if you updated the value in the Cost field of the Modify Action – Mitigating Condition Based Actions window for an existing Action, the value in the Annual Cost field did not was not updated based on the new value in the Cost field. This issue has been resolved. | TFS341464 |
Inspection Management
Description | Tracking ID |
---|---|
Previously, when you created an Inspection Task for an RBI Recommendation, the Task Details field in the Inspection Task was not populated when the RBI Recommendation was consolidated. This issue has been resolved. | TFS356893 |
Previously, when you used Record Manager to add a Finding to an Inspection record, the new Finding did not appear unless you refreshed the page. This issue has been resolved. | TFS352506 |
mobileAPM
Description | Tracking ID |
---|---|
Now, mobileAPM supports Near Field Communication (NFC) scanning capability built into the Ecom Smart-Ex 01 smartphone. | TFS356353 |
MobileAPM now supports iOS 11.3. | TFS356263 |
On the Inspection screen for Routes, an option is now available to filter and display on the device only Routes that are due based on the defined Route schedule. | TFS353992 |
When you return to the keyword search results on the Inspection screen for Routes after previously selecting a search result, your most recent search term and results now remain in effect until your session ends. | TFS353851 |
MobileAPM now supports the Ecom Smart-Ex 01 smartphone and its built-in NFC or Near Field Communication scanning capability. The third-party NFC Tools app is required and must be installed before you can take NFC tag readings with mobileAPM. | TFS341046 |
MobileAPM now supports Android 5.1. | TFS336168 |
Description | Tracking ID |
---|---|
Previously, you could not access Reference Documents when using mobileAPM on a handheld device with Android 5.x and older. This issue has been resolved. | TFS360207 |
Previously, when you entered search criteria to filter search results, the scroll functionally did not respond. This issue has been resolved. | TFS358699 |
Previously, when you used mobileAPM on a device, drop-down list boxes in the application may have been unresponsive, preventing you from making selections. This issue has been resolved. |
|
Previously, you could not access, via the Chrome browser version 65 or later, a Site, Area, Unit, or Asset whose name contained a space. This issue has been resolved. | TFS356986 |
Previously, on an Android version 4.x device, when you attempted to access the Inspection page in mobileAPM, you were unable to access the Routes to which you were subscribed. This issue has been resolved. | TFS356259 |
Previously, the last route did not appear in the Inspection screen. This issue has been resolved. | TFS353999 |
Previously, if you accessed mobileAPM from a device using Android 5.1.1, when you unsubscribed from a Route, the Route still appeared on the device. This issue has been resolved. | TFS353852 |
Previously, if your device was offline when you accessed mobileAPM, an incorrect message appeared stating the selected server was not available. If your device came back online, the same message was displayed when you accessed the application, the available data sources were not listed, and you had to re-enter the application server details. This issue has been resolved. Now, if you are offline, when you access the application, a message appears stating that you are offline and you need to go back online to reconnect. | TFS347784 |
Previously, when you accessed the Inspection screen to view the list of routes, routes whose IDs contained single quotes did not download and the routes remained in the Downloading status. This issue has been resolved. | TFS347546 |
Previously, when you accessed a site, then selected an item in the Area list, and then accessed the Inspection tab and searched for Route records, the search did not work as expected. This issue has been resolved. | TFS347542 |
Previously, you were unable to scan RFID tags using the Ecom Smart-Ex 01 Android device. This issue has been resolved. | TFS347541 |
Previously, when using MobileAPM on an iOS 11 device, the left menu panel did not open or close as expected after a new dialog box was opened. This issue has been resolved. | TFS343367 |
Previously, if a Route had multiple assets and Measurement Locations due, the green progress bar did not account for the unsatisfied conditional Measurement Locations. This issue has been resolved. | TFS286483 |
Policy Manager
Description | Tracking ID |
---|---|
Previously, for Policies with a Measurement Location node configured to automatically trigger the Policy, adding a new reading to the associated Measurement Location record triggered multiple Policy executions. This issue has been resolved. | TFS361160 |
Previously, when you executed a Policy configured to update Health Indicator records, the reading timestamp in the execution history appeared in Coordinated Universal Time (UTC) and in 12-hour format. This issue has been resolved. Now, in this scenario, the reading timestamp appears in 24-hour format and in the time zone associated with the Policy. | TFS344673 |
Previously, time in the execution history of Policies appeared in 12-hour format. This issue has been resolved. Now, the time appears in 24-hour format. | TFS337897 |
Production Loss Analysis
Description | Tracking ID |
---|---|
Previously, in the PLA – Production Event Management page, when you right-clicked the table header, and then selected the Show Available Fields option, the Available Fields list that appeared did not contain the custom fields that were added to the Production Event family. This issue has been resolved. | TFS352375 |
Queries
Description | Tracking ID |
---|---|
Previously, if you added a query alias for a field, the localization for the query alias was incorrectly applied to related Entity Family captions throughout the system. This issue has been resolved. Now, the localization will be applied only to the query alias. | TFS350275 |
Previously, if you accessed the query design view for a Crosstab query, and then attempted to run the query, an error occurred. This issue has been resolved. | TFS340030 |
Risk Based Inspection
Description | Tracking ID |
---|---|
Previously, the navigation paths for the following XML files were incorrect in the GE Digital APM Installation and Upgrade document:
| TFS362521 |
Previously, when you selected the Generate Recommendations using Policy Manager check box in the Admin Preferences for Risk Based Inspection window, and generated recommendations for an RBI 581 Risk Analysis associated with the Equipment that appears at the first level of the tree in the RBI Explorer pane, an inaccurate error message appeared. This issue has been resolved. Now, in this scenario, an error message appears, indicating that the recommendation generation failed because Inspection Strategy and Policy Records do not exist. | TFS346564 |
Previously, in an RBI 581 Risk Analysis, if you selected the Stress Override check box, the following issues existed:
| TFS340179 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, when you copied and pasted a node with an empty label in the Event Diagram, an error occurred. This issue has been resolved. | TFS352513 |
Previously, on the Event Diagram page, changes were not saved and errors occurred when you:
| TFS352266 |
SIS Management
Description | Tracking ID |
---|---|
Previously, in the Final Element Reference Data page, while creating or updating a Protective Instrument Loop Final Element, if you selected the Severe Service check box, an error occurred. This issue has been resolved. | TFS345395 |
Thickness Monitoring
Description | Tracking ID |
---|---|
Previously, when a user whose culture setting was French or German tried to save Thickness Measurement readings using a datalogger device, an error occurred. This issue has been resolved. | TFS343369 |