V3.6.1.6.X Patch Release Notes

V3.6.1.6.4

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

Risk Based Inspection (RBI) 581

DescriptionTracking ID
Previously, when you attempted to generate recommendations for multiple assets from unit level, recommendations were not generated for all the corresponding RBI 581 Risk Analysis. This issue has been resolved.TFS385036
Previously, when you selected the Enable recommendations to be generated at created state check box in the RBI administrative setting, and attempted to create a recommendation for RBI 581 Risk Analysis in the Created state, an error occurred. This issue has been resolved.TFS385036

V3.6.1.6.3

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

mobileAPM

DescriptionTracking ID
Previously, if the Close Date and Reading Taken Date fields were set to Coordinated Universal Time, and if your time zone in mobileAPM differed from the time zone of the server to which you uploaded a reading in a completed Route, those fields displayed an incorrect time. This issue has been resolved.TFS374644
Previously, if your culture setting was a variant of English other than English (United States), when you attempted to create a recommendation whose Target Completion Date value contained a value for the day that was greater than 12, the recommendation was not created. This issue has been resolved.TFS373162

V3.6.1.6.2

mobileAPM

Table 1. Resolved Issues
DescriptionTracking ID
Previously, using the Chrome browser version 65 or later, you could not access a Site, Area, Unit, or Asset whose name contained a space. This issue has been resolved.TFS370592
Previously, in the localized version of mobileAPM, when you accessed a Health Indicator, navigated to a different page, and then accessed the Health Indicator again, the date format changed. This issue has been resolved.TFS370583
Previously, in the localized version of mobileAPM, the text was not translated. This issue has been resolved.TFS369175
Previously, the date format in the date fields in an Operator Rounds Recommendation record was not updated based on the culture setting. This issue has been resolved.TFS369016
Previously, after you marked a Route done and refreshed the page, an error occurred. This issue has been resolved. Now, in this scenario, the Route History appears.TFS367911
Previously, the font size of the text in the More Information field in a Measurement Location record was too small. This issue has been resolved.TFS365936

V3.6.1.6.1

mobileAPM

Table 2. Resolved Issues
DescriptionTracking ID
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 opened. This issue has been resolved.TFS350645

Production Loss Analysis (PLA)

Table 3. Resolved Issues
DescriptionTracking ID
Previously, when you created or updated a Production Plan, the dates in the Production Data reflected your time zone, instead of the time zone specified in the Timezone field of the Production Unit. This issue occurred when the Timezone field was blank. This issue has been resolved. To facilitate this fix, Timezone has been made a required field.TFS350757
Previously, when you added or deleted a field from the Production Event family, the list of available fields on the PLA - Production Event Management page was not updated. This issue has been resolved.TFS350643

Risk Based Inspection (RBI)

Table 4. Resolved Issues
DescriptionTracking ID
Previously, the baseline RBI Risk Matrix could be customized by modifying values in the corresponding Risk Matrix record and the records to which it was linked. However, you were limited to using five Probability records and five Consequence records, which restricted the size of the RBI Risk Matrix and prohibited adding additional columns or rows. This issue has been resolved. Now, in compatible Meridium APM environments, you can select a larger 8x8 RBI Risk Matrix that accommodates eight Probability and eight Consequence records. Before using an 8x8 RBI Risk Matrix, however, contact GSS to configure the Meridium APM environment to ensure that the RBI Risk Matrix appears and functions as expected.TFS350642

Root Cause Analysis (RCA)

Table 5. Resolved Issues
DescriptionTracking ID
Previously, on the Event Diagram page, changes were not saved and errors occurred when you:
  • Added a node and then selected in the Node Properties window.
  • Deleted a link between nodes.
  • Assigned a decimal value to the x or y coordinates for a node in environments using a SQL database.
  • Repositioned a node having x-coordinate or y-coordinate decimal values in environments using a SQL database.
These issues have been resolved.
TFS340622