|
Case Number
|
Internal Defect
|
Description
|
Feature
|
Fixed Version
|
|---|---|---|---|---|
|
00174007
|
064508
|
Issue — The Standard Maintenance Plan Process in Asset 360 Admin did not run consistently. While it sometimes executed successfully, it frequently failed with errors related to heap size and oversized batchable instances. The issue was linked to excessive detailed logging and high CPU usage, which caused instability during long-running processes.
Resolution — The fix introduced two improvements:
• disabling detailed logging to significantly reduce heap consumption
• applying CPU-time optimizations, including query refinements in record type mappings, to streamline execution
Customers were required to contact ServiceMax Support to disable detailed logging via the following configuration details:
• Custom Setting Object: Global Properties
• Name: GP805
• Key: COMMON_ORG_SETTINGS
• Value: True (default)
For more information, refer to Maintenance Plan Processing Data Volume Recommendation.
|
A360 Maintenance Plan Process
|
12.0
|
|
Case Number
|
Internal Defect
|
Description
|
Feature
|
Fixed Version
|
|---|---|---|---|---|
|
00174279
|
064675
|
When the Preventive Maintenance Plan process finished running in Asset 360, the expected Application Log was not attached to the Maintenance Plan Completion Log. After reviewing the related records for the process run, no Application Log entries were found, leaving users without the necessary execution details.
|
A360 Maintenance Plan Processing
|
12.0
|