Service Board introduces multiple selection and movement of dependent appointments to simplify scheduling adjustments. Users can select multiple appointments within the same dependency group or Service Task appointments of the same job and move them together, reducing the effort required to reschedule related appointments individually. The feature supports selection across multiple resources and is available in dependency management scenarios.

Managing large dependency groups can be time-consuming when appointments must be rescheduled one at a time. Multiple selection enables Dispatchers to adjust related appointments in a single action, improving scheduling efficiency and reducing manual effort.

No additional configuration is required. Existing dependency management rules continue to apply.

Users can select multiple dependent appointments and move them together instead of updating each appointment individually. This capability helps Dispatchers respond more quickly to schedule changes while maintaining dependency relationships and planning constraints.

For more information, see Selecting and Moving Multiple Dependent Appointments.

Resource Recommendation can now use the service team assigned to a job when identifying recommended resources. When the setting Use the Job's Service Team and Related Secondary Service Teams for Resource Recommendations is enabled, Service Board evaluates resources from the job's primary service team and any related secondary service teams instead of relying only on the selected resource list. This enhancement helps provide recommendations that better match the job's service team structure and assignment requirements.

Dispatchers can receive Resource Recommendation based on the service team assigned to the job. If the job includes a primary service team, Service Board considers resources from that team and its related secondary service teams when generating recommendations. If no service team is assigned to the job, Resource Recommendation continues to use the selected resource list and follows the existing behavior.

For more information, see Resource Recommendations Based on Job’s Service Teams.

Current Day Optimization now exposes its monitoring timeout as an operation parameter. Previously the monitoring duration was fixed, so an optimization run past the built-in limit was canceled and marked as failed.

An administrator configures Maximum Monitor Duration In Minutes on the Current Day Optimization operation to control how long the job is monitored before it times out. Organizations that run large job volumes, where a run can exceed the former fixed limit, can raise the value and avoid unnecessary cancellations.

For more information, see Configuring the Maximum Current-Day Optimization Monitor Duration.

There are no customer-facing defects fixed in this patch release.