TimeSimplicity & Other Product Ideas

If a TOR bucket is set to "Hide" in in the AccrueUpScript rule, then the employee should not be able to see this bucket or these balances when working in the ESS Portal or placing a TOR request.  Most of the time hidden buckets are for accrued hours that determine when an employee has reached a certain threshold which no longer entitles them to accrue additional TOR hours.

An example of this is NYC Sick Pay.

• The employee can accrue up to 40 hours per year
• The employee can use up to 40 hours per year
• The employee can carryover up to 40 hours per year

So, an Accrued Hours bucket keeps track of when they hit 40 hours and a separate Sick bucket keeps track of how many actual hours of Sick time they can use.  Once the Accrued Hours bucket reaches 40, both the Accrued Hours and Sick buckets stop accruing.

• As the employee exhausts their Sick time, the AccrueDownScript reduces their Sick balance but keeps their Accrued Hours balance the same.
• This way, if my accrued hours are already at 40.00 and I use 8.00 Sick hours, reducing my Sick balance from 40.00 to 32.00, since the system knows I already maxed out on what I can accrue, my Sick balance will remain at 32.00 hours and the system will not try to accrue an additional 8.00 hours to bring me back to 40.00.
• Because my accrued hours were already at 40.00, it knows whatever Sick time I'm using is taken off of the maximum amount I was allowed to accrueup for the year.

Having spelled that out, it doesn't seem like there's any benefit -- only confusion -- to be gleaned from showing the employee balances for hidden buckets.  They don't need to see their Accrued Hours -- they just need to know how much Sick time they have remaining.

Can hidden TOR buckets be completely hidden from employee view?