00134147

The user was unable to hide/unhide the tabs in the Advanced Technician Search configuration page.

00136440

Incremental events were not displayed on the Scheduler when the user refreshed the Work Order Grid.

00133602,

00135259

When the user created events in advanced mode for the work orders with the Dispatch Status field value as Queued, the Dispatch Status did not change to Assigned.

00134529

Work orders in the Work Order grid were not filtered as expected when special characters such as & were present in any of the fields.

00131178

Technician working hours overlapped over holidays when the logged-in user and the technician working hours had the same time zone.

00130045

The Dispatch Console UI elements were not translated into German.

00132518

The business hours of inactive technicians were also considered.

00136877, 00139976

The Start DateTime and End DateTime fields did not render values on the UI when the Work Order was debriefed. This issue was specific to iOS version 16.4.

3.13.2

00137501

The orientation became unresponsive in the landscape mode when the user added the signature on the Output Document and clicked Done. This issue was specific to iOS version 16.4.

3.13.2

00138355

The lookup filter with advanced search did not work as expected.

3.13.2

00132723

The technician details were blank when the user updated the work order.

00132589

Schedule overlaps occurred on the non-availability of technicians with special characters in the name.

This is a server-side fix.

00129420

Appointment slots were not displayed on the Ranked Appointment Booking page for the specified date range.

00137188

Schedule Optimization assigned work orders over the unavailability events in a few scheduling job runs. This caused event overlaps.

00136727

The user could not select and add the technician in the Immediate dispatch process when there was a high volume of technician data.

00130175

Issue: Schedule Optimization did not reassign the Ranked Appointment Booked work order to a different technician when the working hours of the currently scheduled technician were updated. The selected arrival window was outside the updated working hours of the currently scheduled technician. This resulted in clearing the Promised Arrival Window, and the Appointment Booked work order was unassigned.

Resolution: Schedule Optimization reschedules the Ranked Appointment Booked work order to another technician if the working hours of the currently scheduled technician are updated and the arrival window is exceeded. Schedule Optimization either reschedules the work order to another technician if available or keeps it unassigned.

For more information, see Ranked Appointment Booking.

00131092, 00133631

Issue: The event trigger validated the Service Duration value of the events and displayed a validation error when the value was negative.

Resolution: You can now control the validation of the negative Service Duration value through a custom setting. Set the custom configuration setting SET00100 to False to bypass the validation for the negative Service Duration value. For more information, see Configuring the Service Duration Validation.

00134980

Issue: Work order events were created for the work orders in a single update if the work orders update was performed for the following field values:

Resolution: Event creation logic on work order update now executes for the dispatch processes of type Immediate Dispatch only.

For more information, see Event Creation Behavior.

00130798

The Description field in the Time Entry records of the Timesheet was populated with wrong data for non-work order events.

00130524

The IB tree on the Installed Product record displayed a blank screen due to the CSRF token enablement.

00130396

The admin was unable to choose a recipient from the drop-down list on the SFA configuration page. The drop-down list did not display any values.

00130717

The SMS Notification was not sent when the recipient was configured to lookup the polymorphic field.

00133533

The Scheduled SFM job to renew the contract failed with an error.

00131366

The latest PM Schedule records were not retrieved, so a new Work Order was created even though the existing Work Order was still open.

00133703

The lookup form-fill fields were not queried when the advanced filter was configured for a lookup field.

00134913

The Service Board application did not launch when invoked through the Background SFM. The external URLs were rendered incorrectly when navigating from Background SFM to Custom Action.

00136165

The Work Order Date was not updated when the PM Plan was created and the Processed checkbox was set to true. A field was missing in the query, resulting in an exception.

00137199

The admin was unable to edit the custom action. The org was Einstein enabled, due to which some of the lookup fields in the custom action did not have edit access.

00133099

The Related Object field value was displayed incorrectly when the admin edited the Advanced Download Criteria expression on the Mobile Configuration page.

00138798

The admin was unable to update the Mobile Configurations due to an "Attempt to dereference a null object" error.

00130507

The SFM child line displayed errors for CreatedDate and LastModifiedDate fields due to GMT time zone conversion when cloned and saved.

This was due to the setting "Enable Set Audit Fields upon Record Creation and Update Records with Inactive Owners User Permissions" enabled in the Salesforce Setup.

00133034

The high volume of PM Schedules for the respective PM Plans caused the PM batch error.

00128459, 00130568, 00129642

Issue: An error occurred when the Mobile Configuration page was accessed on the ServiceMax Setup. When the Mobile Configuration page was launched, all the object labels available in an org were retrieved and displayed. The large number of objects in the org led to Salesforce governor limit issues.

Resolution: You can now exclude objects belonging to a managed package or namespace from loading on the Mobile Configuration page by creating a custom setting. You can define the custom setting with the comma-separated list of namespaces from which you want to exclude the objects. Additionally, some areas of the Mobile Configuration page have been optimized.

For more information, see Exclude Objects from Mobile Configuration Page.

00129511

Issue: The stock transfer between the source and destination location always updates the product stock record's DECREASED status in the source location with Qty as Zero. The DECREASED status was not required in this scenario.

Resolution: The admin must create a custom setting SET00999 and set it to False to update the DECREASED status for stock transfer between the source and destination location, where the destination location is non-stocking.

For more information, see Enable or Disable DECREASED Status for Product Stock.

00135034

Issue: The PM Process engine did not send an email notification to the user even when the PM Process qualified zero PM Plans.

Resolution: The PM Process engine sends an email notification to the user indicating zero PM Plans were qualified.

For more information, see Schedule and Notifications Tab.

00136955

The SFM number field, when edited using the tab key, did not highlight the number field on focus.

00135937

The SFM reloaded when the Owner field was selected in the SFM grid line. The browser cache limit was exceeded due to additional properties from Salesforce in the API call.

00136665

The SFM did not display the error message when a data validation rule was configured to avoid blank space for a field. The user was able to add empty space and save the SFM.

00135740

The value None selected from the picklist for a Technical Attribute was not displayed in the related list object record.

00122031

The Service Report was generated with one extra signature.png extension file, due to which there were two files in the Notes and Attachment section for a Work Order instead of just one.

00130055

The SFM Search displayed a different scheduled DateTime value than the one on the Work Order record.

00133495

An error was displayed when a button configured with a webservice in an SFM was invoked.

00126892

Issue: The ".value" attribute for picklist and multi-picklist fields was not supported on Output Document Designer.

Resolution: The ".value" attribute in the picklist and multi-picklist fields is now supported using the new "Insert API Name" option on the Output Document - Template Designer. The "Insert API Name" option inserts the API name of the picklist or multi-picklist value at runtime on the SFM Delivery.

For more information, see Template Designer.

00134870

A blank screen was displayed after adding the Start DateTime and End DateTime. This was specific to the Chinese locale.

00134303, 00133986

An out-of-range validation error was displayed for the number field.

00132671

The number field on the Work Order displayed a decimal number even though the number field was not configured to include any decimal numbers.

00133281

The standard Get Price code snippet included seconds value from the Start DateTime and End DateTime, which led to incorrect line price calculation.

00131797

The 'is required' field in an SFM was not translated.

00130675

The required field triggered a real-time data validation error in the SFM grid even though it was disabled in the SFM page layout.

00129263

User preferences of the SFM grid tabs were not retained on Quick Save.

00125141

The webservice was executed for each child line added in the SFM grid instead of executing just once for all the child lines added using Multi-Add.

00120942

Issue: The user made multiple clicks to select the picklist values, and this resulted in a loss of time for the user.

Resolution: The inline search capability is enabled for picklist values. The user can type to filter the picklist values and use either the tab key or focus out of the field to select the immediate matching result.

For more information, see Child Section.

00133163

The migration tool incorrectly fetched the "Id" instead of "id" in the JSON format when the ServiceMax profiles were migrated.

00134185

The Checklist process with questions was not migrated as the request URI was too long.

00134018

The Migration Tool validated inappropriate metadata fields for the Checklist Output Document process.

00133913

The profile name field was mapped to null when SFM Mobile permissions were migrated using the Migration Tool.

00136443

Post-migration of various SFM Wizards using the SFDX Plugin Tool, the SFMs failed to load on runtime.

00139375

The updated SFM Transaction, when migrated to the target org, did not modify the source and target child object configurations in the target org.