Validation rules page
Validation rules verify that requests meet the conditions that you specify. The validations rules that you use are available as approval and denial criteria for autoprocessing rules. A subset of these rules are available as waitlist criteria for time-off requests.
Each validation rule has an icon. If a request violates a validation rule, the icon is displayed for both the requesting employee (My Request page) and the employees that manage these requests (Employees Request page).
Time Off Request Validation rules section
Time off type list
This list lets you select validation rules for all activity types Groups of similar activities not covered by the predefined activity types in Workforce Management (WFM). or a specific activity Core component of both schedules and time records in Workforce Management (WFM). When an employee performs any kind of work, activities specify the scheduled work and capture employee adherence to their schedule. type. The default is All.
The list includes all activities created for the organization with the Used in Requests option. This option is set on the Activities page. This page is located on Work Administration, under Activities.
Validation rules
-
Time Off Pool has available time off hours. This rule is violated if the total length of scheduled time-off events for all employees during the requested day(s) is greater than the number of hours entered in either the Daily Pool or the Interval Pool or both time-off pools depending on the setup of the Time Off Activity selected for the request.
Hours for the Daily Pool and the Interval Pool are entered on the Time Off Pools page. This page is located on Organization Management Module in WFO that allows administrators to set up different hierarchies to manage users from a single, unified, Web interface., under Request Management.
-
Request avoids days where time off is not allowed. This rule is violated if the request covers a day where time off is not allowed.
Days where time off is not allowed are set up on the Special Days page. (This page is located in Organization Management under Request Management.)
-
Employee's time off balance has reached a value lower than the minimum allowed balance of <zero (0.00) or negative (-) n> hours. If this validation rule is set to zero, the rule is violated if the total length of scheduled time-off events for this employee during the schedule of accrual is a negative value. (Employees can accrue time off hours on different schedules, such as daily, weekly, biweekly, monthly.)
If this validation rule is set to a negative value, the rule is violated if the total length of scheduled time-off events for this employee during the schedule of accrual is lower than the defined negative value.
For example, this validation is set to Employee's time off balance has reached a value lower than the minimum allowed balance of negative (-) 8 hours. The total length of scheduled time-off events for an employee is -12 hours. In this case, an error message is displayed that this validation has been violated.
The allotment is entered on the Time Off page. This page is located on User Management Module that an administrator uses to create a profile for each employee in their organization., under Employees. Time Off year may be either the employee anniversary year or a calendar year, as configured on the page.
This validation rule takes into account the number of hours accrued by an employee as of the request target date.
-
Request complies with filing rules. This rule is violated if the request submittal date violates any of the filing rules applicable to the employee’s organization.
-
Requested time off is not being swapped. This rule is violated if one or more request choices overlaps a shift Work period in WFM that has a definite length. that will be received from a pending shift swap request (state of shift swap request is either pending, in negotiation or escalated).
-
Scheduled calendar event Scheduled event in WFM that is manually created on the schedule, can be a single instance or recurring event, and can have one or multiple attendees. Examples of calendar events are meetings or training sessions. activities that the request avoids: <All or a specific calendar event>. This rule is violated if the requested time off period overlaps with the selected scheduled calendar event.
-
Minimum duration of the request: <number> <Minutes, Hours, or Days.> This rule is violated if the request duration (end date - start date) is not at least the specified minimum. The minimum can be expressed in units of Minutes, Hours, or Days.
-
Maximum duration of the request: <number> <Minutes, Hours, or Days.> This rule is violated if the request duration (end date - start date) exceeds the specified maximum. The maximum can be expressed in units of Minutes, Hours, or Days.
-
Requested time off is for a past date. This rule is violated any time a request is created for a start date earlier than the creation date of the request.
-
A minimum of<x> percent of changed intervals improves net staffing based on all queues that the employee is <eligible to work or assigned to work> for the request duration. This rule is violated when the percentage of queue Entity that represents demand in WFM. Queues help predict workload by multiplying the volume of customer interactions by their expected handling time. time intervals that will be changed by the request is less than the specified minimum percentage for net staffing improvement in the work queues.
The minimum staffing level percentage is calculated as follows:
Improvement Percentage = (#periods where net staffing is improved / (#periods where net staffing is improved + #periods where net staffing is worsened) )*100
Examples
Example 1
Employee information:
Alice has skills to work both Queue-A and Queue-B. Both queues are overstaffed on Friday between 8:00 AM and 12:00 PM. Alice is only working Queue-A during this time. She requests Voluntary Time Off for this time range.
Time off validation rule setting for Voluntary Time Off:
A minimum of [100] percent of changed intervals improves net staffing based on all queues that the employee is [eligible to work] {for the request duration.
Result:
Alice’s request receives the following validation alert:
Time Off Request violates the net staffing requirements
Explanation:
The validation rule states all of the queues that the employee is eligible to work must be compared against the request. Because Alice is working only Queue-A, Queue-A improves. Queue-B gets no better, no worse; so the denominator of the fraction interval made better/interval changed is zero. Therefore, the percent improved cannot be calculated.
Example 2
Employee information: (This is the same employee as in Example 1.)
Alice has skills to work both Queue-A and Queue-B. Both queues are overstaffed on Friday between 8:00 AM and 12:00 PM. Alice is only working Queue-A during this time. She requests Voluntary Time Off for this time range.
Time off validation rule setting for Voluntary Time Off:
A minimum of [100] percent of changed intervals improves net staffing based on all queues that the employee is [assigned to work] for the request duration.
Result:
Alice's request does not receive an alert.
Explanation:
Because Alice's request is compared only to Queue-A and 100 percentage of the intervals that are changing improve, the request passes the validation.
Example 3
Employee information:
Barry has skills to work both Queue-A and Queue-B. Both queues are overstaffed on Friday between 8:00 AM and 12:00 PM. Barry is working a blended shift that applies to both queues during this time. He requests Voluntary Time Off for this time range.
Time off validation rule setting for Voluntary Time Off:
A minimum of [100] percent of changed intervals improves net staffing based on all queues that the employee is [eligible to work] for the request duration.
Result:
Barry's request does not receive an alert.
Explanation:
Because Barry’s request will improve both queues, the validation passes.
-
Request complies with employee’s maximum VTO per day/week. This rule is violated if approval of the request results in the employee exceeding his maximum VTO hours per day / week.
-
Request complies with Required Pay Period Hours. This rule is violated if the request would cause the employee to not meet the minimum hours in a pay period (includes Flex Time Requests).
Tracking for the Required Pay Period Hours entered on the Settings page. This page is located on Organization Management, under Request Management. When this setting is selected for an employee's organization, the Required Hours (balance) for Pay Period section is available on the following pages:
-
Time Summary: This page is located on Tracking, under Roster.
-
My Schedule Summary: This page is located on My Home, under My Schedule.
One or more time off activities must be set up to deduct from the Required Pay Period Balance. (This is done on the Activities page. It is located on Administration, under Work Administration, Request Management Usage section.)
-
-
Time Off Bid: Enforce the maximum approvals per employee for Time Off Bids. This rule is violated if the request exceeds the maximum time that can be approved for that employee and bid. The maximum time can be hours or days.
The maximum time for all employees in an organization and its suborganizations that are in the bid is set on the Settings page. This page is located on Request Management, under Time Off Bidding. The maximum time for individual employees that are in the bid is set on the Employees page. This page is located on Request Management, under Time Off Bidding.
-
Time Off Bid: Requests submitted before Time Off Bid deadline. This rule is violated if the request is submitted after the Time Off Bid deadline.
-
Time Off Bid: Request does not overlap with approved Requests. This rule is violated if the request overlaps one or more approved time-off requests. This rule prevents automatic approval of multiple continuous requests in the Time Off Bid process.
Request complies with maximum <number> approved time off requests per quarter. This rule is violated if the request for the selected time off type exceeds the specified number of approved time off request in any quarter. The four quarters are:
-
January, February, and March (Q1)
-
April, May, and June (Q2)
-
July, August, and September (Q3)
-
October, November, and December (Q4)
Request does not overlap with approved time-off requests. This rule is violated if the request submitted by the employee overlaps a portion of an already approved request submitted by the employee.
Approved Time Off Withdrawal Validation rules section
-
Request complies with filing rules. This rule is violated if the withdrawal request submission date violates any of the filing rules applicable to the employee’s organization.
Flex Time Request Validation rules section
-
Maximum duration of Flex Time Request: <number> <Minutes or Hours>. This rule is violated if the flex time-off duration, and any consecutive requests enabled for Flex Time, is equal to a value that is greater than the specified maximum duration.
-
Minimum duration of Flex Time Request: <number> <Minutes or Hours>. This rule is violated if the total flex time duration is less than the specified minimum.
-
Maximum number of makeup blocks per request: <number>. This rule is violated if the total number of flex time makeup blocks is greater than the specified maximum.
-
Maximum number of Flex Time Requests: <number> <Month or Quarter>. This rule is violated if the total flex time requests are greater than the specified maximum. When this rule is selected for an employee's organization, the Flex Time Summary section is available on the following pages:
-
Time Summary: This page is located on Tracking, under Time Summary.
-
My Schedule Summary: This page is located on My Home, under My Schedule.
-
-
Minimum duration of the activity < adjustable break activity or shift gap activity> is <number> <Minutes or Hours> after a make-up extension during the activity. This rule is violated if the minimum duration of the selected activity will not be met after an extension during the activity. (Until shift event Time period in WFM when employees are scheduled for specific activities, other than the main shift activity. Shift events can either be productive or unproductive, and can be associated with activities such as Phone, Email, Break and Lunch. activities are created for adjustable breaks or shift gaps, the list of activities is empty.) Example - adjustable break activity: Employees get a 60 minute, unpaid lunch break for a shift that exceeds six hours. By law, they are required to take 30 minutes for lunch. You can define this rule with a minimum activity duration of 30 minutes to prevent employees from making their lunch break too short.
Two break segments can occur due to a gap--one segment before and one segment after the work extension. Only one of these break segments must meet the minimum duration requirement in this rule.
If you are defining this rule for multiple activities with the same duration, you can select all applicable activities and enter the duration once. If you are defining this rule for activities with different durations, define each activity separately. Also, you can save or cancel all activities at one time instead of processing them individually. By default, the first adjustable break activity or shift gap activity shows in the list box.
To remove a minimum duration for an activity, set the duration to blank and save the change.
-
Makeup must occur <time period option>. This rule is violated when the requested make-up time does not occur in the selected time period. Time period options are:
-
as soon as possible and no later than a specific number of days <number of days>
Make-up time must be made up in the next gap, shift start, or shift end--whichever one comes first.
Employees can use an adjustable break to make up time, but it is not included in this validation.
Examples:
-
If an employee requests time off at the beginning of a shift and the shift has a gap, then all or part of the make-up time must occur during the gap.
-
If an employee requests time off at the end of a shift, then the make-up time must occur before the next shift.
-
-
in the same organization week
Make-up time must start and end within the same organization week as the time off.
The organization week is based on Week Start Day defined on the Organization Settings page (under Hierarchies Organization Management, then Hierarchies).
-
in the same scheduling period
Make-up time must start and end within the same scheduling period as the time off.
The scheduling period is based on the scheduling periods listed on the Campaigns Settings page (under Forecasting and Scheduling then Campaigns).
-
in the same pay period
Make-up time must start and end within the same pay period as the time off.
The pay period is based on two Required Pay Period Hours settings, Pay Period and Start Date, defined on the Request Management Settings page (under Organization Management then Request Management).
-
-
Makeup must occur as soon as possible and no later than <number> days. This rule is violated if earlier suitable flex makeup times occur before the proposed flex makeup time (excludes flex time with adjustable breaks).
-
Scheduled calendar event activities that time off must avoid <All or specific calendar event>. This rule is violated if the flex time request falls within a calendar event activity which must be avoided.
-
Request complies with filing rules. This rule is violated if the request submittal date violates at least one of the filing rules applicable to the employee’s organization
-
Makeup time complies with the organization hours of operation. This rule is violated if the flex makeup time specified in the flex time request does not fall within the hours of operation for the organization.
-
Maximum consecutive working days allowed as per organization settings. This rule is violated if the requested flex makeup time on a non-working day causes the employee to exceed the maximum number of shifts defined in the Maximum consecutive working days to schedule organization setting. (This setting is located on the Organization Settings page, under Scheduler Options.)
-
Minimum required time gap between consecutive shifts as per organization settings. This rule is violated if consecutive shifts including the makeup shift are scheduled closer than the minimum time required between consecutive shifts.
-
Maximum paid duration allowed: <number> minutes per <Organization Day> or 24 Hour Period>. This rule is violated if the request causes the paid duration to exceed the user-defined duration allowed for the selected period. Shift length is not considered; however, all paid hours during the selected period are considered. For the paid duration calculation, only paid hours are counted. Shift work (normal shifts, overtime, overtime extension) and time off are counted as paid hours. Flex time off segments are not counted as paid hours.
For the reference period that defines the day, select from the following options:
-
Organization Day: If all employees only have shifts that start and end in the organization day boundary, use this option.
During validation, the duration calculation uses the time period defined for the organization day. The organization day is defined on the Organization Setting page (located on the Organization Management menu, under Hierarchies). If the maximum paid duration threshold is exceeded, an alert is generated.
-
24 Hour Period: If any employees have shifts that cross the organization day boundary (shift starts on one day and ends on another day), use this option.
During validation, the duration calculation uses a sliding 24-hour window that increments by 15 minutes. The sliding window begins 24 hours + 15 minutes before the request start time and stops at 24 hours - 15 minutes after the request end time. If the maximum paid duration threshold is exceeded in a 24-hour window, the rule is violated. No more 24-hour windows are checked, and an alert is generated.
-
-
Minimum paid duration allowed: <number> minutes per <Organization Day or 24 Hour Period>. This rule is violated if the request for a makeup extension on a nonworking day causes the employee to fall under the user-defined duration allowed for the selected period. Shift length is not considered; however, all paid activities during the selected period are considered. For the paid duration calculation, only paid hours are counted. Shift work (normal shifts, overtime, overtime extension) and time off are counted as paid hours. Flex time off segments are not counted as paid hours.
For the reference period that defines the day, select from the following options:
-
Organization Day: If all employees only have shifts that start and end in the organization day boundary, use this option.
During validation, the duration calculation uses the time period defined for the organization day. The organization day is defined on the Organization Setting page (located on the Organization Management menu, under Hierarchies). If the minimum paid threshold is not met, an alert is generated.
-
24 Hour Period: If any employees have shifts that cross the organization day boundary (shift starts on one day and ends on another day), use this option.
During validation, the duration calculation uses a sliding 24-hour window that increments by 15 minutes. The sliding window begins 24 hours + 15 minutes before the request start time and stops at 24 hours - 15 minutes after the request end time. If the minimum paid duration threshold is not met after checking all windows, an alert is generated.
-
-
A minimum of <x>percent of changed intervals improves net staffing based on all queues that the employee is <eligible to work or assigned to work> for the request duration. This rule is violated when the percentage of queue intervals that will be changed by the request is less than the specified minimum percentage for net staffing improvement in the queues. Both the time off portion and each make up portion of the request are evaluated. When any portion of the request fails validation, an alert is displayed for the request. The alert specifies which portion failed validation: the time off portion or any of the make up portions.
The minimum staffing level percentage is calculated as follows:
Improvement Percentage = (#periods where net staffing is improved / (#periods where net staffing is improved + #periods where net staffing is worsened) )*100
Shift Swap Request Validation rules section
-
Both employees are from the same organization. This rule is violated if employees are assigned to different organizations.
-
Both employees are from the same campaign Collection of scheduling periods in WFM, which are defined time periods where specific employees target specific workloads.. This rule is violated if both shifts in a swap do not belong to the same campaign. They can be in different campaign weeks.
-
Both employees have the same skills for the active campaign queue. This rule is violated if the receiving employee does not have the same skills as the employee currently scheduled to work the shift.
-
Both employees have at least same skills for the active campaign queue. This rule is violated if the receiving employee does not have at least the same skills as the employee currently scheduled to work the shift. Receiving employees with additional skills will not cause a violation.
-
Both employees have the required skills to work the swapped shifts. This rule is violated if the employee or employees receiving a shift or partial shift do not have the required skills for the activities during that shift or partial shift.
-
One-way shift swap: When the employee receiving the shift does not have the skills to work all activities in the shift, this rule is violated.
-
Two-way shift swap: When a minimum of one of the two employees receiving a shift does not have the skills to work all activities in the shift, this rule is violated.
-
One-way partial shift swap: When the employee receiving the partial shift does not have the skills to work all activities in that partial shift, this rule is violated.
-
Two-way partial shift swap: When a minimum of one of the two employees receiving a partial shift does not have the skills to work all activities in that partial shift, this rule is violated.
-
-
Both employees have the same proficiencies for the active campaign queue. This rule is violated if the receiving employee does not have the same skills and proficiencies as the employee currently scheduled to work the shift.
-
Request complies with filing rules. This rule is violated if the request submittal date violates any of the filing rules applicable to the employee’s organization.
-
Both employees comply with min/max hours. This rule is violated if, after the swap, at least one of the employees will not comply with the min/max hours during the corresponding week(s) of the shift they get and the shift they give away in the swap.
-
Swapped shifts start on the same organization week. This rule is violated if the swapped shifts do not fall in the same organization week.
-
Swapped shifts have the same paid hours. This rule is violated if the total duration of paid time in the two shifts is different.
-
Swapped shifts must overlap the exact same portion with scheduled calendar events and time offs, and not overlap unavailabilities. This rule is violated if the following events occur:
-
Calendar events, which may or may not be inside a shift, do not overlap the same portion of the swapped-in shift.
-
Time off events, which may or may not be inside a shift, do not overlap the same portion of the swapped-in shift.
-
Any unavailability type event will overlap with the swapped shifts as the result of the swap.
-
-
Swapped shifts will overlap scheduled calendar events that must occur during a shift. This rule is violated if calendar events, which have to be inside a shift, fall outside shifts as the result of the swap.
-
Partial Shift Swap: Minimum duration of the shift that can be swapped: <number>Percent or Minutes. This rule is violated if the duration of the swapped shift is less than the specified duration.
-
Partial Shift Swap: Minimum duration of the shift to leave after pickup: <number>Percent or Minutes. This rule is violated if the remaining shift duration after the swap is less than the specified duration.
-
Maximum paid duration allowed: <number> minutes per <Organization Day or 24 Hour Period>. This rule is violated if the request causes the paid duration to exceed the user-defined duration allowed for the selected period. Shift length is not considered; however, all paid hours during the selected period are considered. For the paid duration calculation, only paid hours are counted. Shift work (normal shifts, overtime, overtime extension) and time off are counted as paid hours. Flex time off segments are not counted as paid hours.
For the reference period that defines the day, select from the following options:
-
Organization Day: If all employees only have shifts that start and end in the organization day boundary, use this option.
During validation, the duration calculation uses the time period defined for the organization day. The organization day is defined on the Organization Setting page (located on the Organization Management menu, under Hierarchies). If the maximum paid duration threshold is exceeded, an alert is generated.
-
24 Hour Period: If any employees have shifts that cross the organization day boundary (shift starts on one day and ends on another day), use this option.
During validation, the duration calculation uses a sliding 24-hour window that increments by 15 minutes. The sliding window begins 24 hours + 15 minutes before the request start time and stops at 24 hours - 15 minutes after the request end time. If the maximum paid duration threshold is exceeded in a 24-hour window, the rule is violated. No more 24-hour windows are checked, and an alert is generated.
-
-
Partial Shift Swap: Activities that cannot be included in the swap: <activity name(s) from drop-down>. This rule is violated if the swap includes any of the specified activities.
-
Gap should be between <number> and <number> minutes, or at least <number> minutes. This rule is violated if the gap created as a result of the swap is outside the specified range, or if the gap is less than the specified duration. If both the range and the minimum are specified, the rule will be violated only if both the conditions are violated.
-
Maximum overlap with an existing shift:<number> minutes. This rule is violated if the overlap with an existing shift caused due to the swap is greater than the specified duration.
-
Maximum consecutive working days allowed as per organization Settings. This rule is violated if the maximum consecutive working days limit is exceeded.
This rule only checks the start of shifts (not the end dates).
The Maximum consecutive working days to schedule set on the Organization Settings page. under the Scheduler Options section. This page is located on Organization Management, under Hierarchies. For example, if the maximum consecutive working days count is set to three, and Employee A is requesting a one-way shift swap from 4/1 to 14/1 then the rule would validate if this shift swap would violate the maximum consecutive working day count for shifts from 1/1 to 1/17, and for the period 1/11 to 1/17.
-
Minimum required time gap between consecutive shifts as per organization Settings.
This rule is violated if the minimum time between the end of a first shift and the start of the next shift for all types of shift swap requests is not met.
The Minimum time between shift assignments is set on the Organization Settings page. under the Scheduler Options section. This page is located on Organization Management, under Hierarchies.
-
Maximum number of <number> one-way shift swap requests per<Month or Quarter>. This rule is violated if the number of one-way shift swaps requested exceeds the maximum number of one-way shift swap requests allowed per month or quarter.
When this rule is selected for an employee's organization, the One Way Shift Swap section is available on the following pages:
-
Time Summary: This page is located on Tracking, under Roster.
-
My Schedule Summary: This page is located on My Home, under My Schedule.)
This rule does not count a swap against the one-way swap limit if the employee picks up another shift on the day that was previouly given away.
-
-
Maximum number of approved swaps for a shift <number>. This rule is violated if the shift swap requested exceeds the maximum number of shift swaps allowed per shift.
-
Partial Shift Swap: Limit number of employees involved to <number>. This rule is violated if the number of employees who can receive swaps from the same shift is exceeded. This rule is limited to partial swaps.
-
Maximum hours per day <number> with an alternate maximum hours of <number> the day after the swap when the maximum hours were reached the day before. This rule is violated if either condition one or condition two is met.
-
Condition one: Maximum hours per day <number>
This rule condition is violated if the maximum hours per day limit is exceeded due to a shift swap (that is, an employee works a standard shift and picks up a shift from another employee).
-
Condition two: with an alternate maximum hours of <number> the day after the swap when the maximum hours were reached the day before.
This rule condition is violated if the maximum hours in the day after a shift swap limit is exceeded after the maximum hours per day limit was reached on the previous day.
Example of completed rule:
Maximum hours per day 12 with an alternate maximum hours of 10 the day after the swap when the maximum hours were reached the day before.
Example of results:
-
Condition one: If Employee A’s standard shift is 8 hours AND Employee A submits a request to pickup a 4-hour shift from Employee B on Monday, then the first condition of this rule is not violated. The maximum hours per day limit is reached, but not exceeded.
-
Condition one: If Employee C’s standard shift is 8 hours AND Employee C submits a request to pickup a 6-hour shift from Employee D on Monday, then the first condition of this rule is violated. The maximum hours per day limit is exceeded.
-
Condition two: If Employee A’s shift swap request for Monday is approved (total of 12 hours), AND Employee A submits a request to swap their 8-hour shift with Employee E’s 12-hour shift on the next day (Tuesday), then the rule is violated. The 12-hour work day on Tuesday exceeds the 10-hour limit for the day after a swap that reached the maximum hours limit per day.
-
-
-
Request complies with Required Pay Period Hours. This rule is violated if the employee’s shift swap request would cause the employee not to meet the minimum hours in a pay period.
Tracking for the Required Pay Period Hours is set up on the Settings page. This page is located on Organization Management, under Request Management. When this setting is selected for an employee's organization, the Required Hours (balance) for Pay Period section is available on the following pages:
-
Time Summary: This page is located on Tracking, under Roster.
-
My Schedule Summary: This page is located on My Home, under My Schedule.
One or more time-off activities must be set up to deduct from the Required Pay Period Balance. (This setting is on the Activities page, under the Request Management Usage section. This page is located on Work Administration, under Activities.
-
Approved Shift Swap Withdrawal Validation rules section
-
Request complies with filing rules. This rule is violated if the withdrawal request submittal date violates any of the filing rules applicable to the requester’s organization.
Shift Bidding Request Validation rules section
-
Request complies with filing rules. This rule is violated if the request submittal date violates any of the filing rules applicable to the employee’s organization.
-
Employee's schedule complies with min/max hours, including overtime maximums. This rule is violated if the requested schedule does not comply with the employee’s min/max hours for the week of the auction including the maximum overtime allowed per day or week.
-
Employee has the same skills as required for the selected schedule. This rule is violated if the employee does not have the same skills as the phantom employee the schedule was generated for. If an employee has more skills than required, this rule is violated.
-
Employee has sufficient skills for the selected schedule. This rule is violated if the employee does not have some skills in common with the phantom employee the schedule was generated for.
-
Employee's schedule complies with organization hours of operation. This rule is violated if any of the requested shifts in the shift bid fall outside the employee organization's hours of operation.
Shift Requests and Changes Validation rules section
-
A minimum of <x> percent of changed intervals improves net staffing. This rule is violated when the percentage of intervals that will be changed by the request is less than the specified minimum percentage for net staffing improvement. Gaps between shifts and extensions are not included.
The minimum staffing level percentage is calculated as follows:
Improvement Percentage = (#periods where net staffing is improved / (#periods where net staffing is improved + #periods where net staffing is worsened) )*100
-
Maximum paid duration allowed: <number> minutes per <Organization Day or 24 Hour Period>. This rule is violated if the request causes the paid duration to exceed the user-defined duration allowed for the selected period. Shift length is not considered; however, all paid hours during the selected period are considered. For the paid duration calculation, only paid hours are counted. Shift work (normal shifts, overtime, overtime extension) and time off are counted as paid hours. Flex time off segments are not counted as paid hours.
For the reference period that defines the day, select from the following options:
-
Organization Day: If all employees only have shifts that start and end in the organization day boundary, use this option.
During validation, the duration calculation uses the time period defined for the organization day. The organization day is defined on the Organization Setting page (located on the Organization Management menu, under Hierarchies). If the maximum paid duration threshold is exceeded, an alert is generated.
-
24 Hour Period: If any employees have shifts that cross the organization day boundary (shift starts on one day and ends on another day), use this option.
During validation, the duration calculation uses a sliding 24-hour window that increments by 15 minutes. The sliding window begins 24 hours + 15 minutes before the request start time and stops at 24 hours - 15 minutes after the request end time. If the maximum paid duration threshold is exceeded in a 24-hour window, the rule is violated. No more 24-hour windows are checked, and an alert is generated.
-
-
Minimum paid duration allowed: <number> minutes per <Organization Day or 24 Hour Period>. This rule is violated if the request causes the employee to fall under the user-defined duration allowed for the selected period. Shift length is not considered; however, all paid activities during the selected period are considered. For the paid duration calculation, only paid hours are counted. Shift work (normal shifts, overtime, overtime extension) and time off are counted as paid hours. Flex time off segments are not counted as paid hours.
For the reference period that defines the day, select from the following options:
-
Organization Day: If all employees only have shifts that start and end in the organization day boundary, use this option.
During validation, the duration calculation uses the time period defined for the organization day. The organization day is defined on the Organization Setting page (located on the Organization Management menu, under Hierarchies). If the minimum paid threshold is not met, an alert is generated.
-
24 Hour Period: If any employees have shifts that cross the organization day boundary (shift starts on one day and ends on another day), use this option.
During validation, the duration calculation uses a sliding 24-hour window that increments by 15 minutes. The sliding window begins 24 hours + 15 minutes before the request start time and stops at 24 hours - 15 minutes after the request end time. If the minimum paid duration threshold is not met after checking all windows, an alert is generated.
-
-
Minimum duration of the activity <adjustable break activity or shift gap activity> is <number> <Minutes or Hours> after an extension during the activity. This rule is violated if the minimum duration of the selected activity will not be met after an extension during the activity. (Until shift event activities are created for adjustable breaks or shift gaps, the list of break activities is empty.) Example - adjustable break activity: Employees get a 60 minute, unpaid lunch break for a shift that exceeds six hours. By law, they are required to take 30 minutes for lunch. You can define this rule with a minimum activity duration of 30 minutes to prevent employees from making their lunch break too short.
Two break segments can occur due to a gap--one segment before and one segment after the work extension. Only one of these break segments must meet the minimum duration requirement in this rule.
If you are defining this rule for multiple activities with the same duration, you can select all applicable activities and enter the duration once. If you are defining this rule for activities with different durations, define each activity separately. Also, you can save or cancel all activities at one time instead of processing them individually. By default, the first adjustable break activity shows in the list box.
To remove a maximum duration for an activity, set the duration to blank and save the change.
-
Maximum consecutive working days allowed as per organization Settings. This rule is violated if the request causes the user to exceed the maximum number of consecutive working days that has been defined for the organization.
-
Minimum required time gap between consecutive shifts as per organization Settings. This rule is violated if approving the shift change request results in the minimum time gap between shifts being violated. The time gap is determined by comparing the start time of the requested shift with the end time of the preceding shift; in addition the end time of the requested shift is checked against the start time of the succeeding shift.
-
Request complies with filing rules. This rule is violated if the request submittal date violates any of the filing rules applicable to the employee’s organization.
-
Employee’s schedule complies with min/max hours, including OT maximums. This rule is violated if approving the request causes the employee not to meet or to exceed the minimum or maximum hours allowed respectively, including the maximum overtime allowed per day/week.
-
Employee’s schedule complies with organization hours of operation. This rule will generate an alert if approving the request causes the employee’s working hours to fall outside the defined hours of operation for the organization.
-
Request does not overlap with a time off event Scheduled event in WFM that can be used to plan and track planned time off, such as vacations. To avoid the approval process associated with time-off requests made through the time-off management functionality, you can create time-off events directly in the calendar.. This rule is violated if the request overlaps with a time-off event.
-
Request does not overlap with an unavailability. This rule is violated if the shift change request overlaps with an unavailability.
-
Request period is published. This rule is violated if the request date and time range falls outside a published period. If any part of the shift is outside a published period, the validation fails.
-
Request complies with Required Pay Period Hours. This rule is violated if the request would cause the employee to not meet the minimum hours in a pay period.
Tracking for the Required Pay Period Hours is set up on the Settings page. This page is on Organization Management, under Request Management. When this setting is selected for an employee's organization, the Required Hours (balance) for Pay Period section is available on the following pages:
-
Time Summary: This page is located on Tracking, under Roster.
-
My Schedule Summary: This page is located on My Home, under My Schedule.
-
Approved Shift Requests and Changes Withdrawal Validation rules section
-
Request complies with filing rules. This rule is violated if the withdrawal request submittal date violates any of the filing rules applicable to the requester’s organization.
Define validation rules for time-off requests
Define validation rules for flex time requests
Define validation rules for shift bidding requests