Confguring a System Job for Current-Day Optimization
* 
Current-Day Optimization is a Production Beta feature in Service Board 25.1.
To begin configuring Current-Day Optimization, you create and configure a System Job to define the execution frequency, including the time zone. After you complete the steps in this following procedure, you can move forward to create a Current-Day Optimization record.
To configure a System Job for Current-Day Optimization:
1. In Max Admin, on the System Management () launchpad menu, in the System Management section, click System Jobs, and then in the list view, in the top left corner, click Create ().
2. On the record page, in the Name field, enter a name for the record, and then do one of the following to define the execution frequency:
For advanced scheduling patterns, in the Cron Expression field, configure a cron expression.
For simple repeat intervals, in the Trigger Interval fields, configure the number of time units between each execution, for example, 2 HOURS.
3. In the Time Zone field, configure the time zone accurately, and then after you review your configured values, in the top left corner, click Save and Close () to activate the System Job.
4. In the Operation field, select the Current-Day Optimization Operation record that ships with Service Board.
* 
Accurate time zone configuration is critical for determining the starting point of the one-day scheduling horizon. The selected time zone should align with the selected Job’s access hours and the related Resource’s shift configuration to ensure correct optimization across time zones.
To prevent dispatch conflicts, ensure that there is no overlap between Current-Day Optimization jobs. Ideally, configure single Jobs in only one Current-Day Optimization job. If the same Job is configured in multiple Current-Day Optimization jobs, schedule those jobs to run at varying time to avoid assigning the Job to multiple Resources.
In cases where multiple Current-Day Optimization jobs share the same Resource pool, be sure to avoid scheduling overlapping execution schedules. Otherwise, multiple Jobs might be dispatched to the same Resource simultaneously.
For more information:
Was this helpful?