PLUGINS

Location
system/modules/timeOffPlanner/
Description
Use this parameter to enable the core MVS plugin for integration between the Time Off Planner and the Multiview Scheduler. You can also use this parameter to enable a custom Time Off Planner plugin (for example, for non-MVS shifts).

To enable the integration between the Time Off Planner and the Multiview Scheduler, set this parameter to es-mvsTimeOffPlannerPlugin. With this configuration, relief shifts are generated as part of any time off approval. Locks are also enforced on any MVS shifts involved in time off requests that are initiated by the employee and are still pending approval. This locking ensures the integrity of shift data while the decision on the request is being made.

As of 2024.04, you can also use the custom extension script ta-top-plugin for integration between the Time Off Planner and the Multiview Scheduler.
Note: No UI capability exists in the Groovy extension script. The use of this script cannot depend on user input.

For information on creating extension scripts, see the Infor Workforce Management Custom Scripting Developer Guide.

If this feature is enabled, you can also optionally use the CONDITIONAL_APPROVAL_ENABLED registry parameter (/system/modules/emvs/CONDITIONAL_APPROVAL_ENABLED) to identify time off requests that are conditionally approved.

A time off request is considered conditionally approved if the supervisor selects Unfilled or Pending as the relief status. The employee receives a notification when a request is conditionally approved, and the time off request is marked in a darker shade of green in the calendar to indicate the conditional approval.

See CONDITIONAL_APPROVAL_ENABLED.

Valid values
This parameter accepts a comma-separated list of Time Off Planner plugins, including es-mvsTimeOffPlannerPlugin.
Note: If multiple plugins are used that contain UI components, they may end up in conflict with each other.

This parameter also accepts customer extension scripts. You can use both plugins and scripts.

Note: If you plan to use both custom extension scripts and plugins as parameters, ensure that the custom groovy class name differs from the custom plugin name.