Configuring MR and OTS publish tasks
The MVS Publish Rotation Task performs
the processing of MR and OTS schedules. One or more publishing tasks must be configured
according to the business requirements for processing rotational schedules. For example,
publishing tasks can be configured to ensure that schedules are always available to
employees for a future period specified by a collective bargaining agreement. Multiple
publishing tasks can be scheduled to support different publishing modes or types of
rotations.
The publish mode specified for each publishing task determines its role in the rotation publishing process. These modes are available: short term, long term, and daily. After a user sends a rotation for processing, a short term task processes the immediate future schedule from the start of the publishing period. This processes the entire length of OTSs. MRs are processed for the number of days specified in the task configuration. A short term task is required for publishing MRs and OTSs.
The long term task picks up the processing of MRs after the last day processed by the short term task. The number of days processed by the long term task is specified in the task parameters. A long term task is not required for customers that are only using OTS.
The daily task ensures that full schedules are available as time progresses. When the daily task runs, it processes the next day after the last processed date for all processed MRs. A daily task is not required for customers that are only using OTS.
Example MR and OTS publishing periods
This table lists an example of publishing periods for MRs and OTSs using short term, long term, and daily publishing tasks:
| Task | Start of Publish Period | End of Publish Period | Task Frequency |
|---|---|---|---|
| Short Term | Current Date | Current Date + 55 days (8 weeks into future) | Every X minutes |
| Long Term | Current Date + 56 days | Current Date + 365 days | Every X minutes |
| Daily | Current Date + 366 days | 1 day | Daily |
All these publish tasks are configured as the MVS Publish Rotation Task, with different execution
frequencies.
The parameters of each of the tasks are different. This table lists the configuration needed to achieve the above publishing periods:
| Parameter | Short Term Task | Long Term Task | Daily Task |
|---|---|---|---|
| Schedule Type | MR, OTS Schedule | MR, OTS Schedule | MR, OTS Schedule |
| Publish Mode | Short Term Publish | Long Term Publish | Daily Publish |
| Publish From | Current Date | Current Date | Current Date |
| Offset | 0 | 56 | 365 |
| Offset Unit | Days | Days | Days |
| Value | 55 | 309 | 1 |
| Unit | Days | Days | Days |
| Success Status | Short Term Published | Published | Published |
| Failure Status | Error Publishing | Error Publishing | Error Publishing |
| Send Notification | Checked | Checked | Checked |
| Thread Count | 1 | 1 | 1 |
| Batch Size | 30 | 30 | 30 |
| Chunk Size | 56 | 56 | 1 |
| Backup User to Notify | <determine by client> | <determine by client> | <determine by client> |
Based on the client's operational needs, the short-term publish period can be longer or shorter than this typical 8-week period. This variation depends on the amount of future schedule information that the client wants to make available to users in the immediate future. For example, a certain organization may only require 6 weeks of schedule to be made available for scheduling transactions shortly after an MR is published. Thus, the Short Term Publishing task could end at the 6-week (42 day) mark, and the Long Term Publishing task will resume publishing after 42 days from the current date.
Registry parameters for rotation publishing
The registry parameter MVS_PUBLISH_LOCK_LENGTH determines the maximum number of days to lock the schedules of employees assigned in an MR. It also determines the length of time that an MR is checked for schedule compliance and shift overlaps before processing. The value of the registry parameter must be set to at least the same as the publishing length of the long-term publishing task, which is determined by adding the Value field to the Offset field. For example, if the Value is 309 and the Offset is 56, this registry parameter must be set to at least 365.
The registry parameters MR_PROCESS_VALIDATION_START_DATE and MR_PROCESS_VALIDATION_OFFSET_DAYS together determine the start date used to validate schedules for schedule compliance and shift overlaps. This start date must match the start date configured for the Short Term Publish task used to publish MRs. For example, if MR_PROCESS_VALIDATION_START_DATE is set to PAYGRP_CUTOFF_DATE, then the Publish From parameter for the Short Term Publish task must be set to Pay Group Cut Off Date. Similarly, if MR_PROCESS_VALIDATION_OFFSET_DAYS is set to 0, then the Offset parameter in the Short Term Publish task must also be set to 0. This ensures the start dates are aligned for schedule validations and publishing.
Notifying backup users
The Backup User to Notify field in the publish task parameters allows system administrators to set up a backup user to receive the publish notification workmails. Backup users can be used in cases where the original user who published an MR or OTS is no longer an active user (for example, due to termination of employment, or changing of roles in the company). If the original user who published the schedule is not found, the system will broadcast the publish notifications to the backup user.