| Previously, when running the Work Management Adapter job for a new Maintenance Plan that was importing a Task List into APM for the first time, the system created a revision that was marked as Discontinued. This issue has been resolved. Now, the revision is not created. | DE85219 |
| Previously, when a job attempted to load data that exceeded the limit set in the threshold parameters in the context file, the job failed even when OVERRIDE_GUARDRAILS was set to Y. This issue has been resolved. Now, APM Connect correctly indicates that the job failed because you did not configure an SMTP server for email notifications and that the threshold has been exceeded. | DE83177 |
| Previously, if you ran the Functional Location Adapter that defines a Functional Location record (for example, FL02) that references a nonexistent Superior Functional Location record (for example, FL03), APM created a record for the Superior Functional Location. If you again ran the Functional Location Adapter that defined the previously created Superior Functional Location, APM created a duplicate Functional Location (FL03) record. This issue has been resolved. Now, the second run of the Functional Location Adapter updates the previously created Functional Location record. | DE82574 |
| Previously, in a cloud environment, Failure records for the First Extract and Load jobs were left on the client side after the Failure records were correctly processed. This issue has been resolved. Now, after the Failure records are correctly processed, they are removed from the client side. | DE80528 |
| Previously, when you deleted the last Task List from an SAP Maintenance Plan and ran the Work Management Adapter job, APM did not synchronize the tasks. This issue has been resolved. Now, the tasks are removed correctly. | DE80440 |
| Previously, in a Multi-EAM environment, APM used the Default EAM System ID when attempting to link a Task List or Work Order to an Inspection Task record. This issue has been resolved. Now, the EAM System defined by the related asset is used when retrieving Task List data. | DE80014 |
| Previously, if you removed all the Classes and Characteristics from an Equipment or Functional Location in SAP, the APM Technical Characteristics was not synchronized. This issue has been resolved. Now, APM Connect sends any Technical Characteristics data from SAP that needs synchronization. | DE80009 |
| Previously, if a Work History record was created from a Notification, values were not populated in the class description fields. This issue has been resolved. Now, the system correctly updates the class description fields. | DE76486 |
