The following are the enhancements in ServiceMax Core 24.1.

Currently, the event's error or violation message is unavailable in the event records when a manually scheduled work order event or a non-work order event is violated, rejected, or non-optimized by Schedule Optimization due to invalid drive time or overlapping event. Also, the error or violation message is unavailable in the technician records when a technician has invalid data, such as incorrect address information. In such cases, the users need to look through the information from ServiceMax job logs to identify the cause.

With the new enhancement, the error or the violation message is available in the event object's and technician object's Files section in the corresponding records.

The admin must manually add the files section from the related list to the page layout for the ServiceMax Event object, Salesforce Event object, and Technician object.

These readily available messages in a centralized location improve overall efficiency and reduce the time required to troubleshoot and resolve issues. For more information, see Capturing Message Details in the Files Section.

The Propose Time option for booking fixed arrival slots in Batch Optimization is now enhanced to support many batch jobs. Additionally, the error messages are displayed with more clarity, making it easier for users to identify and resolve any issues arising during the booking process. These enhancements streamline the booking experience and improve overall efficiency when scheduling regular batch qualified work orders along with the Propose Time booked work orders. For more information, see Propose Time Error Codes and Messages.

A new custom setting SET00100 (Module: OptiMax, Submodule: Manage Optimax Setting) — Service Board Shifts callout batch size is introduced to support large data volumes per batch job only when Shift is enabled as Business Hours. For more information, see Configuring Schedule Optimization to Use Service Board Shift Information.

Schedule Optimization has enhanced data validations to filter out and report invalid data resulting in better optimized schedules. This enhancement ensures that the data is complete and reasonable for the optimax engine to provide a better results to utilize. This helps in seamless implementation. For more information, see Improved Input Data Validation for Optimization Jobs.

The Schedule Optimization provides the job statistics captured at the corresponding job level after the successful job completion based on the optimization results. These statistics assist in analyzing data such as the number of scheduled work orders, technicians, drive time, and number of routes.

Now, the names of the statistics listed under the ServiceMax job statistics and the corresponding units for each statistic are enhanced for a better experience. For more information, see Naming Convention in ServiceMax Job Details.

Currently, the preferred dates are considered a soft constraint. In some scenarios, the Real-Time Optimization optimizes beyond the specified dates.

Admin can configure the Cost Factor to consider the preferred dates as a hard constraint for Real-Time Optimization. For more information, see Defining Constraints and Cost Factors.

The Time entries Start DateTime and End DateTime are now calculated according to the actual hours for events split across multiple days. Previously, Time Entries calculated Start Date/Time and End Date/Time based on the defined Business Hours of the Timesheet. This confused users when their recorded actual time fell outside their Business Hours across multiple days. The Multi-Day Split now supports actual Start and End Date/Time hours when processing time entries.

For more information, see Splitting Multi-Day Events using Actual Hours.

The PM Work Orders in a batch are rolled back and not created when an error is encountered while generating Work Orders from PM Schedules. The statuses of the associated PM Schedules have also been rolled back. The Work Order Generation Status and the Scheduled On date remain unchanged.

Previously, when the PM Process engine generated Work Orders from PM Schedules and encountered an error in a batch, it would roll back the creation of all Work Orders in that batch, even for PM Schedules that did not have errors. The statuses for the associated PM Schedules were not rolled back. This led to PM Schedule Lines having a status of Complete without associated PM Work Orders.

For more information, see Work Order Generation Status on PM Schedule.

Administrators can now determine the number of questions that must be queried per API call when a checklist is loaded in the Checklist Designer. This helps the administrator to reduce the batch size and avoid the platform limit exception, while loading the checklist template. For more information, see Bulk-loading of Questions and Answers.

Users can select or clear a checkbox on the grid Layout with a single click. Two clicks were required to set the value for the checkbox on the Detail Lines grid. The user can also use the Tab key to navigate the checkbox field, followed by the Spacebar key to select or clear a checkbox. For more information, see Checkbox Fields.

The DVR Warning messages are now displayed inline in the Extended Edit window of a child line when real-time validation is set to true. When the user enters a value and exits a field in the Extended Edit window, the warning message is displayed below the erroneous field.

For more information, see Extended Edit.

The DataGuide Form configurations can now be overridden in the target org for Forms and Document Templates.

For more information, see DataGuide Supported Dependent Items.