Time and Attendance
13620610
POST-14100
When a time code name contains a greater than (>) symbol, the greater than sign is displayed as ">" instead of ">" in the Code Summary of the timesheet.
Outcome
Fixed by not encoding the less than and greater than symbols for the time code name in the Code Summary of the timesheet.
13734755
POST-14407
The ETM schedule is displaying incorrect shift information when the shift is split in the ASV. When a shift is split using time codes (for example, 7:00-13:00 WRK; 13:00-14:00 CHARGE; 14:00-15:00 WRK), the individual splits are not displayed in the ETM schedule.
Outcome
Fixed. The splits are displayed when time code is configured to be a visible field on the page.
13784607
POST-14570
In POST-13118, validation logic was implemented to prevent the user from creating Schedule Detail overrides that overlap with Shift Pattern shifts. Prior to the validation, overlapping time between the override and the Shift Pattern shift was being counted twice on employee's timesheets.
As a result of the fix in POST-13118, if an affected retrospective scenario is recalculated, then the system generates retrospective adjustments, leading to overpayments due to the override error in the timesheet.
Outcome
Fixed by adding the SCHED_OVERLAP_VALIDATION_EFF_DATE registry parameter to make the validation in POST-13118 date effective. The date format for this registry is MM/dd/yyyy. For new installs, the default is set to 01/01/1900 to enable the validation. For upgrades, the default is set to 01/01/3000 to prevent unintended retros due to old data.
13814283
POST-14738
Employees entitled to a premium for hours worked within a Shift Premium Zone from 15:00 to 23:00 are not earning a premium for overnight shifts (for example, from 13:00 to 01:00). In this scenario, employees must be working on or after 18:01 to qualify for the premium.
The issue occurs because the date from the work detail end time is used with the time specified in the Must End Work On or After Time parameter.
Outcome
Fixed by adding new parameters to let you configure the date that is considered for the times specified in the Must Start Work and Must End Work parameters. The date can be the date from the work detail start time (default for Must Start Work times), date from the work detail end time (default for Must End Work times), or charge date. The default values preserve the existing logic.
13826323
POST-14613
When making a change to an employee record in the Supervisor Approval Worksheet and then clicking on another record without saving, a warning is not displayed about unsaved changes. When returning to the original edited record, the changes are lost.
Outcome
Fixed. A warning is displayed if there are unsaved changes when clicking on another record.
13844580
POST-14723
After configuring the employee information cards to display information on the employee's jobs, the preferred job is not shown on the timesheet and SAW.
Outcome
Fixed.
13847121
POST-14845
An HTTP 500 error occurs when selecting a time off type in mobility. The issue occurs when the name of the time off type contains '&'.
Outcome
Fixed.
13930170
POST-14892
The Create Default Records function is no longer working. New work summaries are not created for an employee.
Outcome
Fixed by using the appropriate method to get the employee IDs.
13934213
POST-14919
When searching for all teams on the Daily or Weekly Timesheet, a system error occurs.
Outcome
Fixed.
14045329
POST-15166
In the timesheet, when the security group permissions for EXPAND_COLLAPSE_DETAILS are set to Deny, the user cannot navigate to other date ranges using the Next and Prev buttons.
Outcome
Fixed.
14089871
POST-15345
When using the Balance Cascade Rule, a null error message is displayed on the timesheet and a NullPointerException is displayed in the Rule Tracer.
Outcome
Fixed. A balance value is only changed if the time code affects that balance.
14107431
POST-15389
Supervisor Approval Worksheet is taking anywhere between 3 and 7 minutes to load multiple teams with sub teams for a pay period.
Outcome
Improved the performance by loading employee full names from DTOs instead of from the DOM.
14123800
POST-15443
In the Supervisor Approval Worksheet, the date navigation area at the top of the screen is missing localization fields.
Outcome
Fixed by adding localization fields (NAV_SAW_FROM_DATE and NAV_SAW_TO_DATE).
14126110
POST-15491
In mobility, attestation messages are not displayed for the English UK locale.
Outcome
Fixed.
14128315
POST-15448
When clicking Save and Continue on the Employee Basic Information - Override form, there is no indication that the page is being saved or has saved.
Outcome
Fixed. Upon saving, "Your changes have been saved" is displayed at the top of the page.
14141511
POST-15546
When a user selects the Recall All option for a time off request, the Recall option is not populated for approved days in the time off request.
Outcome
Fixed by populating the Recall value for approved days.
14147100
POST-15517
When applying the Mass Edit Project override to set the value of the Project field, the Override Values field only shows 'Project='. A similar issue occurs with other mass edit overrides.
Outcome
Fixed.
14155404
POST-15580
When trying to run the Adjustment report for a single pay group, the message "You may only select employees with the same pay period" is displayed.
This issue occurs because the query is returning records with different pay periods when an employee is associated with multiple pay groups during the current pay period.
Outcome
Fixed by updating the query.
14214647
POST-15596
After editing the second ON clock on a day in the timesheet, the clock controls disappear and the change cannot be saved. The issue occurs if the previous clock is an OFF clock.
Outcome
Fixed.
14230792
POST-15657
The Daily Overtime Plus Rule is configured with these details: Hour Set Description is REG=480,OT1.5=360,OT2.0=9999, meaning first 8 hours is REG, next 6 hours is OT1.5, and the remaining hours is OT2.0; Can Continue From Yesterday is selected.
When work details are added to the day that start at the same time as when the OT1 hour type begins, the hour type is converted into OT1 and incorrectly calculated to 7 hours instead of 6 hours. As a result, OT2 is calculated incorrectly too.
If the edit takes place before the OT1 hour type begins (for example, OT1 begins at 11pm, the work detail start time is 10pm, and the end time is 11pm), there is no issue. The time is calculated correctly for 8 hours REG, next 6 hours of OT1.5, and the rest is OT2.0.
The issue occurs when there are multiple, consecutive work details with the same time code and hour type, but with different other labor metrics (for example, department).
Outcome
Fixed. Instead of checking the last eligible work detail, all of yesterday's details are considered to get the hour set info.
14237399
POST-15768
When using a timesheet detail filter, the filter is not being applied to the timesheet results.
Outcome
Fixed.
14260906
POST-15760
Using an '&' in a field name causes issues:
- A shift pattern containing '&' in the name cannot be assigned to an employee on the Employee Basic Information-Override screen.
- An override type containing '&' in the name is displayed as '&' on the timesheet.
Outcome
Fixed by removing encoding from DBLookupUI fields and override type names.