Release Information > Release Notes > Core Feature Progression > Core Patch Releases > Patch Releases - 2025 > May 2025 Patch
May 2025 Patch
Release Notes for ServiceMax Core May 2025 Patch — May 30, 2025
Defects Fixed
Case Number
Internal Defect
Description
Product/ Feature
Fixed Version
00170290
063322
The multi-source SFM was not linked to the SFM when it was migrated via the global deploy command.
Tools
24.10000.48,
24.20000.33
00170292
063474
An error occurred when the number of tags exceeded the Salesforce's query limit during the migration of a DataGuide form and its associated tags.
Tools
NA
00170584,
00169767,
00169466
063471,
063059
An error occurred during the migration of an SFM transaction when the transaction with the same name already existed in the target org.
* 
The 063059 defect was fixed and released on May 10, 2025.
Tools,
ServiceMax
24.10000.48,
24.20000.33
00170872
063505
The expressions failed to map after an SFM transaction was migrated to the target org via the CLI tool.
* 
This defect was fixed and released on May 10, 2025.
Tools
24.10000.48,
24.20000.33
00165767
063176
Transactions configured with a button in the Page Properties or Page Layout sections with no elements were not retrieved via the CLI command.
Tools
24.10000.48
00171763
063737
The expressions were not retrieved in bulk after the new ServiceMax plugin was installed via the CLI tool.
* 
This defect was fixed and released on May 10, 2025.
Tools
24.10000.48,
24.20000.33
00171764
063738
An error occurred when the user tried to retrieve transactions after the patch upgrade via the CLI tool.
* 
This defect was fixed and released on May 10, 2025.
Tools
24.10000.48,
24.20000.33
00171166
063599
The SFM Wizard Expressions field values were displayed as False in the Lightning version, even when they were marked as True in the Salesforce Classic mode.
ServiceMax
24.20000.33
00165712
062142
Changing the contract type in the SFM did not clear the associated PM Plan Template field as expected. Specifically, when the contract type was changed, the PM Plan Template field appeared to be cleared initially. However, after saving, the field retained its old value. This behavior was triggered from a failure in the before-save web service or code snippet, where form fill values set to null were not correctly updated during the save operation.
SFMD React
24.10000.48,
24.20000.33
00170264
063321
The issue occurred when users attempted to upload an image to the Response Description field within the SFM. When an image larger than 3 MB was uploaded, a generic error message appeared. After clearing the ServiceMax cache and uploading an image between 1 MB and 3 MB, a different error message was displayed.
SFMD React
24.10000.48,
24.20000.33
00171164
063574
The issue occurred in the Debrief SFM when users added a new part line under the Parts tab. After selecting the product and saving, a new line appeared with blank Part In and Part Out fields. When the IP Configuration field was populated, the Part Out field was automatically filled through FormFill. Despite this, a validation error was immediately triggered, incorrectly indicating that the Part Out field was blank.
SFMD React
24.20000.33
Was this helpful?