V4.3.0.7.4 Release Notes

V4.3.0.7.4

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

Activate Licenses

DescriptionTracking ID
Previously, when you activated a license, you had to manually take the data source to which you applied the license offline, and then bring it back online. Now, after activating the license, you must log off from GE Digital APM and log in again.DE109678

APM Data Extraction

DescriptionTracking ID
Previously, when you tried to fetch navigation (relationship) property data using a property request call, the service returned an HTTP 404 error. This issue has been resolved.DE109958

Asset Health Manager

DescriptionTracking ID
Previously, in the <Asset Name> workspace, links for Asset Health Manager did not appear. Additionally, when you accessed the Health Summary page, the page loaded slowly, and error messages appeared. This issue has been resolved.DE108371
Performance in the Risks section of the Health Summary page has been significantly improved.US338922

Asset Strategy Implementation

DescriptionTracking ID
To enhance performance and scalability, in ASI, the implement package operation has been converted to a job.US348194
To enhance usability, in the ASI Package workspace, importing a task list is now a background operation.US348193
To enhance usability, in the ASI Overview page, performance when loading large implementation packages has been improved.US348192

Calibration Management

DescriptionTracking ID
Previously, when CalibDeviceMappingsUpgradeUtility was run to upgrade to 4.3.0.0.0 or later for replacing the old Device Mapping IDs with the new Device Mapping IDs on all the existing templates, an error occurred. Due to this, you could not perform calibration on the old templates using Fluke calibrator. This issue has been resolved.
Note: The upgrade was required only if you wanted to use the Fluke documenting process calibrator.
DE109864

Data Loaders

DescriptionTracking ID
Previously, in a cloud environment, when you tried to load a .zip file containing .csv files using the Data Loader interface, the load intermittently failed with the message access denied. Now, the files load without errors.DE109151

Failure Modes and Effects Analysis (FMEA)

DescriptionTracking ID
Previously, the user experienced database errors when using FMEA data loaders under certain conditions. This issue has been resolved. Now, the incremental save feature has been added to these data loaders.DE109688

Family Policies

Table 1. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels.US347947
Table 2. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
  • The old Execution History records were not deleted.
  • The policy execution transactions were reverted because the Execution History table of the database was locked by the job. This resulted in the execution failure of policies while the job was in progress.
These issues have been resolved.
  • DE106869
  • DE101822

Inspection Management

DescriptionTracking ID
A new Human Resource role, Contract Inspector, is now available. A Contract Inspector can modify the Inspection Document Status field in Inspection records to Pending Approval without being the user defined in the Inspection Report Owner field if they are a Team Member in the associated Inspection record.US346807
Using the Inspection Management (IM) Assets and Inspection Management (IM) Functional Location data loaders, a Contract Inspector who is a Team Member in the associated Inspection record can now modify the Status field to Pending Approval without being the user defined in the Inspection Report Owner field.US346807
If you are using Status to manage your Inspection Recommendation records and you are a Team Member in the associated Inspection record, you can now transition the Inspection Recommendation to the Pending Review status without being the user defined in the Author field.US346807
Previously, the Inspection Lock field was disabled unless you were the Inspection Report Owner. This field is now enabled if you are a Team Member in the associated Inspection record.US346807

Policy Designer

Table 3. Enhancements and New Features

The following enhancements and new features have been added.

DescriptionTracking ID
The messages written in the server logs by the Policy Execution Service and Policy Trigger Service are now more specific to the logging levels.US347947
Table 4. Resolved Issues

The following issues that existed in one or more previous versions have been resolved.

DescriptionTracking ID
Previously, if you copied and renamed an Input node of the policy model, and then saved the policy, the following issues occurred until you reloaded the policy:
  • The renamed node did not appear in the instances associated with the policy.
  • All instances associated with the policy were deactivated due to which the policy was not executed.
  • The validation of the policy failed with an error message, indicating that you had not specified any record for the new Input node.
These issues have been resolved.
DE109329
Previously, when the job configured to delete the execution history logs ran, the following issues intermittently occurred:
  • The old Execution History records were not deleted.
  • The policy execution transactions were reverted because the Execution History table of the database was locked by the job. This resulted in the execution failure of policies while the job was in progress.
These issues have been resolved.
  • DE106869
  • DE101822

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.
DE109171

RBI 581

DescriptionTracking ID
Previously, you could not create a Quantitative (581) analysis if the logged in user culture was Russian. This issue has been resolved. DE109168

Reliability Analytics

DescriptionTracking ID
Previously, in the Failure Probability workspace, if you selected Future Probability and then entered a value in the Set Future Probability window, the value in the Future Failure Probability column was not correctly updated. This issue has been resolved.DE109848

Reliability Centered Maintenance (RCM)

DescriptionTracking ID
Previously, the apply template builder took a long time to load when the template was complex. This issue has been resolved. Now, when creating an analysis from a template, the Apply Template Builder window loads more quickly.DE109690
Previously, the user experienced database errors when using RCM data loaders under certain conditions. This issue has been resolved. Now, the incremental save feature has been added to these data loaders.DE109688

Root Cause Analysis

DescriptionTracking ID
Previously, when you created an RCA for a Production Event from the Production Loss Analysis (PLA) module, in the Analysis Summary workspace, in the Linked Assets section, the Causing Asset associated with the Production Event did not appear in the Record ID column. This issue has been resolved.DE109585

Rounds Designer

DescriptionTracking ID
Previously, when creating a Checkpoint condition, you could not enter a value in the Select Value box when an allowable value was not defined. This issue has been resolved.DE108709

Rules

DescriptionTracking ID
You can now compile only the family rules that you added or modified, instead of compiling all the family rules in a rules library project. To facilitate this enhancement, the data source ID is now used instead of GUID. This enhancement also resolves possible errors when compiling rules with references to other rule projects.
Note: You must compile all the family rules only if you modify the data source ID.
US352396