| Previously, when you attempted to save a checklist inspection report that contained edits to multiple categories of checklist findings, an error occurred, and certain findings were not saved. This issue has been resolved. | DE142898 |
| Previously, for Inspection Tasks created as part of the work management interface with EAM as the master, the Task Type field was disabled. This issue has been resolved. | DE141999 |
| Previously, when there were multiple Taxonomy Classes or Types for the same category, Taxonomy Configurations were not correctly displayed in the IM Admin Preferences workspace. This issue has been resolved. | DE140172 |
| Previously, the Inspection Task Complete field was disabled for Team Members assigned to Checklist Inspection families. This issue has been resolved. Now, Team Members assigned to Checklist Inspections can set the Inspection Task Complete field. | DE136020 |
| Previously, when you selected the Inspection Lock check box, the Reviewers Name field was disabled and another Reviewer was unable to modify the field or assign a different Inspection Reviewer to approve the Inspection. This issue has been resolved. Now, the Reviewers Name field is enabled for all reviewers. You can also assign a different Reviewer to approve the Inspection. The Reviewers Name field is disabled only when the Final Inspection Lock field is selected. | DE133983 |
| Previously, the Checklist Has Finding (MIR_CHKHSFDG) relationship family did not have a baseline business rule. Due to this, you received an error when you attempted to inherit the Library.Baseline.MIR_CHKHSFDG.MIR_CHKHSFDG rule in your custom project. This issue has been resolved. | DE132960 |
| Previously, in the Asset Hierarchy, when you selected an asset, and then selected the Integrity tab, the link for Inspection Management took longer to load, depending on the number of assets in the Asset Hierarchy. This issue has been resolved. | DE132867 |
|
Previously, when you downloaded inspections in bulk from the Inspection Field Data Collection Overview page along with the inspection history report, no warning message appeared even if the SQL Server Reporting Services were not configured. This issue has been resolved.
| DE132733 |
| Previously, when an Inspection event was created for an Asset for which Equipment profiles were defined and sequenced, the automatically generated General Finding records were not arranged in the order of the values in the assigned Sequence field. This issue has been resolved. Now, the Equipment Profiles in General Finding records are arranged in the same order in which they were sequenced in the Inspection Profile Details. | DE132290 |
