Count Configuration Common Mistakes

Common Mistakes:

• Not attaching the Count Strategy to the positions included in the Target area. Roster Counts ultimately belong to Roster Count Strategies. A Roster Count will include and only act on positions attached to the same Roster Count Strategy.
• The Target area is excluding records that you want to count. The Target’s Days of the Week, Pre Filter, Timeframe and or Condition are excluding records that you want to count.
• The Target area is excluding the vacancy where you are performing a ROSTERCOUNTALARM(#) test. If the vacancy is not in the Target area then the ROSTERCOUNTALARM(#) will always test FALSE.
• The Target area includes many shifts of varying time frames; therefore the alarm is unexpectedly but correctly triggered. Further limit your Target using Timeframe, pre filters... to exclude unwanted records.
• The Target time frame is 24 hours off of the desired date and time. For example, a From of 03:00:00 is 3:00 a.m. of the target date. Sometimes 03:00:00+1day is called for.
• The level in the Alarm area is too low and therefore the totals are being cleared before the Over or Under threshold is reached.
• Unassigned records (a.k.a. Floaters) are counted if the same Roster Count Strategy is attached at the Region level or third level within the organizational structure.
• Roster Counts act on a Roster for a single date - not across Rosters for several dates.