00144062

The SFM Description was not translated into German as the description value was not retained when saving the SFM.

00137568

Issue: Ranked Appointment Booking work orders were unassigned when there was a low capacity.

Resolution: An enhancement is provided to prioritize scheduled Ranked Appointment Booking work orders in case of a low capacity.

00142807

Schedule Optimization scheduled fixed events to a different technician. This issue occurred when the initially intended technician had insufficient drive time.

00141903

The proposed options included overlapped events when the Propose Times option was used in the Service Board.

00139031

The ellipses info icon feature did not work as expected for the read-only lookup fields.

00140449

The Display criteria filter did not work as expected for the dynamic section when configured with the Record ID field.

NA

Issue: Errors in the Advanced Search are displayed on the SFM Delivery page instead of the Advanced Search lookup modal for the user to cancel and perform the search again.

Resolution: Errors in the Advanced Search are now displayed on the Advanced Search lookup modal for the user to cancel and perform the search again.

For more information, see Advanced Lookup.

00141627

The picklist field name with a question mark at the end displayed the question mark at the beginning in SFM Delivery.

00143091

00141919

The code snippet $env.getUserInfo to populate the current user's information displayed an undefined value error.

00142321

The Parts lookup configured with multi-level mapping did not search for any parts.

00142634

A white screen was displayed when child tabs were accessed to add child lines in an SFM.

00143068

Issue: The user does not have the ability to enter the current date and time in the DateTime field of an SFM with one click.

Resolution: The user can enter the current date and time with one click using the Now button at the end of the DateTime field of an SFM.

For more information, see Supported Datatypes.

00142857, 00143223

Issue: The DVR error or warning banner displays the custom error messages that succeed the list of error fields for header and child sections. If a child tab contains incorrect fields, tab names are repeated with each child field. The custom error message that follows the list of error fields loses its significance.

Resolution: The custom error or warning message appears first followed by the error or warning field name of the header or child section. If the DVR is on a single field, then the field name is displayed for the header, and the child tab name followed by the field name is displayed for the child section. If the DVR is on many fields, then the header fields are displayed with the comma-separated list. For the child section, the child tab name is displayed only once, followed by the list of comma-separated fields. The user has the option to view or hide all DVR participating fields from the display.

For more information, see Error Messages.

00143352

Issue: There is no option for the user to confirm the DVR warning messages for an SFM.

Resolution: An Ok button is added at the bottom of the DVR warning messages list and the Quick Save and Save buttons are disabled. The user must click Ok to acknowledge the warning messages after which the Quick Save or Save buttons are enabled on the SFM.

For more information, see Warning Messages.

00142956

The Lookup criteria with boolean values did not work as expected due to incorrect empty string values passed.

00143704

Two code snippets were configured on the SFM, one on the field exit and the other before saving the SFM. One code snippet's error was overridden with the other code snippet's successful execution and enabled the Save button.

00144026

The user was unable to save the SFM due to the formula configured on the number field.

00142858

An error message was displayed with a colon followed by the error message in the UI.

00142911

The warning message on the SFM was not displayed when the DVR criteria were met.

00143231

A blank child line was incorrectly added when a child line was deleted, another child line was edited, and then the user clicked the Quick Save button.

00143755

A lookup field displayed an error message, as the lookup form-fill configured did not work as expected.

00143602

An SFM with DVR did not highlight the child line field for the first time.

00143811

The DVR warning configured on the Travel line End DateTime field did not work as expected when debriefing a Work Order.

00145168

The DVR warning or error messages were not displayed as expected for linked SFM in the child line.

00143068

The user was unable to select the correct DateTime field value in dd/mm/yyyy format in the header and child lines using a single click with the Now button.

00143526

The "Related to ID" field was not populated with the Work Order number even though it had Work Order as its data source.

00144982,

00144605

The DVR messages were not displayed when a webservice configured for a custom button was executed and multiple child lines were added using the multi-add modal window.

00143707

The values in the encrypted fields of an SFM were displayed as undefined after saving the SFM.

00145090

The Edit menu item on a child line to open the extended edit dialog box overlapped with the child line columns when scrolling horizontally in the SFM grid.

00144396

The SFM grid table was not resized to fit the page width when the user used the browser View > Zoom option to zoom the child line section.

00142948

The Auto Update checkbox, when disabled, did not display the user confirmation window when the user moved to the next record after updating the current record

00145526

The field values for the child lines modified on the grid's inline view were not retained when the user invoked the Extended Edit window and clicked the close X icon or the Cancel button.

00143707

The values in the encrypted fields of an SFM were displayed as undefined after saving the SFM.

00139375

The Migration Tool did not delete the child object configurations in the target org post the SFM Transaction migration.

00143150

The migration of the dispatch process configuration resulted in an error, as the dispatch process was not present but the territories were present in the target org.

00098911, 00110893,

00108619, 00108159

The Output Document was generated as an HTML and PNG file instead of a PDF file.

00112672, 00112601

The Work Order lines copied using the Copy Line Item feature were not synchronized to the server.

00115422

The Work Order line copied using the Copy Line Item feature was not saved. This was because the Time field in the extended edit screen was uneditable.

00110309, 00122744

The Attachments renamed on the server were stuck in the Downloading state due to issues with Data Sync.

00114719

The time overlapping error message did not disappear on the SFM even after the Start DateTime and End DateTime on the Work Detail lines were modified.

00122744, 00110309

The Output Document generated on FSA was renamed but the server was not updated successfully with the renamed filename. After smart sync, the document on the server was reverted to its original name.

00120936

In the Work Order debrief, the Software Version Update lookup field was configured with lookup criteria. The lookup criteria had spaces due to which the lookup criteria failed, and the Software version records were not downloaded.

00123310

The Start DateTime and End DateTime fields on the event were blank after the app was upgraded.

00128525

The Lookup field did not display any results when the app was offline. The lookup criteria had spaces due to which the lookup criteria failed, and the records were not downloaded.

00128956

The Lookup field worked in all other versions of the app except version 3.12.3. The lookup criteria had spaces due to which the lookup criteria failed, and the records were not downloaded

NA

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

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.

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.

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.

00138355

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

00142595

The Data Validation Rule did not work as expected in the FSA as boolean values were incorrectly converted to string.

00139650

The DateTime field did not display the user-selected values on the UI as an empty string revoked the user-selected values.

00134259

The child lines created in FSA were not synced to the server when multi-source mapping was configured for an SFM.

00139091

The currency field value on the covered product child line record was overridden with the currency field value on the service contract header record.

00138250

In the console view, when an IB record was clicked in the IB Tree, the IB was displayed in a new window in classic mode instead of opening it in the console view.

00140332

The admin was unable to view all the objects in the SFM Search Designer. The Search Object picklist did not accommodate all the objects due to the high volume of objects.

00140331

The admin was unable to view the Layout Configuration in the SFM Wizard due to a view state error.

00141048

The manual pull for the timesheet for work detail lines split over two or more business days did not work as expected. This was due to the combination of settings for the time entries due to which the timesheet engine displayed an exception.

00136525

The Scheduled SFM batch run failed, due to the high volume of records which resulted in a Salesforce CPU time limit exception error. A probable fix is provided for this issue. For more information, see Configuring Scheduled SFM Batch Apex Chaining.

00137933

The SFM Mapping displayed an error due to the changes in saving the Parameter Type field value.

00140921

The Custom Action of Type URL configured to open an Aura application in the same tab did not work as expected.

00141344

The standard Get Price code snippet did not consider the Travel Percentage Coverage of the Product Warranty when processing Travel Lines in a Work Order.

00140420

The translations for the words "Installed Product" in multiple supported languages were reverted when the org was upgraded to the latest ServiceMax Core Patch release.

00141296

The Custom Action email template used the user's display name instead of the Org-wide email address to send an email notification

00141625

The validation message was not displayed on the Stock Adjustment Inventory process when the Stock Serial Number had one entry even though the Quantity field was zero.

00143442

The SOQL query caused the Salesforce alert "SOQL query consuming too much of CPU consumption".

00143384,

00142287

The ServiceMax Mobile Configuration page displayed the Apex CPU Time-Limit error.

00139908

Issue: The Timesheet feature did not prioritize time entry creation for the Salesforce Events, ServiceMax Events, and Work Detail lines with custom Start DateTime and End DateTime field values.

Resolution: The Timesheet feature is now enhanced with a configuration setting that will allow time entry autofill to prioritize any custom mapping of Start DateTime and End DateTime fields that are defined for Salesforce Events, ServiceMax Events, and Work Detail lines when creating time entries.

For more information, see Creating Time Entries for Custom DateTime Fields.

00143303

Issue: Salesforce Event and ServiceMax Event triggers were executed on record creation irrespective of type of user.

Resolution: Salesforce Event and ServiceMax Event triggers can now be disabled using Trigger Control.

For more information, see Trigger Controls.

00146103

The Related Object field was not populated when the Advance Download Criteria was edited, post 23.1 server upgrade.

00145131

An error was displayed when the standard inventory process for stock adjustment was created or updated. The inventory process succeeded when the value of the Stock Status picklist field value was set as default in the inventory process, and it was not the first value in the picklist. The inventory process failed when the value of the Stock Status picklist field value was set as default in the inventory process, and it was the first value in the picklist.

NA

Issue: The user was unable to move or resize the Event modal window.

Resolution: The user can now resize the Event window.

For more information, see Creating Work Order Event.

00139271

The user was unable to save an event that had a Drive Time After value when the JDM setting was True.

00143958

The user was unable to create events when the Event. Duration field was configured in the Event Color rule.