May 2025 Patch
Release Notes for ServiceMax Asset 360 May 2025 Patch
Release Date: May 30, 2025
Enhancement
|
Case Number
|
Internal Defect
|
Description
|
Feature
|
Fixed Version
|
|---|---|---|---|---|
|
00170120
|
063333
|
Issue — The issue occurred when executing the Maintenance Plan Process using a maintenance plan that contained over 15 rules. Despite multiple rules meeting their condition-based, frequency-based, or time-based criteria, only one work order was generated. This work order appeared only after a rule was modified to evaluate as false and the process was re-run. Each time the process was executed, other valid rules that should have triggered work order generation did not, indicating a failure in handling multiple qualifying work rules during the plan execution.
Resolution — The sort order feature is enhanced to support multiple scenarios depending on the values. The updated use cases are as follows:
• If the sort order is blank, work orders are generated for all qualified rules.
• If the sort order is defined, a work order is generated for a single qualified rule.
• If multiple work rules share the same sort order value, work orders are generated for all qualified rules with that same sort order while still adhering to the overall sort order logic.
For more information, refer to Define Work Rule Template.
|
A360 Condition-Based Maintenance Plan
|
12.0
|
Defects Fixed
|
Case Number
|
Internal Defect
|
Description
|
Feature
|
Fixed Version
|
||
|---|---|---|---|---|---|---|
|
00166179
|
062108
|
The issue occurred in the Service Console FSI app within the users’ org when users accessed a PSC record and clicked Manage. Although all records were displayed correctly, the page continued to show a loading indicator. This misleading behavior caused confusion, as it appeared that the page had not fully loaded despite the data being visible.
|
A360 Product Service Campaign
|
12.0
|
||
|
00167416
|
062799
|
The issue occurred on the Asset page in Asset 360 when users attempted to open the warranty term under asset coverages. A component error appeared due to a failure triggered by the asset hierarchy configuration using an expression. Specifically, the error was caused by an undefined getBoundingRect function. This was a regression defect introduced by the PSC search expression builder enhancement in version 12.0.
|
A360 Asset Management
|
12.0
|
||
|
00172109
|
063806
|
The issue occurred after the Summer '25 upgrade when opening the Asset 360 Admin Page, which resulted in a component error. This was caused by Salesforce's update to the Lightning Tree component that introduced stricter validation for the href attribute, requiring a properly formatted URL string. Previously, the setup page used the current page reference object to set the href for parent nodes, which worked without issue. However, with the new sanitization logic in place, this method no longer met the validation criteria, causing the component to fail.
|
A360 Admin Setup
|
12.0
|
||
|
00172071
|
||||||
|
00172214
|
||||||
|
00172052
|
||||||
|
00172117
|
||||||
|
00172024
|
||||||
|
00172195
|
||||||
|
00172155
|
||||||
|
00172205
|
||||||
|
00172041
|
||||||
|
00172007
|
||||||
|
00172064
|
||||||
|
00172031
|
