Previously, if your culture setting was not English, when you accessed the checklist inspections for pre-defined API checklists or configured checklist templates, the values in the Name and Category fields of the Checklist Finding records were not translated to the language based on your culture setting. This issue has been resolved. | DE116950 |
Previously, if the Inspection ID field of an Inspection Event contained special characters, which were not supported by Windows operating system for a file name, you could not bulk-print the Inspection Event from the Inspection Management Overview page. This issue has been resolved. | DE114406 |
Previously, for the Inspection Task record that did not contain an Inspection Document Type, when you selected a link in the CREATE INSPECTION column in the Results section of the query associated with the Underlying Inspection Tasks section, an error message appeared. This issue has been resolved. Now, in this scenario, a window appears to prompt you to select the Inspection Document Type for the record. | DE113031 |
Previously, when you switched from the Bulk Review Inspections workspace to a different tab or page, and then returned to the Bulk Review Inspections workspace, you could not approve the Inspection records. This issue has been resolved. | DE111741 |
Previously, even if the Keep History check box was selected for a field in the Inspection Task family, you could not access the history of the field in an Inspection Task. This issue has been resolved. | DE110746 |
Previously, in the Inspection Data section of the Full Inspection: <Inspection ID> workspace for an inspection, if you updated a master/detail datasheet that was created for the Full Inspection family, and then attempted to save the datasheet, two spinners appeared, indicating that the data was being updated for the inspection. This issue has been resolved. Now, in this scenario, only one spinner appears. | DE104168 |
Previously, when adding items to a Checklist Configuration template, when you searched for and added an item to the template, the item was successfully added. However, when you searched for a second item, it did not appear in the search results, even if it was available in the list of items. This issue has been resolved. | DE101414 |
Previously, you could modify the site assigned to the Resource Role records because the Resource Role family was enabled for site filtering. When the site assigned to a Resource Role for a given user was modified, the name of that user did not appear in the drop-down list boxes in the respective datasheets. This issue has been resolved. Now, the Resource Role family is no longer enabled for site filtering and the user names appear correctly. Note: The fields containing the user names will continue to be filtered based on the site to which the respective record is assigned. | DE91540 |
Previously, for an Inspection Profile, in the Inspection Profile Details section, if the Item ID box contained a special character, APM could not automatically generate the General Finding report that was based on the associated Inspection Scope. This issue has been resolved. | DE83319 |
Previously, when you used the IM Functional Location Data Loader to load Inspection Methods, if the Inspection Methods did not have a Method Category defined in the data loader, subsequent Inspection Methods that shared an Inspection Profile did not load. This issue has been resolved. | DE82397 |