V4.3.0.7.19 Release Notes

V4.3.0.7.19

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

Asset Strategy Optimization

Table 1. Resolved IssuesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
Previously, if you promoted a Reliability Centered Maintenance (RCM) analysis or Failure Modes and Effects Analysis (FMEA) to a strategy, and then attempted to optimize the actions of the strategy, the optimization of the actions took longer than expected. This issue has been resolved.DE150356

Production Loss Analysis

Table 2. Resolved IssuesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
Previously, screen failed to render on certain devices or zoom settings. This issue has been resolved. To reduce the risk of the screen failing to render on certain devices or zoom settings, the settings for PLA have been modified to accept small screen devices.DE150060
Previously, even though Production Plan Records for the same unit and start time were available in multiple culture settings, you could create duplicate plans and no warning message appeared. This issue has been resolved for Time Based Plans that were not created as manual plans.
Note:
  • This fix is not applicable to Manual Plans.
  • For Quantity-Based Plans (Sequential or Concurrent), duplicate check is additionally applied on Original Quantity.
  • For Quantity-Based Plans (only Concurrent), sequence of the product should be same when using data loader.
DE149759

Queries

Table 3. Resolved IssuesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
Previously, certain queries that contained parameter prompts and referenced other queries would unnecessarily recompute parameter values. This issue has been resolved. Now, parameter values are only recomputed when needed.DE151796
Previously, when you attempted to select a query prompt value in the prompt filter, the prompt values intermittently took longer than expected to appear and there was no indication that the operation of loading the values was in progress. This issue has been resolved. Now, a spinner appears when the values are being loaded.DE150574
Previously, when you exported a query using the CASTNUM and ROUND functions to an Excel file, the numeric values were exported as text. This issue has been resolved.DE149973

RBI 581

Table 4. Resolved IssuesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
Previously, the Calculated T-min field on 581 Risk Analyses was calculated incorrectly when Geometry Type field value was Spherical Head or Hemispherical Head. This issue has been resolved. Now, the Calculated T-min field on 581 Risk Analyses is calculated using the updated formula. For more information about the formula, refer to KBA 000037009.DE149233

Root Cause Analysis

Table 5. Resolved IssuesThe following issues, which existed in one or more previous versions, have been resolved.
DescriptionTracking ID
Previously, in RCA Recommendations, the fields did not appear in the language based on your language settings. This issue has been resolved.DE148760
Previously, in the Preserve Records section for a Root Cause Analysis, some of the fields were not translated based on the Language setting for your user account. This issue has been resolved.DE141652
Previously, in the Team Members section for a Root Cause Analysis, some of the fields were not translated based on the Language setting for your user account. This issue has been resolved.DE137975