V4.3.0.6.10 Release Notes

V4.3.0.6.10

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

Calibration Management

DescriptionTracking ID
Previously, when you added assets to a Calibration Profile, the applied profile that was thus created was in the Development state. In addition, the Template State value was not copied from the Profile Template to the applied profile. This issue has been resolved.DE116366
Previously, after you upgraded the GE Digital APM database from V3 to V4, certain Calibration Events did not appear in the Calibration Events section. This issue has been resolved.DE116320
Previously, after you upgraded the GE Digital APM database from V3 to V4, in the Calibration Queue section, the records that existed in the database before the upgrade did not appear, because the existing Calibration Templates were not directly linked to the Calibration Tasks. This issue has been resolved.DE116319
Previously, after you upgraded the GE Digital APM database from V3 to V4, when you created a Calibration (Event) manually from a Calibration Task, saved the record, and entered values for As Found or As Left in the Calibration section, the error percentages were not calculated. This issue has been resolved.DE116318
Previously, after you upgraded the GE Digital APM database from V3 to V4, when you attempted to create a Calibration (Event) manually from a Calibration Task, an error message appeared. This issue has been resolved.DE116317

Units of Measure and Conversions

DescriptionTracking ID
Previously, in the UoM field, when you searched for a converted value, the search was applied on the original UoM data instead of the converted value in a query result. In addition, the issue data was not filtered correctly. This issue has been resolved. Now, the search on the UoM field works according to the User conversion set.DE115384

Risk Based Inspection (RBI) 580

DescriptionTracking ID
Previously, in the Criticality Consequence Evaluation datasheet, two required fields for Heat Exchanger Bundles, Flammable Leak Type and Toxic Leak Type, did not have the Not Applicable (N/A) option in their respective drop-down list boxes. This issue has been resolved.
Additionally, the following validation changes have been made:
  • The Flammable Leak Type field is required irrespective of the governing representative fluid type.
  • The Toxic Leak Type field is required in the following scenarios:
    • If the Governing or Leaking fluid is toxic.
    • If the Governing or Leaking fluid contains a toxic mixture.
DE114989