August 2025 Patch
Release Notes for ServiceMax Core August 2025 Patch — August 29, 2025
Enhancements
Case Number
Internal Defect
Description
Feature
Fixed Version
00173963
064664
Issue: Previously, users could not launch standard Salesforce record pages (such as Account or Location) with pre-defined field values through a Custom Action URL. Users manually entered information, which increased effort and led to inconsistencies across records.
Resolution: Administrators can now configure a Custom Action URL to launch standard Salesforce record page with pre-defined field values. In the Custom Action configuration, admins must append “?defaultFieldValues=” to the record page URL and define field parameters. This automatically populates default values for new records, reducing manual data entry and ensuring consistency.
SFM Custom Actions
24.20000.46,
25.10000.34
00172926
064087
Issue: Previously, the SFM Delivery engine blocked creating duplicate records, even when the Salesforce Duplicate Rule was set to warn and allow save.
Resolution: The SFM Lightning Delivery now enforces Salesforce Duplicate Rules for SFM header records. To enable this, set SET013 (Module: SFM Transaction Manager; Submodule: SFM Transaction Delivery Engine) to True. When this setting is enabled and a duplicate is detected, the SFM Delivery Engine displays an error message. On clicking Save again, the record is saved if the rule is set as a warning. If it is a blocking error, the same error message is shown and the record is not saved.
* 
Duplicate Rules are enforced only for the SFM header record.
For child records, the SFM Delivery Engine always blocks duplicate records, even if the rule is configured as a warning.
This setting is supported only in Web SFM Lightning Delivery (React-based delivery).
SFM Delivery
24.10000.54,
24.20000.46,
25.10000.34
00170983
063689
Issue: Previously, in the Manage Work Order Lines – Usage SFM, labor and parts prices did not populate from the selected price book when users clicked the Get Price button. This occurred when users changed the Parts Pricebook or Labor Pricebook on the SFM layout. The updated prices appeared only after clicking the Get Price a second time. This led to inaccurate price calculation and delayed work order completion.
Resolution: The pricing engine now reads the latest Parts and Labor Pricebook values from the Work Order’s price book fields on the SFM layout when the user performs the Get Price action. If the fields are not available, the engine fetches the last saved price book values from the Work Order record.
For more information, see Initiating Price Calculation.
Get Price-Work Order
24.20000.46,
25.10000.34
00174734
064593
Issue: Previously, deleting a covered product from a Service Contract did not clear Service Contract Name, Service Contract Line, Contract Start Date, and Contract End Date fields from the Installed Product record. As a result, the Installed Product displayed outdated contract details.
Resolution: Administrators can set the global setting GBL014 to automatically clear the Service Contract Name, Service Contract Line, Contract Start Date, and Contract End Date fields from the Installed Product record when the covered product is removed from the Service Contract.
This keeps the Installed Product record accurate and helps users avoid confusion from outdated contract details.
Service Coverage
24.20000.46,
25.10000.34
NA
NA
Administrators can now add images for parts or products, which are displayed in the replacement modal. This provides end users with a visual reference when selecting replacement parts, helping to improve accuracy and streamline the replacement process.
Product Structure
25.10000.34
NA
NA
Automated AI Actions through Service Flow Automation (SFA) allows AI-driven actions, such as Summarize Work Order, to be triggered automatically based on SFA configuration during record creation or update. The output of these AI actions is stored in a designated field, such as a custom Work Order Summary field, making it easy for users to access and review the generated summaries. For more information, see Configuring Automated AI Actions in Service Flow Automation.
* 
For Work Orders, the same existing field set (SFA Fields) is used to monitor changes as compared to field set (SFA AI Action) in 25.1.
For Case, Installed Product and Location, use the sample trigger code published as part of SFA feature to use AI Actions. Admins must update this code to add only those relevant fields whose change must result in AI Action. Admins must update this code to include only the relevant fields whose changes should trigger an AI Action.
ServiceMax AI
24.20000.46
Defects Fixed
Case Number
Internal Defect
Description
Feature
Fixed Version
00174390
064651
The PDF generation error occurred when the user switched from the old editor to the new editor and tried to generate the output document. This issue occurred because the Script tag was not supported by default in the new editor.
SFM Designer
24.20000.46,
25.10000.34
00175283
064756
The user was unable to view and clone an expression in the Criteria section of a PM Process.
Preventive Maintenance
25.10000.34
00175464
064816
The PM Process engine failed to process all PM Plans in a batch if one PM Plan failed. The error summary logs lacked specific details, so admins could not troubleshoot PM Plans and Schedules.
Preventive Maintenance
25.10000.34
00175398
064804
An error occurred when the user tried to save a new PM Process.
Preventive Maintenance
25.10000.34
00174163,
00170896
063679
When the customer license type changed from Rapid to Enterprise, the Expression Detail records specific to the Rapid License were deleted and Sync Gateway failed to complete sync.
ServiceMax
24.20000.46,
25.10000.34
00173673
064338
The output PDF displayed an unwanted 'undefined' string for child line details.
Recommendation: It is recommended to update the document template expression to include a null check, ensuring missing labor details are handled properly and 'undefined' does not appear in the generated report.
SFM Delivery
24.20000.46,
25.10000.34
00173863
064650
Installed Product fields were incorrectly updated when new covered products were created. All installed products were linked to the same contract and covered product instead of their respective ones.
Service Coverage
24.20000.46,
25.10000.34
Was this helpful?