Previously, when you attempted to send criticality values in a batch to SAP, only errors were logged with the success and failure count of the assets. This issue has been resolved. Now, you can view the results of the criticality values that are successfully sent to SAP. | US381408 |
Previously, when you accessed the ACA Overview page, the data took longer than expected to load. This issue has been resolved. | DE124940 |
Previously, even though the number of team members associated with an Asset Criticality Analysis (ACA) was more than 20, you could view a maximum of 20 team members in the Team Members section until you added a team member to the ACA team. This issue has been resolved. | DE122640 |
Previously, when multiple send to SAP jobs were running, the analysis did not track the correct job. This issue has been resolved. | DE121671 |
Previously, if you attempted to import an Asset Criticality Analysis record for an asset that did not exist in Predix Essentials, an incorrect error message appeared in the error log. This issue has been resolved. Now, an appropriate error message appears, indicating that the asset does not exist in Predix Essentials. | DE120766 |
Previously, if you changed the state of an Asset Criticality Analysis, if you modified a value in the Analysis Definition section, and then attempted to save the datasheet, an error occurred. This issue has been resolved. | DE120765 |
Previously, when a criticality mapping was linked to an EAM, if you attempted to send the criticality indicator to an EAM system other than the target EAM system, an error occurred. This issue occurred only if you had multiple EAM systems. This issue has been resolved. Now, an appropriate error message appears. | DE115402 |
Previously, when you saved a new analysis, duplicate requests were created. This issue has been resolved. | DE108892 |