V4.3.0.7.7 Release Notes
V4.3.0.7.7
This topic provides a list of product changes included in this patch.
Action Management
Description | Tracking ID |
---|---|
Previously, in the General Recommendation datasheet, when the Alert Assignee When Due check box was selected for a record, alert email messages were not sent. This issue has been resolved. | DE116027 |
Asset Criticality Analysis
Description | Tracking ID |
---|---|
Previously, if a field in a checklist was updated by a policy, the corresponding entity was not updated with the latest field value. This issue has been resolved. | DE114440 |
Asset Hierarchy
Description | Tracking ID |
---|---|
Previously, in the Hierarchy section of the Asset Finder window, the Add icon () was intermittently disabled due to which you could not add an asset to an analysis. This issue has been resolved. | DE110477 |
Asset Strategy Implementation
Description | Tracking ID |
---|---|
Previously, if you implemented a strategy maintenance plan in SAP, the unit for scheduling period appeared incorrectly. This issue has been resolved. | DE115380 |
Calibration Management
Description | Tracking ID |
---|---|
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. | DE116429 |
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. | DE116427 |
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 then entered values for As Found or As Left in the Calibration section, the error percentages were not calculated. This issue has been resolved. | DE116426 |
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. | DE116421 |
Previously, when you added assets to a Calibration Profile, the Applied Profile that was thus created was in the Development state. The values in the Template State field was not copied to the Applied Profile from the Profile Template. This issue has been resolved. | DE116412 |
Failure Modes and Effects Analysis
Description | Tracking ID |
---|---|
Previously, when you attempted to promote a Recommendation that was created using the Failure Modes and Effects Analysis (FMEA) data loader, an error occurred. This issue has been resolved. | DE116212 |
Previously, you could not consolidate the Recommendations that were created using the Failure Modes and Effects Analysis (FMEA) data loader. This issue has been resolved. | DE116023 |
Manage Translations
Description | Tracking ID |
---|---|
Previously, when managing translations for a family field through the globe button (), in the window for the localization of the field, if you did not provide translation for all the languages, when you attempted to use the family in a query, an error occurred. This issue has been resolved. | DE115260 |
Inspection Management
Description | Tracking ID |
---|---|
Previously, when an inspection event was created for an asset for which the Inspection Profile records were defined and sequenced, and when the auto-generate findings for the selected inspection event family was enabled, the automatically created General Finding records were not arranged in the order of the values in the assigned Sequence field. This issue also existed in Inspection Field Data Collection when the inspection event was downloaded. The issue has been resolved. Now, when viewing an inspection event in Inspection Management or in Inspection Field Data Collection, the General Finding records are arranged in the order of the values in the assigned Sequence field. Note: If the Inspection Profile records do not contain a value in the Sequence field, or if the General Finding records have been manually created, the General Finding records are arranged in alphabetical order of the values in the Inspection Profile Item field. | DE115888 |
Previously, you could not print Inspection Reports in bulk if the Inspection ID contained special characters that were not supported by the Windows operating system in a file name. This issue has been resolved. | DE115279 |
Policy Designer
Description | Tracking ID |
---|---|
Previously, a policy that was configured to be triggered when an Entity was created or modified was intermittently not triggered when the trigger event occurred. This issue has been resolved. |
|
Previously, an error message stating that the session had expired appeared periodically in the policy execution results. This issue has been resolved. | DE113039 |
Production Loss Analysis
Description | Tracking ID |
---|---|
Previously, the Event ID was automatically generated in the format <Event ID> ~ <Unique Sequence Number>. The format has been changed to <Unit Name> ~ <Headline> ~ <Unique Sequence Number>, so that you can add information from the Headline field. | DE116525 |
Previously, if you were assigned to the Production Loss Accounting Administrator Security Role and you attempted to remove the mapping between an Impact Code and an OEE Code, an error occurred if the mapping was used in a Production Loss record. This issue has been resolved. | DE115705 |
Previously, the State Management functionality was not activated even if you had enabled the State Management functionality. This issue has been resolved. | DE115597 |
Previously, if the values in the Product Name and Product Alias fields of a Production Profile were different in GE Digital APM or in the Production Loss Analysis (PLA) 1-Admin Data Loader, when you attempted to import Production Plans for the Production Profile using the Production Loss Analysis (PLA) 3-Plan Data Loader, the import job failed. This issue has been resolved. | DE115364 |
Previously, when reconciling production losses, you could not modify the estimated downtime value in the EDT field. This issue has been resolved. | DE115081 |
Previously, the list of active Products that appeared when creating or modifying Production Profiles, Plan Templates, and Production Plans were not sorted numerically. This issue has been resolved. | DE114902 |
Previously, when you attempted to create a Production Plan using a Plan Template, the Plan End Time was not automatically set based on the Plan Start Time. This issue has been resolved. | DE114901 |
Previously, when creating a Production Plan for a given Production Unit and start date, if another Production Plan already existed for the same Production Unit and start date, a warning message did not appear to indicate the possibility of creating a duplicate Production Plan. This issue has been resolved. | DE114900 |
Reliability Centered Maintenance
Description | Tracking ID |
---|---|
Previously, when you attempted to promote a Recommendation that was created using the Reliability Centered Maintenance (RCM) data loader, an error occurred. This issue has been resolved. | DE116212 |
Previously, you could not consolidate the Recommendations that were created using the Reliability Centered Maintenance (RCM) data loader. This issue has been resolved. | DE116023 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, if you had created a customized message using a custom rule, when you attempted to publish an RCA that was refrained from being published, the Internal Server Error message appeared, instead of the customized message. This issue has been resolved. | DE116153 |
Previously, when you attempted to link an asset to an Analysis, you could not find a list of Production Events associated with the Asset in the Linked Events section. This issue has been resolved. Now, you can find a list of events associated with the Asset and link them to the Analysis. | DE115273 |
Previously, when exporting the RCA Event Diagram to the SSRS Comprehensive Analysis Report, the resolution of large diagrams was poor when you zoomed in on them. This issue has been resolved. | DE113894 |
Rounds Data Collection
Description | Tracking ID |
---|---|
Previously, when you used the GE Digital APM mobile application to collect data, you could view a list of Routes that were not assigned to you. This issue has been resolved. | DE115280 |
Rounds Designer
Description | Tracking ID |
---|---|
Previously, while adding a reading for a Checkpoint with the character ML type and the allowable values defined, the Reading Value Character box appeared as a text box instead of a drop-down list box until the reading was created. When you attempted to modify the reading later, the Reading Value Character drop-down list box appeared with appropriate values. This issue has been resolved. | DE115524 |
Security Manager
Description | Tracking ID |
---|---|
Previously, you could access a Map query in the Maps tool only if you had one of the following privileges:
This issue has been resolved. Now, all the GE Digital APM users can access the Map queries in the Maps tool. | DE115905 |
Thickness Monitoring
Description | Tracking ID |
---|---|
To enhance the performance of the Thickness Monitoring Analysis Overview workspace, duplicate network calls have been removed. | DE115278 |
Previously, after collecting data using the DMS Go+ device, if the Send button was held for more than two seconds, the device would also store an A-Scan reading. In addition, the APM Thickness Monitoring Datalogger could not process the file containing an A-Scan or display the readings. These issues have been resolved. Note: GE Digital APM Thickness Monitoring does not store the A-Scan data stored on the device. You must upgrade Meridium Device Service application to the latest version. | DE114988 |
SAP Adapters
Description | Tracking ID |
---|---|
Previously, when using multiple culture extraction from SAP, the numbering format changed for some numbers, resulting in abnormally large numbers loading to GE Digital APM. This has been corrected. | DE115517 |