Skip to main content

Time & Attendance Release Notes June 11 2026

  • June 26, 2026
  • 0 replies
  • 7 views
Sparky
NEOGOV Employee
Forum|alt.badge.img

Timeline

 

When will this be released?

Thursday, 06/11/2026 at 5 PM PST.

 

Is there downtime for this release?

No.

 

New Time Rule - “Add Lunch”

 

Some customers have the need for hours to be deducted from a shift on a timesheet entry for lunch time. This time rule provides the ability to define the number of hours of worked before the lunch is applied and the length of the lunch.

Value

Currently, the way lunch is deducted it is applied at the beginning using the Deduct Lunch time rule. This sometimes results in the employee's shift differential (shift premiums) to be paid incorrectly.

Audience

Primary Users - Administrators.

Example 1

  • Employee Shift - 0800-1600
  • Time Rule Setup
    • ADD LUNCH
      • Min Hrs Worked - 4
      • Lunch Length - 1
  • Result
    • Shift - 0800-1200 Reg
    • Lunch - 1200-1300 (Lunch defined Time code)
    • Shift - 1300-1600 Reg

Example 2

  • Employee Shift - 0800-1600
  • Time Rule Setup
    • ADD LUNCH
      • Min Hrs Worked - 8
      • Lunch Length - 1
  • Result
    • Invalid setup - no lunch applied.

Example 3

  • Employee Shift - 0800-1600
  • Time Rule Setup
    • ADD LUNCH
      • Min Hrs Worked - 7
      • Lunch Length - 1
  • Result
    • Shift - 0800-1500
    • Lunch - 1500-1600

Example 4

  • Employee Shift - 0600-1800
  • Time Rule Setup
    • ADD LUNCH
      • Min Hrs Worked - 5
      • Lunch Length - 1
    • Prem Time Of Day
      • From Time - 2300
      • To Time - 0700
      • Prem Time Code - Night Differential
    • Prem Time Of Day
      • From Time - 1500
      • To Time - 2300
      • Prem Time Code - Afternoon Differential
  • Result
    • Night Differential - 0600-0700
    • Shift - 0700-1200
    • Lunch - 1200-1300
    • Shift - 1300-1500
    • Afternoon Differential - 1500-1800

 

Bugs Resolved

 

Functional

 

Scenario When Issue Encountered Issue Resolved
(TA-14640) When the IMUSL rollout was implemented, consideration for the migrating of existing IMFOS Cost Center configurations to IMUSL was missed. Agencies that had Cost Center marked as required in IMFOS were left with a "Default" (non-enforcing) setting in IMUSL, silently breaking their mandatory field requirement. A database script has been run to copy the IMFOS permissions for the time sheet cost center field to the IMUSL Cost Center configuration.
(TA-14527) A regression bug was identified where the UACALC report threw a database error whenever a Leave Type name exceeded 40 characters. The system now supports 60 characters for Leave Type names.
(TA-14392) On the Clock Entries screen a regression bug was identified where double-clicking the Save button after adding a new clock entry resulted in duplicate punch records. The Clock Entries screen now correctly creates only a single punch record per Save action, even when the button is double-clicked.
(TA-15084) After an approved Leave request made in the Schedule product the integration API was incorrectly removing the leave request along with the shift information the employee was previously scheduled for. The integration delete API From Schedule to Time and Attendance was corrected to stop removing child records to the employees’ schedule being deleted.

 

508(C) Compliance

 

Screen(s) Count of Bugs Resolved
N/A N/A

 

    This topic has been closed for replies.
    Terms & ConditionsAccessibility statement