Previously, when you applied a template to an Asset Strategy, new Risk IDs and Action IDs were not generated. This issue has been resolved. | US337882 |
Previously, if you were assigned to the MI ASM Viewer Security Group, you could create or modify the records of some families. This issue has been resolved. Now, the MI ASM Viewer Security Group has been modified to remove the insert and update privileges for the applicable families. | US335762 |
Previously, in the Asset Strategy Approval report, the labels of axes in the graph were not generic. For example, by default, the labels for currency and risk axes were $ and Risk Rank, respectively. This issue has been resolved. | US333482 |
Previously, you could modify the value in the Plan Length field of the Asset Strategy record that was in the Pending Review state. Consequently, you could also modify the record. This issue has been resolved. Now, the Plan Length field of the Asset Strategy record that is in the Pending Review state is disabled. | US305127 |
Previously, when you implemented an Action as an EAM Maintenance Plan, and then exported the record in a CSV format, the value in the Description field of the Action incorrectly appeared in the exported file. This issue has been resolved. | DE117099 |
Previously, if your culture setting was Japanese, when you accessed the Review Strategy workspace for a Unit Strategy, no values were populated in the State and Operations drop-down list boxes. This issue has been resolved. | DE114831 |
Previously, the Mitigated Financial Risk for an asset was incorrectly calculated. This issue has been resolved. | DE114245 |
Previously, actions generated by applying a template to a Strategy were not linked to the EAM Plan and EAM Plan Details records. This issue has been resolved. | DE113906 |
Previously, for a Risk sourced from the Risk Based Inspection module, in the Risks and Actions section, you could modify the Unmitigated Risk values. This issue has been resolved. | DE112872 |
Previously, you could not activate the Asset Strategy template that had a custom state between the Pending Review and Active states and had controlled strategies. This issue has been resolved. Now, you can transition the template from a custom state to the Active state. | DE112836 |
Previously, if your culture setting had a culture other than English, and you accessed the Review Strategy workspace for a system or unit strategy, the following drop-down list box captions were not translated to the language based on your culture setting.This issue has been resolved. | DE108776 |
Previously, if you used a localization setting other than English, and then attempted to modify the state of a System or Unit Strategy in the Review Strategy workspace, an error message appeared. This issue has been resolved. | DE108015 |
Previously, in the Implement Actions section of the Strategy Details page, an irrelevant button, Send to ASI Package ( ), was available. This issue has been resolved. | DE105294 |
Previously, when you attempted to apply a template as a master strategy template to an Asset Strategy, an error occurred if the template was created using a strategy with risks or actions sourced from other modules. This issue has been resolved. | DE95408 |
Previously, in the Risks and Actions sections of the ASM Overview page, some of the column headings were not translated. This issue has been resolved. | DE93789 |
Previously, when using Internet Explorer, in the Strategy Details page, if you attempted to access the Review Strategy workspace, an error message appeared. | DE88696 |