V4.3.1.0.2 Release Notes
V4.3.1.0.2
This topic provides a list of product changes included in this patch.
Action Management
| Description | Tracking ID |
|---|---|
| Previously, when you created a notification from a General Recommendation, the Work Request Reference field was not populated even if the Create EAM Notification? check box was selected. This issue has been resolved. | DE121169 |
Asset Strategy Management
| Description | Tracking ID |
|---|---|
| Previously, when importing actions from rounds, an error occurred when you tried to view the Route. This issue has been resolved. | DE121075 |
Asset Strategy Optimization
| Description | Tracking ID |
|---|---|
| Previously, under certain conditions, if the simulation stopped while saving results back to ASM, you could not cancel the simulation. This issue has been resolved. Now, you can cancel the simulation at any point in the process. | DE122729 |
| Previously, while accessing the grid view, some of the fields did not appear until the field values were changed back and forth. This issue has been resolved. | DE122728 |
Family Policy
| Description | Tracking ID |
|---|---|
| Previously, if you configured a Last, Min, or Max node to operate on the output collection from a Sub Policy node, and mapped the output of the Last, Min, or Max node to another node and saved the policy, when the policy was reloaded in the Design workspace, the mapping was lost. This issue has been resolved. | DE121181 |
Inspection Management
| Description | Tracking ID |
|---|---|
| Previously, the Inspection Management Overview page was filtered based on the asset hierarchy context, despite providing the unit key in the Uniform Resource Locator (URL). This issue has been resolved. Now, the Inspection Management Overview page is filtered based on the unit key you provide. | US376669 |
| You can now manage API RBI Recommendations in the Inspection Plan page for the asset. The Inspection Plan page of the Compliance Management module now supports viewing, managing, approving, and implementing API RBI Recommendations. In addition, the Inspection Plan Management page now supports managing Inspection plans with API RBI Recommendations in bulk. To facilitate this enhancement, you must follow the steps in KBA: V4.3.1.0.2 – Compliance Management – How to Configure API RBI Recommendations for Inspection Plan. Note: If you had previously performed a similar KBA for the V4.3.0.7.8 release, you must still perform the steps in the KBA for the V4.3.1.0.2 release and ensure the attached queries are imported. | US373707 |
Policy Designer
| Description | Tracking ID |
|---|---|
| Previously, if you updated the schedule settings for a policy with an existing schedule and saved the policy, the updated schedule settings were not applied. This issue has been resolved. | DE122328 |
| Previously, if you configured a Last, Min, or Max node to operate on the output collection from a Sub Policy node, and mapped the output of the Last, Min, or Max node to another node and saved the policy, when the policy was reloaded in the Design workspace, the mapping was lost. This issue has been resolved. | DE121181 |
| Previously, the policy execution service processing the notifications was limited by the maximum number of concurrent WCF connections. This issue has been resolved. Now, the policy execution service is configured to allow up to 32768 concurrent WCF connections by default. | DE120993 |
RBI 580
| Description | Tracking ID |
|---|---|
| Previously, if an RBI Criticality Analysis contained a Chloride Stress Corrosion Cracking (CI SCC) or Hydrogen Stress Cracking (HSC) - Hydrofluoric Acid Degradation Mechanism, the value in the output fields were incorrectly calculated. This issue has been resolved. | DE121801 |
RBI 581
| Description | Tracking ID |
|---|---|
|
Previously, when the UOM conversion set was assigned to you, while calculating an RBI 581 Risk Analysis, the Risk Category field was calculated incorrectly. In addition, the output fields were calculated incorrectly for any of the following conditions:
This issue has been resolved. | DE121779 |
Rounds Data Collection
| Description | Tracking ID |
|---|---|
| The APM Mobile application editing has been enhanced to ensure the route readings in the database are synchronized with the application server before removing the data from the device. Additional logging has been added to track the synchronization activity between the APM Mobile device and the APM Application server. | DE122634 |
Thickness Monitoring
| Description | Tracking ID |
|---|---|
| When performing bulk analysis from the Assets section of the Thickness Monitoring Overview page, you can now choose to analyze all assets or only the assets that require calculation. | US380458 |
| Description | Tracking ID |
|---|---|
|
Previously, when you calculated an asset corrosion analysis in Thickness Monitoring where the Maximum Allowable Working Pressure (MAWP) was calculated for the Thickness Measurement Locations, the following error was logged in the application log file even though the calculation of the MAWP was successful: System.Xml.XmlException: Root element is missing This issue has been resolved. | DE122427 |
| Previously, when you performed the Minimum Thickness (T-Min) calculation for more than 400 thickness measurement locations from the T-Min Calculator workspace, an error occurred. This issue has been resolved. Now, a pagination has been introduced to the T-Min Calculator workspace to load 100 thickness measurement locations per page. | DE121542 |