|
Case Number
|
Description
|
|---|---|
|
NA
|
The AI Actions SFM Wizard Step is available to add for the Work Order object.
For more information, see Adding AI Action SFM Wizard Step.
|
|
00152183
|
Issue: Auto Entitlement for Work Order did not support entitlement covered through Product, Product family or Product line.
Resolution: A new rule is added to the Work Order Entitlement rules: Should product, product family and product line (in that order) be included in Entitlement Check for Service Contracts. For more information, see Entitlement Settings for Work Order.
|
|
00161244
|
Issue: In Condition-Based PM Plans, the configured Threshold % value in the Condition-Based PM Template was not applied to each milestone of the condition rule. Instead, only the frequency was considered when generating the PM schedule.
Resolution: A new setting, SET005 has been introduced that enables you to apply the configured Threshold % value to each milestone of the condition rule that got adjusted via dynamic adjustments. As a result, PM schedules are now calculated based on both the Threshold % and dynamic adjustments, ensuring that PM Work Orders are created in alignment with the updated PM schedule.
For more information, see Applying Threshold Percentage for Condition-Based PM Plans based on Dynamic Adjustments.
|
|
NA
|
The product name for ServiceMax’s AI-powered assistant is changed from ServiceMax Copilot to ServiceMax AI.
For more information, see ServiceMax AI.
|
|
NA
|
The ServiceMax AI Console is accessible from ServiceMax Setup screen.
For more information, see ServiceMax AI.
|
|
NA
|
Issue: The Chevron icon was displayed for installed products with no child records in the IB Hierarchy tree view.
Resolution: The Chevron icon is not displayed for nodes with no child records. For more information, see Installed Base Hierarchy for End Users.
|
|
Case Number
|
Description
|
|---|---|
|
00167529
|
Issue: Document Templates linked via form actions were implicitly migrated when a DataGuide Form was migrated from source to target org. This caused unintended overwrites when the Document Template already existed in the target org.
Resolution: The Document Template will not be overwritten in the target org when a DataGuide Form is migrated from source to target and the associated Document Template exists in the target org. Instead, it will be linked to the migrated form if not already linked.
To migrate Document Template changes, it is recommended to select the Document Template during migration.
This validation also applies to the SFM Wizard during dependant form migration.
For more information, see DataGuide Configurations.
|
|
Case Number
|
Description
|
|---|---|
|
00170316
|
Issue: Users could not disable the bulk action in SFM.
Resolution: A new global setting, SET012 has been introduced to enable/disable bulk action. When this setting is set to true, the bulk update child lines and bulk delete child lines action are disabled for users on the Lightning SFM Delivery. For more information, see Editing Child Lines and Deleting Child Lines.
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00163702
|
The Technician Search box was incorrectly placed in the Dispatch Console Scheduler section.
|
January 2025 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00168201
|
The Batch Optimization job failed due to an unexpected character error when the SB shift was enabled in the SFDC org with a specific SB tenant.
|
March 2025 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
||
|---|---|---|---|---|
|
00159110
|
The Warranty Start Date and Warranty End Date fields on the Installed Product were not populated when the Date Installed on IB was a future date.
|
December 2024 Patch
|
||
|
00161356,
00160004,
00163513,
00161287
|
Multilevel mapping did not work when the user launched the SFM.
|
December 2024 Patch
|
||
|
00162017
|
The error was displayed when the user updated the Technical Attributes fields on the Installed Product record.
|
December 2024 Patch
|
||
|
00163529,
00163363
|
The error was displayed when the user opened Wizard Criteria from the Wizard step.
|
December 2024 Patch
|
||
|
00152227,
00151551
|
When the Immediate type Dispatch process is loaded with high volume assignment rules, the user experienced performance or lagging issues.
|
December 2024 Patch
|
||
|
00161287,
00160004,
00161356,
00163513
|
Multilevel mapping did not work as expected when the SFM was launched.
|
January 2025 Patch
|
||
|
00166705
|
An error message was displayed when Wizard Criteria from a Wizard step was opened.
|
January 2025 Patch
|
||
|
00163806
|
The pop-up was not displayed when the user clicked on an icon in the Timeline.
|
January 2025 Patch
|
||
|
00164342,
00164842
|
A redirection error was displayed when the community user tried to navigate after generating the service report.
|
January 2025 Patch
|
||
|
00165883
|
The double quotes were not displayed as expected in the error message.
|
January 2025 Patch
|
||
|
00167957
|
In classic mode, an error was displayed when user clicked Preview for an object in the Wizard.
|
February 2025 Patch
|
||
|
00168194,
00168216
|
SFM Wizards were not translated correctly.
|
February 2025 Patch
|
||
|
00163272
|
The discount was not applied to labor and expense charges in the Work Detail lines.
|
March 2025 Patch
|
||
|
00168537
|
The SLA cutoff time expired on the same day instead of rolling over to the next day when a Work Order was created after the cutoff time.
|
April 25 2025
|
||
|
00169767,
00169466
|
An error occurred during the migration of an SFM transaction when the transaction with the same name already existed in the target org.
|
May 30 2025
|
||
|
00171166
|
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.
|
May 30 2025
|
||
|
00162836
|
The Custom Action failed to load when the user clicked on the Wizard step.
|
Core 25R1
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00167059
|
The error message was not displayed when the file name of an output document exceeded 100 characters in length.
|
February 2025 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00162469
|
When the user updated the value for a Technical Attribute, the value was not saved.
|
December 2024 Patch
|
|
Case Number
|
Description
|
Fixed Version
|
|---|---|---|
|
00165027
|
Dependent picklist fields did not display correctly based on the Boolean value of the controlling picklist field.
|
December 2024 Patch
|
|
00164907
|
The user could not save the SFM transactions after bulk updating dependent picklist fields.
|
January 2025 Patch
|
|
00166144
|
The "Not Null" condition for the Lookup field did not work after the 24.1 Core upgrade.
|
January 2025 Patch
|
|
00164723
|
The field update did not work correctly during web service execution when Salesforce Flow was also configured.
|
February 2025 Patch
|
|
00167615,
00166469,
00168218
|
Extended edit did not show configured fields for SFMs when the 'No of column' field was empty in the Designer configuration.
|
February 2025 Patch
|
|
00168217
|
The navigation icons used in the extended edit window navigated incorrectly.
|
March 2025 Patch
|
|
00168603
|
The rich text field width was fixed and created an issue when the browser resolution percentage was reduced.
|
March 2025 Patch
|
|
00169473
|
The list view width of Lookup, Picklist, and Time components in the default state was too small to read.
|
March 2025 Patch
|
|
00163909
|
Incorrect data validation error occurred as the $F.DATEVALUE() function was not considered in the DST time zone.
|
March 2025 Patch
|
|
00164907
|
The bulk update on picklists with field dependencies allowed incorrect picklist values to be saved.
|
March 2025 Patch
|
|
00170264
|
Different error messages were displayed when an image was attached to the Response Description field based on the attachment size.
|
April 25 2025
|
|
00168952
|
Warning messages were not correctly translated into the User's preferred language.
|
April 25 2025
|
|
00169705
|
The calendar in the Start Date And Time and End Date And Time fields in the Labor tab affected the visibility of the record.
|
April 25 2025
|
|
00165712
|
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.
|
May 30 2025
|
|
00170264
|
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.
|
May 30 2025
|
|
00171164
|
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.
|
May 30 2025
|
|
Case Number
|
Description
|
Fixed Version
|
||
|---|---|---|---|---|
|
00165715
|
Duplicate code snippets were created when SFMs to create code snippets were retrieved and deployed using the SF command plugins.
|
January 2025 Patch
|
||
|
00165109,
00164512
|
SFMs migrated using the SF command plugins did not function correctly in the target org after migration.
|
January 2025 Patch
|
||
|
00166867
|
Some backend records field values were missing when SFM Search configurations were migrated through SF Command Plugins.
|
February 2025 Patch
|
||
|
00167411
|
SFMs with mismatched Source Object Update were not migrated correctly through Migration Tool.
|
February 2025 Patch
|
||
|
00165109,
00164512
|
SFMs migrated using SF Command Plugins did not launch and displayed an error.
|
February 2025 Patch
|
||
|
00167948
|
SFM Search configurations with field sorting configured were not retrieved using SF Command Plugins.
|
February 2025 Patch
|
||
|
00168444
|
Users could not access SFM Output Documents in the Go app after migration using the CLI tool.
|
March 2025 Patch
|
||
|
00168506
|
An error occurred when the SF plugin tried to process an org with large number of products or user records.
|
March 2025 Patch
|
||
|
00168538
|
An error occurred when the Logos and Metadata picklists were processed during the seed data load.
|
April 25 2025
|
||
|
00168835
|
An error occurred when the Checklist was deployed via SF Command Plugin.
|
April 25 2025
|
||
|
00169762
|
Expressions failed to map when the SFMs were migrated for standalone software updates.
|
April 25 2025
|
||
|
00165767
|
An expression failed to map in the transaction when it was migrated via the SF Command Plugin.
|
April 25 2025
|
||
|
00170370
|
An error occurred when the admin configured a language other than English in the org during the seed data load.
|
April 25 2025
|
||
|
00170873
|
The Smart Sync was not enabled in the target org after the CLI deployment.
|
April 25 2025
|
||
|
00170290
|
The multi-source SFM was not linked to the SFM when it was migrated via the global deploy command.
|
May 30 2025
|
||
|
00170292
|
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.
|
May 30 2025
|
||
|
00170584
|
An error occurred during the migration of an SFM transaction when the transaction with the same name already existed in the target org.
|
May 30 2025
|
||
|
00170872
|
The expressions failed to map after an SFM transaction was migrated to the target org via the CLI tool.
|
May 30 2025
|
||
|
00165767
|
Transactions configured with a button in the Page Properties or Page Layout sections with no elements were not retrieved via the CLI command.
|
May 30 2025
|
||
|
00171763
|
The expressions were not retrieved in bulk after the new ServiceMax plugin was installed via the CLI tool.
|
May 30 2025
|
||
|
00171764
|
An error occurred when the user tried to retrieve transactions after the patch upgrade via the CLI tool.
|
May 30 2025
|
|
Case Number
|
Description
|
|---|---|
|
NA
|
The AI Gateway currently takes approximately 2–3 seconds before initiating a call to the Knowledge Access Agent (KAS). This delay significantly reduces the time available for KAS to process and respond, making it difficult to meet the defined 5-second service-level agreement (SLA) for query responses. As a result, even if KAS performs optimally, the overall response time often exceeds the SLA threshold.
|