Dependability Rule Set Settings

Rule Settings

• Name: Name of the rule set.
• Description: A description of the rule set.
• How long should points be considered valid?: Defines the time frame to use when calculating dependability. There are three different options:
  1. Expire points on a rolling basis: Select this option button to expire dependability points on a rolling basis. You will set the roll-off window with the Points Valid For fields.
     • In the Points Valid For drop-down menu, select the unit of time for your roll-off window.
     • In the field in front of the drop-down menu, enter how many units your roll-off window is in length. For example, if you enter 6 in the first field and select Months in the drop-down menu, dependability points will expire six months after they are assigned.
  2. Expire points annually on specific dates (month and day): Select this option button to expire all dependability points on a date that you specify.
     • Click the blue text link Add New Date. A date selector appears.
     • Use the date selector to choose the date that you want dependability points to expire on. You can add multiple expiration dates; if you do so, points accumulated after the first expiration date but before the second will expire on the second expiration date. You can set up multiple dates if you want points to expire at regular intervals, every three months for example. If you want to remove a date, click the blue text link Remove Date next to that date.
  3. Expire points on employee anniversary: Select this option button to expire each employee’s dependability points on the anniversary of their hire date.
• Freeze points during active disciplinary actions: Check this box to freeze dependability points during active disciplinary actions. When there is an active disciplinary action, points set to expire (based on the method you selected in the previous rule) would not expire, and RosterApps would continue to consider those points valid until the disciplinary action is no longer active. The disciplinary action is active until the time period set by the ‘Active for’ field of the disciplinary action rule passes, and the disciplinary action expires. Even if a supervisor marks the disciplinary action completed, RosterApps still considers it active until the time period passes.
• Always use this rule set to calculate points from the past: Check this box to use this rule set for the entire time frame that dependability points are considered valid (established in rule C), regardless of which rule set was assigned on past dates. This is relevant if this rule set’s time frame overlaps a previously assigned rule set. Checking this box overrides previous rule sets that were assigned within this rule set’s current time frame, and points for past infractions/absences would be assigned according to this dependability rule set. Here’s an example:
  • Rule Set A has a rolling six-month point window, assigns one dependability point per absence, and is assigned to Emily’s work group from 1/1/2018 to 5/15/2018.
  • Rule Set B has a twelve-month rolling point window, assigns three dependability points per absence, and is assigned to Emily’s work group from 5/15/2018 to the present.
  • Emily has two absences: one marked on 5/1/2018 and one marked on 5/20/2018.
  • If Rule Set B has rule E turned on, Emily would receive 3 dependability points for each of the two absences, since RosterApps would use Rule Set B to calculate points up to a year in the past. If Rule Set B has rule E turned off, Emily would receive 1 dependability point for the absence on 5/1/2018 (because it was marked absent when Rule Set A was in effect) and 3 dependability points for the absence on 5/20/2018 (because Rule Set B was in effect).
• Allow supervisor to view dependability point balance: Check this box to allow supervisors to view employees’ dependability point balances.
• Allow supervisor to view dependability history: Check this box to allow supervisors to view employees’ dependability history. An employee’s dependability history shows any active dependability points and any disciplinary actions assigned to the employee.
• Allow schedule viewer to view dependability point balance: Check this box to allow schedule viewers to view employees’ dependability point balances.
• Allow schedule viewer to view dependability history: Check this box to allow schedule viewers to view employees’ dependability history. An employee’s dependability history shows any active dependability points and any disciplinary actions assigned to the employee.
• Allow time keeper to view dependability point balance: Check this box to allow time keepers to view employees’ dependability point balances.
• Allow time keeper to view dependability history: Check this box to allow time keepers to view employees’ dependability history. An employee’s dependability history shows any active dependability points and any disciplinary actions assigned to the employee.
• Allow employees to view dependability point balance: Check this box to allow employees to view their current dependability point balances. If you check this box, employees can view their dependability point balance by clicking a text link that reads ‘Get Current Dependability Point Balance’ on their RosterApps home page.
• Company admin can deduct dependability points: Check this box to allow Company Admin-level users to manually deduct dependability points. Users can do this while signed into RosterApps as Location Admins (Location Admin>Dependability tab), but only Location Admins that are also Company Admins will have this ability (unless you allow all Location Admins to deduct points in rule below).
• Company admin can manually add dependability points: Check this box to allow Company Admin-level users to manually add dependability points. Users can do this while signed into RosterApps as Location Admins (Location Admin>Dependability tab) but only Location Admins that are also Company Admins will have this ability (unless you allow all Location Admins to add points in rule below).
• Company admin can edit manual dependability points: Check this box to allow Company Admin-level users to edit dependability points that have been added or deleted manually. Users can do this while signed into RosterApps as Location Admins (Location Admin>Dependability tab) but only Location Admins that are also Company Admins will have this ability (unless you allow all Location Admins to edit points in rule below).
• Company admin can delete manual dependability points: Check this box to allow Company Admin-level users to delete dependability points that have been added or deleted manually. Users can do this while signed into RosterApps as Location Admins (Location Admin > Dependability tab) but only Location Admins that are also Company Admins will have this ability (unless you allow all Location Admins to delete points in rule below).
• Location Admin can deduct dependability points: Check this box to allow Location Admin-level users to manually deduct dependability points.
• Location Admin can manually add dependability points: Check this box to allow Location Admin-level users to manually add dependability points.
• Location Admin can edit manual dependability points: Check this box to allow Location Admin-level users to edit dependability points that have been added or deducted manually.
• Location Admin can delete manual dependability points: Check this box to allow Company Admin-level users to delete dependability points that have been added or deducted manually.
• Company admin can remove disciplinary actions from dependability history: Check this box to allow Company Admin-level users to remove disciplinary actions from employees’ dependability histories. Users can do this while signed into RosterApps as Location Admins (Location Admin > Dependability tab), but only Location Admins that are also Company Admins will have this ability.
• Location admin can undo completed disciplinary actions: Check this box to allow Location Admin-level users to undo disciplinary actions that have been marked completed. This makes the disciplinary action active again and it would need to be marked complete.
• Allow disciplinary actions to be assigned to and completed by schedule viewers: Check this box to allow disciplinary actions to be assigned to and marked completed by Schedule Viewers.
• Allow employees to view dependability point rules: Check this box to allow employees to view the dependability point rules. Employees will not be able to edit dependability point rules. This rule is located under the Dependability Point Rules table.
• Allow employees to view disciplinary action rules: Check this box to allow employees to view the disciplinary action rules. Employees will not be able to edit disciplinary action rules. This rule is located under the Disciplinary Action Rules table.
• When adding points triggers multiple disciplinary actions, only apply the one with highest point threshold: Check this box if only a single disciplinary action should be triggered in the case when multiple thresholds are crossed.
• Allow employees to view exceptions: Check this box to allow employees to view rule exceptions. Employees will not be able to edit rule exceptions. This rule is located under the Rule Exceptions table.

Add/Edit/Delete Dependability Point Rules

Dependability point rules establish which employee actions generate dependability points, and the number of points they generate.

Add Dependability Point Rules

To add a dependability point rule:

• Click the blue Add new dependability point rule text link directly above the Dependability Point Rules table on the righthand side.

• RosterApps opens an Add Dependability Point Rule box.

• Complete the sections in this box with information about the new dependability point rule. Sections with a red asterisk are required. Below is a list of sections with descriptions:
  • Name: The name of the dependability point rule.
  • Infraction Types: Check the box(es) of the infraction type(s) that trigger the dependability point rule. You must choose at least one infraction type or absent reason (below). You can choose one or more of each. If you select both infraction type(s) and absent reason(s), a shift will need to have at least one of the selected infraction types and at least one of the selected absent reasons to match the dependability point rule.
  • Absent Reasons: Check the box(es) of the absent reason(s) that trigger the dependability point rule. You must choose at least one absent reason or infraction type (above). You can choose one or more of each. If you select multiple, a shift will need to have at least one of the selected absent reasons and at least one of the selected infraction types to match the dependability point rule.
  • Shift Classifications: Check the box(es) of the type(s) of shifts that can generate dependability point rules. If the infraction type(s) and/or absent reason(s) you have selected occur on the type of shift you select here, RosterApps will assign dependability points. For example, if you selected the absent reason Sick and the shift classification Traded Shift, any time a supervisor marks an employee sick on a traded shift, the employee will receive dependability points per this dependability point rule. The color in parentheses next to the shift classification is the color that shift classification appears on employee calendars. If multiple shift classifications are selected, the shift only needs to match one to match the dependability point rule.
  • Points: The number of dependability points that employees receive when they trigger this dependability point rule.
  • Min Length of Absence: Enter the minimum length of absence/infraction that will trigger this dependability point rule and use the drop-down menu to select the unit of length. If the shift matches an infraction type that is in/out early or late, the length will be the infraction length. Otherwise, the length will be the total duration of the shift. Entering this value is optional.
  • Max Length of Absence: Enter the maximum length of absence/infraction that will trigger this dependability point rule and use the drop-down menu to select the unit of length. If the shift matches an infraction type that is in/out early or late, the length will be the infraction length. Otherwise, the length will be the total duration of the shift. Entering this value is optional.
• Click the Done button to create your new rule (or click the Cancel button to cancel).
• The dependability point rule now appears in the Dependability Point Rules table.

Edit Dependability Point Rules

To edit a dependability point rule:

• Find the dependability point rule that you would like to edit in the Dependability Point Rules table. Click the text link Edit in that dependability point rule’s row.

• RosterApps opens an Edit Dependability Point Rule box.

• Edit any of the sections in this box as needed. Sections with a red asterisk are required. Below is a list of sections with descriptions:
  • Name: The name of the dependability point rule.
  • Infraction Types: Check the box(es) of the infraction type(s) that trigger the dependability point rule. You must choose at least one infraction type or absent reason (below). You can choose one or more of each. If you select both infraction type(s) and absent reason(s), a shift will need to have at least one of the selected infraction types and at least one of the selected absent reasons to match the dependability point rule.
  • Absent Reasons: Check the box(es) of the absent reason(s) that trigger the dependability point rule. You must choose at least one absent reason or infraction type (above). You can choose one or more of each. If you select both infraction type(s) and absent reason(s), a shift will need to have at least one of the selected absent reasons and at least one of the selected infraction types to match the dependability point rule.
  • Shift Classifications: Check the box(es) of the type(s) of shifts that can generate dependability point rules. If the infraction type and/or absent reason you have selected occur on the type of shift you select here, RosterApps will generate dependability points. For example, if you select the absent reason Sick and the shift classification Traded Shift, any time a supervisor marks an employee sick on a traded shift, they will receive dependability points per this dependability point rule. The color in parentheses next to the shift classification is the color that shift classification appears on employee calendars. If multiple shift classifications are selected, the shift only needs to match one to match the dependability point rule.
  • Points: The number of dependability points that employees receive when they trigger this dependability point rule.
  • Min Length of Absence: Enter the minimum length of absence/infraction that will trigger this dependability point rule here and use the drop-down menu to select the unit of length. If the shift matches an infraction type that is in/out early or late, the length will be the infraction length. Otherwise, the length will be the total duration of the shift. This value is optional.
  • Max Length of Absence: Enter the maximum length of absence/infraction that will trigger this dependability point rule here and use the drop-down menu to select the unit of length. If the shift matches an infraction type that is in/out early or late, the length will be the infraction length. Otherwise, the length will be the total duration of the shift. This value is optional.
• Click the Done button to save your changes or click the Cancel button to cancel.

Delete Dependability Point Rules

To delete a dependability point rule:

• Find the dependability point rule you would like to delete in the Dependability Point Rules table. Click the text link Delete in that dependability point rule’s row.

• RosterApps asks if you are sure you want to delete the dependability point rule. Click the Continue With Delete button to continue (or click the Cancel button to cancel).
• The dependability point rule no longer appears in the Dependability Point Rules table.

Add/Edit/Delete Disciplinary Action Rules

Disciplinary action rules establish disciplinary actions and the conditions under which RosterApps assigns them to employees. RosterApps automatically assigns disciplinary actions to employees using these rules that you create, and then a Location Admin must either mark the disciplinary action as completed or assign it to a supervisor or schedule viewer to administer and mark complete.

 

Add Disciplinary Action Rules

To add a disciplinary action rule:

• Click the blue text link Add new disciplinary action rule, directly above the Disciplinary Action Rules table on the righthand side.

• RosterApps opens an Add Disciplinary Action Rule box.

• Complete the sections in this box with information about the new disciplinary action rule. Sections with a red asterisk are required. Below is a list of sections with descriptions:
  • Name: The name of the disciplinary action.
  • Description: A description of the disciplinary action.
  • Active for: The length of time that the disciplinary action remains active, regardless of whether it is marked completed or not. The disciplinary action will remain in the dependability history until this time period passes, unless the time period specified in rule C of the dependability rule set is longer, in which case the disciplinary action will disappear from the history once that time period passes. Choose the unit of time with the drop-down menu and enter the number of units in the field.
  • Trigger Event: The event that triggers the disciplinary action. You have two choices of trigger events—point thresholds or absent reasons.
    1. Point Threshold: Choose this option if you want a certain number of dependability points to trigger the disciplinary action.
       • Click the Point Threshold button.
       • Minimum points for action: Enter the number of dependability points that will trigger the disciplinary action.
       • Dependent on following another disciplinary action: Check this box to make this disciplinary action dependent on following another disciplinary action. If selected, this rule won’t be assigned to an employee until the disciplinary action it is dependent on is assigned and marked complete. Each disciplinary action can only be dependent on one other action. This option only appears if you have at least one other disciplinary action already established.
    2. Absent Reason: Choose this option if you want a certain number of absences to trigger the disciplinary action.
       • Click the Absent Reason button.
       • Require disciplinary action after [number] of the following absence reasons/types: In the field, enter the number of absences that will trigger the disciplinary action. Use the drop-down menu to select whether these are consecutive occurrences or total occurrences.
       • Infraction types: Check the box(es) of any infraction type(s) that will trigger the disciplinary action. You must choose at least one infraction type or one absent reason. You can have one or more from both.
       • Absent reasons: Check the box(es) of any absence reason(s) that will trigger the disciplinary action. You must choose at least one absent reason or one infraction type. You can have one or more from both.
       • Shift Classifications: Check the box(es) of the type(s) of shifts that can generate the disciplinary action. If the infraction type and/or absent reason you have selected occur on the type of shift you select here, the number of times you established above, RosterApps will generate the disciplinary action. The color in parentheses next to the shift classification is the color that shift classification appears on employee calendars.
  • Can be postponed by administrator: Check this box to allow Location Admins to delay the assignment of the disciplinary action.
• Click the Done button to create the disciplinary action rule (or click the Cancel button to cancel).
• The new disciplinary action rule now appears in the Disciplinary Action Rules table.

Edit Disciplinary Action Rules

To edit a disciplinary action rule:

• Find the disciplinary action that you want to edit in the Disciplinary Action Rules table. Click the text link Edit in that disciplinary action’s row.

• RosterApps opens the Edit Disciplinary Action box.

• Edit the sections on this page as needed. Sections with a red asterisk are required. Below is a list of sections with descriptions:
  • • Name: The name of the disciplinary action.
    • Description: A description of the disciplinary action.
    • Active for: The length of time that the disciplinary action remains active, regardless of whether it is marked completed or not. The disciplinary action will remain in the dependability history until this time period passes, unless the time period specified in rule C of the dependability rule set is longer, in which case the disciplinary action will disappear from the history once that time period passes. Choose the unit of time with the drop-down menu and enter the number of units in the field.
    • Trigger Event: The event that triggers the disciplinary action. You have two choices of trigger events—point thresholds or absent reasons.
      1. Point Threshold: Choose this option if you want a certain number of dependability points to trigger the disciplinary action.
         • Click the Point Threshold button.
         • Minimum points for action: Enter the number of dependability points that will trigger the disciplinary action.
         • Dependent on following another disciplinary action: Check this box to make this disciplinary action dependent on following another disciplinary action. If selected, this rule won’t be assigned to an employee until the disciplinary action it is dependent on is assigned and marked complete. Each disciplinary action can only be dependent on one other action. This option only appears if you have at least one other disciplinary action already established.
      2. Absent Reason: Choose this option if you want a certain number of absences to trigger the disciplinary action.
         • Click the Absent Reason button.
         • Require disciplinary action after [number] of the following absence reasons/types: In the field, enter the number of absences that will trigger the disciplinary action. Use the drop-down menu to select whether these are consecutive occurrences or total occurrences.
         • Infraction types: Check the box(es) of any infraction type(s) that will trigger the disciplinary action. You must choose at least one infraction type or one absent reason. You can have one or more from both.
         • Absent reasons: Check the box(es) of any absence reason(s) that will trigger the disciplinary action. You must choose at least one absent reason or one infraction type. You can have one or more from both.
         • Shift Classifications: Check the box(es) of the type(s) of shifts that can generate the disciplinary action. If the infraction type and/or absent reason you have selected occur on the type of shift you select here, the number of times you established above, RosterApps will generate the disciplinary action. The color in parentheses next to the shift classification is the color that shift classification appears on employee calendars.
    • Can be postponed by administrator: Check this box to allow Location Admins to delay the assignment of the disciplinary action.
• Click the Done button to save the changes (or click the Cancel button to cancel).

Delete Disciplinary Action Rules

To delete a disciplinary action rule:

• Find the disciplinary action rule that you want to delete in the Disciplinary Action Rules table. Click the text link Delete in that disciplinary action rule’s row.

• RosterApps asks if you are sure you want to delete the disciplinary action rule. Click the Continue With Delete button to delete the disciplinary action rule (or click the Cancel button to cancel).

• The disciplinary action rule no longer appears in the Disciplinary Action Rules table.

Add/Edit/Delete Rule Exceptions

Rule exceptions are exceptions to dependability point rules. You may use a rule exception if there are certain situations where you don’t want dependability points assigned or want a different number of dependability points assigned than RosterApps would normally assign according to your dependability point rule.

Add Rule Exceptions

To add a rule exception:

• Click the blue text link Add new exception, directly above the Rule Exceptions table on the righthand side.

 

• RosterApps opens the Add New Exception Rule box.

• Complete the sections in this box with information about the new rule exception. Sections marked with a red asterisk are required. Below is a list of sections with descriptions:
  • Dependability Point Rules: This section lists all of the dependability point rules at your company. Check the box of the dependability point rule(s) that this rule exception applies to.
  • Type: The type of exception that this will be. There are two choices—Point Change or Ignore Occurrences.
    1. Point Change: Choose this rule exception type if after a certain number of occurrences of the trigger event(s) you want to assign a different number of dependability points than the dependability point rule(s) typically assigns.
       • Click the Point Change button.
       • After [X][drop-down menu] employees will receive [X] points: In the first field, enter the number of occurrences of the trigger event after which employees will receive a different number of dependability points than the dependability point rule typically assigns. Use the drop-down menu to select whether these are consecutive occurrences or total occurrences. In the next field enter the new number of points that employees will receive after they have reached the number of occurrences.
       • Shift classifications that break consecutive pattern: If you selected ‘consecutive occurrences’ in the drop-down menu above, choose any shift classifications (or types) that would interrupt that consecutive pattern. For example, say in the above section you selected 3 consecutive occurrences. That would mean that after an employee had absences/infractions that triggered dependability points on three shifts in a row, the rule exception would apply. However, if you then select Traded Shifts in this section, a traded shift would break the consecutive pattern. So, if an employee did a triggering event on three shifts in a row but one of those shifts was a traded shift, the traded shift would not count towards consecutive occurrences and the rule exception would not apply. Shifts after the traded shift would also not be considered consecutive with the shifts before the traded shift, because the traded shift interrupted the consecutive pattern.
       • Normally scheduled days off will break consecutive pattern: Check this box if you want an employee’s regularly scheduled days off to break the consecutive pattern. This means that a shift on an employee’s Friday and a shift on the employee’s Monday would not be considered consecutive.
       • If a shift not matching an attendance point rule comes from the same parent (pre-split) shift as a later shift matching an attendance point rule, the first shift DOES NOT break the consecutive pattern: Check this box if in the event that a shift is split and one of the shift segments has a dependability point trigger event attached to it but the other segment does not, you do not want the segment without the trigger event to break the consecutive pattern. This means that if shifts directly before the split shift contain a trigger event, the split shift will be considered consecutive, and so will shifts after it. The name of this rule is somewhat misleading—the rule applies whether the first or second shift segment contains the trigger event.
       • Only require one shift per day to match an attendance point rule to keep the consecutive pattern: Check this box if in the event that an employee has multiple shifts in a day and one of them has a trigger event attached to it, you want to consider that shift consecutive with shifts that occur on the days before and after it (if those shifts have trigger events), regardless of whether or not other shifts on the same day have trigger events.
    2. Ignore Occurrences: Choose this rule exception type if you want RosterApps to ignore the first occurrences of a trigger event.
       • Click the Ignore Occurrences button.
       • Ignore first [X] occurrences of this absence: Enter the number of occurrences of the trigger event that you want RosterApps to ignore. For example, if you enter 3 in this field, RosterApps will ignore the first three times an employee does a trigger event, within the current valid time window. RosterApps would only consider the fourth trigger event that occurs within the valid time window.
• Click the Done button to save the rule exception (or click Cancel to cancel).
• The rule exception now appears in the Rule Exceptions table.

Edit Rule Exceptions

To edit a rule exception:

• Click on the Dependability tab.
• Find the rule exception you would like to edit in the Rule Exceptions table. Click the text link Edit in that rule exception’s row.

• RosterApps opens the Edit Rule Exception box.

• Edit the sections in this box as needed. Below is a list of the sections with descriptions:
  • Dependability Point Rules: This section lists all of the dependability point rules at your company. Check the box of the dependability point rule(s) that this rule exception applies to.
  • Type: The type of exception that this will be. There are two choices—Point Change or Ignore Occurrences.
    1. Point Change: Choose this rule exception type if after a certain number of occurrences of the trigger event(s) you want to assign a different number of dependability points than the dependability point rule(s) typically assigns.
       • Click the Point Change button.
       • After [X][drop-down menu] employees will receive [X] points: In the first field, enter the number of occurrences of the trigger event after which employees will receive a different number of dependability points than the dependability point rule typically assigns. Use the drop-down menu to select whether these are consecutive occurrences or total occurrences. In the next field enter the new number of points that employees will receive after they have reached the number of occurrences.
       • Shift classifications that break consecutive pattern: If you selected ‘consecutive occurrences’ in the drop-down menu above, choose any shift classifications (or types) that would interrupt that consecutive pattern. For example, say in the above section you selected 3 consecutive occurrences. That would mean that after an employee had absences/infractions that triggered dependability points on three shifts in a row, the rule exception would apply. However, if you then select Traded Shifts in this section, a traded shift would break the consecutive pattern. So, if an employee did a triggering event on three shifts in a row but one of those shifts was a traded shift, the traded shift would not count towards consecutive occurrences and the rule exception would not apply. Shifts after the traded shift would also not be considered consecutive with the shifts before the traded shift, because the traded shift interrupted the consecutive pattern.
       • Normally scheduled days off will break consecutive pattern: Check this box if you want an employee’s regularly scheduled days off to break the consecutive pattern. This means that a shift on an employee’s Friday and a shift on the employee’s Monday would not be considered consecutive.
       • If a shift not matching an attendance point rule comes from the same parent (pre-split) shift as a later shift matching an attendance point rule, the first shift DOES NOT break the consecutive pattern: Check this box if in the event that a shift is split and one of the shift segments has a dependability point trigger event attached to it but the other segment does not, you do not want the segment without the trigger event to break the consecutive pattern. This means that if shifts directly before the split shift contain a trigger event, the split shift will be considered consecutive, and so will shifts after it. The name of this rule is somewhat misleading—the rule applies whether the first or second shift segment contains the trigger event.
       • Only require one shift per day to match an attendance point rule to keep the consecutive pattern: Check this box if in the event that an employee has multiple shifts in a day and one of them has a trigger event attached to it, you want to consider that shift consecutive with shifts that occur on the days before and after it (if those shifts have trigger events), regardless of whether or not other shifts on the same day have trigger events.
    2. Ignore Occurrences: Choose this rule exception type if you want RosterApps to ignore the first occurrences of a trigger event.
       • Click the Ignore Occurrences button.
       • Ignore first [X] occurrences of this absence: Enter the number of occurrences of the trigger event that you want RosterApps to ignore. For example, if you enter 3 in this field, RosterApps will ignore the first three times an employee does a trigger event, within the current valid time window. RosterApps would only consider the fourth trigger event that occurs within the valid time window.
• Click the Done button to save your changes (or click the Cancel button to cancel).

Delete Rule Exceptions

To delete a rule exception:

• Find the rule exception that you want to delete in the Rule Exceptions table. Click the text link Delete in that rule exception’s row.

• RosterApps asks if you are sure that you want to delete the rule exception. Click the Continue with delete button to continue (or click the Cancel button to cancel).
• The rule exception no longer appears in the Rule Exceptions table.