Rolling days publish task
You can use this publishing task to enable the scheduler to publish the schedule for rolling days without requiring a manual trigger to initiate the task. An email notification is sent to users mentioned in the workmail notification lookup.
You can configure the task to run for multiple teams, with a specified rolling number of days and offset, enabling the task to operate automatically according to the frequency you specified.
- Include Sub Teams - When one or more parent teams are selected, this check box enables users to schedule jobs for multiple teams and sub-units.
- Publish shifts with pending time off requests - This check box indicates whether to include or exclude shifts with pending time off requests.
- Offset (Days) - This field specifies the number of days when unpublished shifts are published, in addition to the system date.
For example, if you specify 0 in the Offset (Days) field, unpublished shifts are published from the current system date. If you specify 1, then unpublished shifts are published from tomorrow. If you specify 3 in the Offset (Days) field, then unpublished shifts are published three days from the current system date.
- Number of Rolling Days - This field specifies the number of days when a shift must be published, in addition to the system date. If the Offset (Days) field is empty, the value in the Number of Rolling Days field is used to determine when unpublished shifts are published.
For example, if you specify 28 in the Number of Rolling Days field and 0 in the Offset (Days) field, then shifts are published for 28 days from the current system date.
When you specify different values for Offset (Days) and Number of Rolling Days, for example 5 and 28 respectively, then unpublished shifts are published 5 days from the current system date. The system then publishes shifts for the next 28 days, starting from the offset date.