ALLOW_EDIT_IN_USE_SHIFT_CONFIG

Description:

Use this configuration key to control whether you can edit a shift configuration that is already in use.

When set to TRUE for a team, you can update a shift configuration even if the effective date falls on or before the Shift Last Used On date. Existing shifts in historical schedules are not updated with the new configuration. When set to FALSE, you cannot edit a shift configuration on or before any date the shift is in use.

A shift is considered in use, for editing transactions, when it is displayed in the schedule (ASV, Manage Schedule, Central Staffing). A shift that is present in MR/OTS and Schedule Templates is not considered in use for the editing transaction.

For example, if Team A's shift is currently displayed in a schedule (ASV, Manage Schedule, or Central Staffing), setting this key to TRUE enables updates to the shift configuration, such as the shift start time or description. Setting it to FALSE prevents those changes.

Sub-teams inherit the parent team's setting only when Apply to Sub-teams is selected. If a sub-team has its own configuration value, that value overrides the parent team's setting.

Examples of sub-team behavior:

  • If the parent team's ALLOW_EDIT_IN_USE_SHIFT_CONFIG is set to TRUE and Apply to Sub-teams is selected, the sub-team can edit shift configurations that are already in use.
  • If the parent team's ALLOW_EDIT_IN_USE_SHIFT_CONFIG is set to TRUE and Apply to Sub-teams is selected, but the sub-team sets its own ALLOW_EDIT_IN_USE_SHIFT_CONFIG value to FALSE, the sub-team cannot edit shift configurations that are already in use.
  • If the parent team's ALLOW_EDIT_IN_USE_SHIFT_CONFIG is set to TRUE but Apply to Sub-teams is not selected, the sub-team cannot edit shift configurations that are already in use.
Note: This configuration key applies only to standard Edit actions. For inherited shifts, Clone and Edit always blocks cloning when the effective date falls on or before the shift's actual last-used date, regardless of whether this configuration key is set to TRUE or a custom mvs-callout-shiftlastuseddate callout is configured.
Default Value:

False

Allowed Configuration Value:

True, False