| Previously, a Recommendation generated while implementing an Action as an EAM maintenance plan contained an incorrect URL in the description. This issue has been resolved. | DE206193 |
| Previously, if using a PostgreSQL database, while updating an Action linked to an EAM Plan or a Plant Detail, an error occurred. This issue has been resolved. | DE206114 |
| Previously, in the Summary tab of a System Strategy, the Risk Profile graph was incorrectly displaying the Proposed values for each Asset Strategy. This issue has been resolved. Now, the Risk Profile graph displays the Proposed values correctly. | DE205233 |
| Previously, when you attempted to view the Risk card on the Risks and Actions page, the Strategy Mitigated Financial Risk values inaccurately displayed the Unmitigated Financial Risk values. This issue has been resolved. Now, the Risk card displays the Strategy Mitigated Financial Risk values correctly. | DE205232 |
| Previously, in the Strategy Summary tab, the Financial Risk graph was incorrectly displaying the Active and Unmitigated values as the same. This issue has been resolved. Now, the Financial Risk graph correctly displays the Active and Unmitigated values. | DE205231 |
| Previously, in the Risk Analysis tab, the Financial Risk graph incorrectly displayed a reduction in Risk without any modifications being made to the Asset Strategy. This issue has been resolved. Now, the Financial Risk graph on the Risk Analysis tab will only show an increase or decrease in Risk if changes are made to the Asset Strategy. | DE205230 |
| Previously, you could create a ASM Data Loader and a Secondary Actions with the same ID, this resulted in duplicate records. This issue has been resolved. | DE205114 |
| Previously, the Condition Monitoring Type field was not present on the RCM FMEA Recommendation Family and therefore could not be promoted to the corresponding field on the ASM Action. This resulted in an undesirable amount of manual rework to successfully run an ASO Analysis on an Asset Strategy. This issue has been resolved. Now, the Condition-Monitoring Type field has been added to the RCM FMEA Recommendation family. | DE203803 |
| Previously, when a non-super user attempted to apply a template as a master, the Apply Template window appeared displaying assets from only one site, though the user had access to assets from multiple sites. This issue has been resolved. Now, the Apply Template window displays assets from all the sites to which the non-super user has access. | DE204575 |
| Previously, if the ACA Analysis Checklist was created for a user configured with an English culture setting, the checklist displayed the wrong probability values for users with a Spanish culture setting. This issue has been resolved. Now, the probability values appear properly regardless of the user culture setting. | DE202862 |
| Previously, in the Implement Actions in Rounds Classic window, in the Create New from Template section, even after you applied a filter, the Filter Applied text did not appear. This issue has been resolved. | DE201858 |
Previously, Asset Strategies that were controlled by a master template displayed the Proposed Action and Risk data instead of the Active Action and Risk data. This issue has been resolved. Now, Asset Strategies that are controlled by a master template display the following data:- Active Actions
- Active Risk
In addition, the State of the Asset Strategy is now displayed as, Controlled by Master Template. It also contains the name and link to the master template. | DE200669 |
| Previously, if the risk threshold values configured in the Risk Matrix were very low with small differences between them, the risk bar displayed on the Risks and Actions screen did not appear correctly. This issue has been resolved. | DE200527 |
| Previously, when going back and forth using the Previous and Next buttons in the Apply Template window, the Next button was disabled and the Apply Method page was not refreshed. This issue has been resolved. | DE198863 |
| Previously, if you attempted to import a General Task List from SAP that did not have a value in the ‘Changed Date’ field, an error occurred. This issue has been resolved. Now, you can import General Task Lists from SAP even if the ‘Changed Date’ field is blank. | DE197786 |
| Previously, even if an Asset Strategy was in the Pending state, you could modify it using the datasheet. This issue has been resolved. Now, you cannot modify an Asset Strategy in the Pending state using either the datasheet or the Asset Strategy Management (ASM) Data Loader. | DE197287 |
| Previously, the criticality value for the asset did not appear in a strategy record sometimes. This issue has been resolved. | DE195771 |
| Previously, while implementing an action as a Calibration Task, if the same task ID existed in the system, an error occurred. This issue has been resolved. Now, in this scenario, a unique task ID is generated. | DE194120 |
| Previously, a Strategy ID containing commas did not align with the heading in .CSV files while implementing an action as EAM maintenance plan. This issue has been resolved. | DE193700 |
| Previously, if you attempted to modify an approved Recommendation, an error occurred. This issue has been resolved. | DE190840 |
