V4.3.0.6.X Release Notes
V4.3.0.6.15
This topic provides a list of product changes included in this patch.
General Dashboards
Description | Tracking ID |
---|---|
Previously, if the catalog path for a query or a graph was used in a dashboard and if it contained an ampersand (&), the widget failed to load. This issue has been resolved. | DE151794 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, when you generated RCA Comprehensive Analysis report, the report was generated without Logic Tree and Event diagrams. This issue has been resolved. | DE147919 |
Previously, in RCA Event Timeline, you could not add the end date for an Event. This issue has been resolved. | DE142503 |
V4.3.0.6.14
This topic provides a list of product changes included in this patch.
Action Management
Description | Tracking ID |
---|---|
Previously, in the General Recommendation datasheet of a Recommendation record, even though the Alert Assignee When Due check box was selected, the alert emails were not sent. This issue has been resolved. | DE146029 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, you could not save RCA Recommendations if the target completion date had passed. This issue has been resolved. | DE144522 |
V4.3.0.6.13
This topic provides a list of product changes included in this patch.
Asset Strategy Optimization
Description | Tracking ID |
---|---|
Previously, in a Risk associated with a Scenario, if you modified the unit of time specified for the Time to Failure (TTF) or Time to Repair (TTR), and then saved the Risk, the modified value was not retained. This issue has been resolved. | DE136634 |
Data Loaders
Description | Tracking ID |
---|---|
Previously, if your user account was configured with a culture setting other than English, and you uploaded data using a data loader, the numeric values in the data were not formatted according to the configured culture setting. This issue has been resolved. | DE139519 |
Reliability Analytics
Description | Tracking ID |
---|---|
Previously, in the Analysis Summary workspace of a Reliability Growth Analysis, in the Analysis Data menu, the Reload option did not appear due to which you could not reload the data of the Reliability Growth plots. This issue has been resolved. | DE131973 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, RCA team members did not receive email notifications. This issue has been resolved. | DE137246 |
Security Manager
Description | Tracking ID |
---|---|
Previously, if a user account was locked in Microsoft Active Directory, and you ran the LDAP synchronization process, the corresponding Security User account in GE Digital APM was locked. This issue has been resolved. Now, in this scenario, the user account of a Security User is not locked even though the corresponding account is locked in Microsoft Active Directory. | DE138870 |
V4.3.0.6.12
This topic provides a list of product changes included in this patch.
Queries
Description | Tracking ID |
---|---|
Previously, queries using DISTINCT or UNION operator were not sorted by columns other than the first column. This issue has been resolved. | DE119828 |
RBI 581
Description | Tracking ID |
---|---|
Previously, irrespective of the Unit of Measure (UOM) Conversion Set configured for your user account, the Consequence of Failure and Risk Values on the RBI 581 ISO-Risk Plot appeared in imperial units. This issue has been resolved. | DE125905 |
Reliability Analytics
Description | Tracking ID |
---|---|
Previously, when accessing a System Reliability Analysis in certain instances, an error message appeared, and the analysis failed to open. This issue has been resolved. | DE127656 |
Previously, in System Reliability, you could not run a simulation for a System Analysis with frequent failures in risks or with a value in the Last Failure field. An error message appeared, stating that the p parameter must contain a value between zero and one. This issue has been resolved. | DE125931 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, when creating an Event diagram, the links between nodes were not retained after you saved the Event diagram. This issue has been resolved. | DE126939 |
Rules
Description | Tracking ID |
---|---|
Previously, when you created a Date Format rule, an incorrect date based on the rule was displayed in the UI. This issue has been resolved. Now, you can update the date format rule to return the date format that you want. For example: Old format:
New Format:
| DE122739 |
V4.3.0.6.11
This topic provides a list of product changes included in this patch.
Asset Criticality Analysis
Description | Tracking ID |
---|---|
Previously, when you attempted to export an analysis that contained both Not Applicable (NA) and non-NA criticality assessments using the Asset Criticality Analysis (ACA) Data Loader, an error occurred, and the file was not exported. This issue has been resolved. | DE118875 |
Thickness Monitoring
Description | Tracking ID |
---|---|
Previously, if the Asset Hierarchy was configured to use the Equipment Has Equipment relationship, the Asset Hierarchy navigation links could not differentiate between a parent Equipment and a child Equipment. This issue has been resolved. | DE117520 |
V4.3.0.6.10
This topic provides a list of product changes included in this patch.
Calibration Management
Description | Tracking 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
Description | Tracking 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
Description | Tracking 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:
| DE114989 |
V4.3.0.6.9
This topic provides a list of product changes included in this patch.
Asset Criticality Analysis
Description | Tracking ID |
---|---|
To fix errors in ACA data loader, the parallel processing feature for ACA data loaders has been reverted. | US350881 |
Asset Strategy Implementation
Description | Tracking ID |
---|---|
To enhance performance and scalability, in ASI, the implement package operation has been converted to a job. | US346475 |
Inspection Management
Description | Tracking ID |
---|---|
Previously, when you configured an Inspection record to use a master/detail datasheet, an error occurred when saving the Detail section of the datasheet. This issue has been resolved. | DE109450 |
V4.3.0.6.8
This topic provides a list of product changes included in this patch.
Asset Criticality Analysis
Description | Tracking ID |
---|---|
Previously, in the Risk section of the Analysis Summary page, if you accessed an analysis whose associated Risk Matrix record had the Use Aliases? check box selected, the Total Risk value on the risk assessment appeared as a numeric value instead of an alias value. | DE105650 |
Previously, in the ACA Admin page, if you locked the Probability, Consequence, or Protection Level fields for an ACA System Criticality Analysis, if you then accessed the Risk Matrix for that analysis, the fields were not locked. This issue has been resolved. | DE104128 |
Calibration Management
Description | Tracking ID |
---|---|
Previously, if the Task ID field in a Calibration Task contained a slash (/) character, and you attempted to perform an automated calibration using a CMX device or a manual calibration, an error occurred. This issue has been resolved. | DE103123 |
Family Management
Description | Tracking ID |
---|---|
Previously, if a newly created field had been added to a datasheet belonging to the Checklist Findings family, and you attempted to access a checklist category for an inspection belonging to a checklist inspection family, an error message appeared, indicating that the datasheet failed to load. This issue has been resolved. | DE104138 |
Risk Based Inspection 580 and 581
Description | Tracking ID |
---|---|
DE104014 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, when viewing an RCA, if your screen size was too small, the Logic Tree and Event Diagram tabs did not appear in the pane. This issue has been resolved. | DE103254 |
V4.3.0.6.7
This topic provides a list of product changes included in this patch.
Asset Criticality Analysis
Description | Tracking ID |
---|---|
Previously, in the Risk section of the Analysis Summary page, if you accessed an analysis whose associated Risk Matrix record had the Use Aliases? check box selected, the Total Risk value on the risk assessment appeared as a numeric value instead of an alias value. | DE98421 |
Graphs
Description | Tracking ID |
---|---|
Previously, if you created a graph using a Crosstab query and mapped fields containing site data to the vertical axis, the graph legend and tooltips contained values from the first field in the list, irrespective of the site to which you are assigned. This issue has been resolved. | DE103122 |
V4.3.0.6.6
This topic provides a list of product changes included in this patch.
Failure Modes and Effects Analysis
Description | Tracking ID |
---|---|
To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | DE97426 |
Production Loss Analysis (PLA)
Description | Tracking ID |
---|---|
Previously, when you attempted to create a Production Profile, an error message appeared, stating that records were not found. This issue has been resolved. | DE98109 |
R Scripts
Description | Tracking ID(s) |
---|---|
The R Scripts module now supports Machine Learning Server 9.2.1 in addition to R Server 8.0.0. To facilitate this enhancement, in the Connections page, the R Server Version drop-down list box has been added to enable you to select the version of your R Server. | US314350 |
Reliability Analytics
Description | Tracking ID |
---|---|
Previously, when creating a new Risk record in System Reliability, if you saved the new Risk record multiple times, a Risk record was created each time that you selected the Save button (). This issue has been resolved. | DE96452 |
Reliability Centered Maintenance
Description | Tracking ID |
---|---|
To avoid timeout issues, in the Analysis Details workspace, Asset Strategy Management promotion is now a background operation. | DE97426 |
Rounds Data Collection
Description | Tracking ID |
---|---|
Previously, if you navigated away from and back to the workspace for a Route, and then closed the workspace for the Route after marking it done, the Route History record for the Route was deleted. This issue has been resolved. | DE99181 |
Previously, in the Rounds Data Collection Overview page, if you were disconnected from a network, Routes for which offline access was enabled did not appear when they became due. This issue has been resolved. | DE95420 |
Rounds Designer
Description | Tracking ID |
---|---|
Previously, in the Rounds Designer Overview page, in the Allowable Values section, if you modified the name of a category and selected Save, an error occurred. This issue has been resolved. Now, you can no longer modify the name or allowable values of a category. | DE97102 |
Thickness Monitoring
Description | Tracking ID |
---|---|
To enhance the data loading process for large amounts of data and to prevent the failure of data load batches that take longer than five minutes, the Thickness Measurement (TM) Equipment data loader and the Thickness Measurement (TM) Functional Location data loader have been enhanced. To facilitate this enhancement and to prevent timeouts, the TM Equipment Data Loader and the TM Functional Location Data loader now split large amounts of data into the following transaction scopes:
In addition to these default values, you can modify these transaction scopes if required. | US310233 |
V4.3.0.6.5
This topic provides a list of product changes included in this patch.
Family Policies
Description | Tracking ID |
---|---|
Previously, when you executed a policy that contained a Create Relationship node and a Create Entity node configured to create multiple records, the subsequent relationships were not created after the creation of the relationship between the first combination of records. This issue occurred if you specified one of the following inputs for the Create Relationship node:
|
|
Previously, if a policy contained a Math node with a variadic function, and the variables of the variadic function represented the columns of a collection, the validation and execution of the policy failed. This issue has been resolved. | DE94085 |
Previously, when you attempted to access a policy containing a large number of nodes, one of the following issues occurred:
| DE93538 |
Previously, if you mapped the time stamp output of a node to an input field of a successor node, and then executed the policy, in the Execution Details window for the successor node, the time stamp appeared in the time zone specified for your GE Digital APM user account instead of the policy time zone. This issue has been resolved. | DE91644 |
Foundation
Life Cycle Costing
Description | Tracking ID |
---|---|
To enhance accuracy in the Cost Data grid, when creating a new Resource for or adding an existing Resource to a Cost Element, the values in the Year <Number> columns (after the Year 0 column) now reflect estimations based on inflation. The escalated inflation values in the Year <Number> columns are based on the Annual Escalation Rate field in the Definitions section. | US256920 |
Policy Designer
Description | Tracking ID |
---|---|
Previously, when you executed a policy that contained a Create Relationship node and a Create Entity node configured to create multiple records, the subsequent relationships were not created after the creation of the relationship between the first combination of records. This issue occurred if you specified one of the following inputs for the Create Relationship node:
|
|
Previously, if a policy contained a Math node with a variadic function, and the variables of the variadic function represented the columns of a collection, the validation and execution of the policy failed. This issue has been resolved. | DE94085 |
Previously, when you attempted to access a policy containing a large number of nodes, one of the following issues occurred:
| DE93538 |
Previously, if you mapped the time stamp output of a node to an input field of a successor node, and then executed the policy, in the Execution Details window for the successor node, the time stamp appeared in the time zone specified for your GE Digital APM user account instead of the policy time zone. This issue has been resolved. | DE91644 |
Reliability Analytics
Description | Tracking ID |
---|---|
Previously, when viewing the Reliability Distribution Analysis Report for an analysis for which a PM Optimization had been performed, the values entered for the Planned Cost and Unplanned Cost did not appear in the report. This issue has been resolved. | DE93870 |
Previously, when creating a new Risk record in System Reliability, if you saved the new Risk record multiple times, a Risk record was created each time that you selected the Save button (). This issue has been resolved. | DE92376 |
To enhance analysis accuracy, when viewing the details of a Scenario in System Reliability, the following Distribution Types can now be selected for TTF and TTR Distributions in the Risks section and the Show Risk/Mitigated Actions grid:
| US271178 |
To enhance analysis accuracy, when viewing the details of a Spare Application in a Spares Analysis, the following Distribution Types can now be selected in the Update Distribution section:
| US271175 |
Reliability Centered Maintenance
Description | Tracking ID |
---|---|
To enhance usability and to allow you to incorporate related Failure Mode Asset ID values that make family records unique, you can now include the related Asset ID value of the Failure Mode family in the following worksheets of the Reliability Centered Maintenance (RCM) Data Loader:
| DE94412 |
Previously, if you tried to promote an RCM Analysis with multiple assets that contained recommendations, only the recommendations in the first asset were promoted. This issue has been resolved. | DE93758 |
Root Cause Analysis
Description | Tracking ID |
---|---|
Previously, in the Create Verification pane, if you selected a team member in the Assigned To drop-down list box, that team member did not receive email notifications when the assigned task was due or overdue because the scheduled email job was not properly executed. This issue has been resolved. | US291622 |
The values in the Alerts drop-down list box in the Add/Edit Tracking Items window are now populated with the Human Resource Record of the team members assigned to the specified RCA. | US254549 |
Rounds Data Collection
Description | Tracking ID |
---|---|
Previously, if you entered a reading value that satisfied a condition of a checkpoint other than the first condition, successor conditional checkpoints did not appear as expected. This issue has been resolved. | DE96113 |
Previously, if you marked a Route done in the Rounds Data Collection Overview page while the workspace for that Route was open, when you navigated back to the workspace for that Route, the Route reappeared in the Due Items or Overdue Items section in the Rounds Data Collection Overview page. This issue has been resolved. | DE92165 |
Previously, if you changed the GE Digital APM password for a user, and that user then performed a sync operation on a Windows Mobile device, the user was unable to sign in to the GE Digital APM mobile application on a Windows Mobile device with the new GE Digital APM password. This issue has been resolved. | DE88896 |
Rounds Designer
Description | Tracking ID |
---|---|
Previously, if you deleted a checkpoint that contained a successor conditional checkpoint, and then attempted to add the successor conditional checkpoint to a Route by selecting the Add button (), the conditional checkpoint did not appear in the Existing ML / LR window. This issue has been resolved. | DE93915 |
Risk Based Inspection
Description | Tracking ID |
---|---|
Previously, when you calculated an RBI Criticality Analysis for a Heat Exchanger Bundle component, the following incorrect validations were performed:
These issues have been resolved. Now, the following validations are performed:
| DE94266 |
Thickness Monitoring
Description | Tracking ID |
---|---|
Previously, if the number format of the user account that is used to run the Meridium Device Service is different from the number format of the English (United States) culture, when you received thickness measurement data from a TM Datalogger, the measurement values were incorrect. This issue has been resolved. | DE92436 |
V4.3.0.6.3
This topic provides a list of product changes included in this patch.
Asset Hierarchy
Description | Tracking ID |
---|---|
To resolve issues that resulted from a recent modification to the Asset Hierarchy, the Asset Hierarchy has been reverted to match the appearance and functionality that was available in the Q2 2018 release. Modules and features that use the Context Browser are unaffected. |
|
Policy Designer
Description | Tracking ID |
---|---|
Previously, if a policy was executed by a family-level rule or another GE Digital APM module multiple times within a short duration, the execution results for the Math and Text nodes were intermittently incorrect after the first execution. This issue has been resolved. | DE89726 |
V4.3.0.6.2
This topic provides a list of product changes included in this patch.
Asset Hierarchy
Description | Tracking ID |
---|---|
Previously, in the Asset Hierarchy, in search results, the full hierarchy path was not always displayed. This issue has been resolved. | US297538 |
Family Policies
Description | Tracking ID |
---|---|
Previously, if you did not update the memory cache after creating or deleting a family policy, the following issues occurred:
| DE91303 |
Previously, if you executed a policy that was configured to perform an action on a recently added, modified, or deleted family or family field, the execution failed even though you could successfully validate the policy. This issue has been resolved. | DE91301 |
Previously, in the Properties window, if you attempted to map a column of a query result to an input field, the drop-down list box to specify the column of the query result did not appear for the following nodes:
| DE90835 |
Previously, in the Properties window for the Create Relationship node, if you specified duplicate predecessor or successor entity keys to create multiple one-to-one relationships, and then validated or executed the policy, a validation error occurred for the node. This issue has been resolved. | DE89330 |
Policy Designer
Description | Tracking ID |
---|---|
Previously, if you executed a policy that was configured to perform an action on a recently added, modified, or deleted family or family field, the execution failed even though you could successfully validate the policy. This issue has been resolved. | DE91301 |
Previously, if you mapped the output of an AMS Asset, GE Tag, Health Indicator, or OPC Tag node to a Comparison node, and then mapped the logical result of the Comparison node to an And or Or node, validation and execution of the policy failed. This issue has been resolved. | DE90937 |
Previously, in the Properties window, if you attempted to map a column of a query result to an input field, the drop-down list box to specify the column of the query result did not appear for the following nodes:
| DE90835 |
Previously, in the Properties window for the Create Relationship node, if you specified duplicate predecessor or successor entity keys to create multiple one-to-one relationships, and then validated or executed the policy, a validation error occurred for the node. This issue has been resolved. | DE89330 |
Rounds Data Collection
Description | Tracking ID |
---|---|
Previously, when you collected data offline for all checkpoints on a Route and then closed the Route without marking the Route done, the progress bar in the Rounds Data Collection Overview page erroneously displayed a value less than 100%. Additionally, if you then marked the Route done, the Route History section in the workspace for the Route in the Rounds Designer module displayed a value that was one fewer than the actual number of readings taken. This issue has been resolved. | DE90935 |
Previously, when you marked a Route done while offline and then went online, the Route disappeared from the device, as expected, and readings were uploaded to the server; however, if you went back offline before the sync interval was met, the device storage was not updated, and the Route appeared in the Due section despite not being due. This issue has been resolved. | DE89050 |
Previously, on a small screen device, the percentage of the Route that was complete did not appear above the progress bar in the Rounds Data Collection Overview page when you were online. This issue has been resolved. | DE88164 |
Previously, on a mobile device, after you cleared Route data from local storage, Routes stored on your device resynchronized with the server, but, once the data was cleared, there was no indication that Routes were still synchronizing. As a result, if you went offline while the Routes were still synchronizing, you were unable to access any Routes that were not finished synchronizing. This issue has been resolved. Now, while Routes are synchronizing with the server, a spinner appears next to the Route names in the Due Items or Overdue Items section of the Rounds Data Collection Overview page, indicating that synchronization is in progress. | DE87172 |
State Management
Description | Tracking ID |
---|---|
In the State Assignments window, the following enhancements have been made:
| US287182 |