Time and Attendance
POST-16403
When applying an LTA using a newly created time off type in the Time Off Request form, the time code is not displayed in the ETM calendar upon approval of the request.
Outcome
Fixed.
13798309
POST-17647
Re-importing the employee data import file changed employee team assignments from the terminated team to the employee's previously assigned team.
Outcome
Fixed by not checking the employee inactive status during the employee import.
14136831
POST-15536
The Employees field in the Mass Edit Creation maintenance form cannot be configured.
Outcome
Fixed.
14138055
POST-15476
In mobility, when an employee scheduled from 11:00p to 7:00a submits a partial day time off request from 3:00a to 7:00a (for the following day), upon approval the LTA shown on the My Schedule page is displayed as 7:00a-7:00a. The issue occurs when the Apply Only When Scheduled option is not selected for the time code associated with the time off request.
Outcome
Fixed.
14146421
POST-15774
In the Weekly Timesheet, when trying to copy elapsed time overrides from the previous week using the Same as Last Week option in the Enter Elapsed Time section, the overrides are not copied to the current week.
Outcome
Fixed.
14160308
POST-15670
When submitting a single request from the Time Off Calendar for multiple days with a day gap in between (for example, January 20-21 and January 23-24), a NullPointerException occurs in the Time Off Approval page in mobility.
Outcome
Fixed.
14248464
POST-16487
The Daily Overtime Plus Rule is only considering the last WRK detail from the previous day when using the parameter "Can Continue From Yesterday".
This issue was addressed in POST-15657. However, that ticket did not address scenarios with multiple consecutive work details with a different time code (BRK) and hour type (UNPAID) in between.
Outcome
Fixed by keeping The OT meter running until it finds a detail that matches the "Overtime Reset Description".
14266547
POST-15809
When an employee clocks in a couple of minutes late and then performs a labor metric punch within the grace period specified in the Graces Rule, the on time code that was within the grace period is changed to a late time code. If the labor metric punch is outside of the grace period, then the timesheet is calculated correctly and the grace period is granted.
Outcome
Fixed by continuing to look for all eligible work details even after encountering an eligible work detail.
14291237
POST-15850
The work detail rate does not change when the Rate Type parameter is set to BASE in the Apply Pay Rates Rule.
Outcome
Fixed by introducing a new Rate Type option named FORCE BASE RATE, which updates the work detail rate to the employee's base rate. The existing BASE option was renamed to DEFAULT.
14297394
POST-16147
When using the Employee Import task to change an employee's hire date, an error occurs if the start date of the employee override is 01/01/1900:
Employee and/or Employee History was not found or was not loaded
The issue occurs because the task is trying to load employee history on the day before the earliest employee date (31/12/1899).
Outcome
Fixed by adding a check to ignore date before the earliest employee date and after the latest employee date.
14301002
POST-15864
When applying retroactive adjustments to an already exported pay period, an error shows in the Job Scheduler task or under import transaction for payroll export.
Outcome
Fixed by checking if list is null or empty before deleting the timesheet lock.
14319667
POST-16081
When applying the Sched Times W Breaks Override for a date in a previous pay period, a warning message is not displayed in the pop-up. A warning message is displayed in the other override pop-ups.
Outcome
Fixed by implementing the warning message for the Sched Times W Breaks Override pop-up.
14325782
POST-16135
When an accrual policy is assigned to an employee, the balances for the policy are displayed on the day before the effective start date and are not displayed on the effective end date in the timesheet. The issue occurs when the BALANCE_ADMIN_BY_EMP_POLICY registry parameter is set to true.
Outcome
Fixed by getting the start-of-day balance and calculating the end-of-day balance by adding the balance logs for the day.
14336498
POST-16137
When trying to compare/migrate any Shift Premium Zone from one environment to another using the 6.4.0.9 migration tool, an error "Table SHIFT_PREMIUM_ZONE_DTTYPE is not defined" occurs.
Outcome
Fixed by adding definition for SHIFT_PREMIUM_ZONE_DTTYPE for both table and functional object types.
14365240
POST-16204
A NullPointerException sometime occurs when calling wbData.getClocks.
Outcome
Fixed by checking whether clock.type is null and verifying the length of $dataType.length before updating the data text field in the clock popup.
14377177
POST-16235
When using the Weekly Overtime Plus Rule with the Apply overtime as a premium option, the premium seems to be hardcoded as having a rate of 0.
The premium rate is calculated as the employee base rate multiplied by the hour type multiplier of the first EDLA record. If the hour type of the EDLA record has a multiplier of 0 (UNPAID), the premium will have a rate of 0.
Outcome
Fixed by adding a new option named Calculate Rate. When this option is selected, the premium rate is calculated as the employee base rate multiplied by the premium hour type multiplier. By default, this option is cleared to preserve the existing behavior.
14397195
POST-16262
When editing labor metric security group permissions, a system error occurs if more that one criteria (for example, security group and calculation group) is specified on a row.
Outcome
Fixed by showing an appropriate error message when the user tries to save a row with more than one criteria. Only one of security group, team, calculation group, or pay group can be selected on a row.
14407707
POST-16447
When a user deletes a clock from the timesheet and clicks Submit, the clock is still on the timesheet the next time the user logs in. A system error occurs when the user tries to delete the clock again.
The issue occurs because of a foreign key constraint violation while trying to insert the work detail record.
Outcome
Fixed.
14413674
POST-16396
A work detail is added to the timesheet and submitted. Then the work detail Start Time and End Time fields are restricted to VIEW. When the user returns to the timesheet and tries to delete the work detail with the trash can icon at the end of the row, the page just refreshes and no change is made. A NullPointerException is also seen at times.
The issue occurs because of a foreign key constraint violation while trying to insert the work detail record.
Outcome
Fixed.
14457081
POST-16525
When applying two different premium overrides with the same time code to the timesheet using the pencil icon, only the latest override is shown. The issue occurs when the PREMIUMS_REPLACE_SAME_TIMECODE registry parameter is set to False.
Outcome
Fixed.
14463866, 14463842, 14467957
POST-16466
When using Relief Management area to reassign employees who are currently scheduled, get an unhandled error.
Outcome
Fixed. Calculate employee balances for each batch of employee balance logs, then update the calculated employee balance at once in the database.
14476599
POST-16496
The Position field cannot be updated in the timesheet. This issue also applies to the Department field and Team field.
The issue can occur when a field column is displayed in work premiums, but not displayed in work details (HiddenUI).
Outcome
Fixed by appending the work detail values in the request.
14511389
POST-16601
The Daily Overtime Plus Rule counts records with ineligible hour types on the prior day toward the hour set calculation when the Can Continue From Yesterday parameter is selected.
Example rule configuration:
- Hour Set Description: REG=480, OT1=9999
- Work Detail Hour Types: REG
- Work Detail Time Codes: WRK
- Overtime Reset Description: GAP=1
- Can Continue From Yesterday?: Selected
- Required Rest: 480
- Apply overtime to work detail records: Selected
- First hour type changes work detail hour types: Selected
- Assign equal or better hour type to eligible work details: Selected
For example, an employee has 2 hours on the previous work day from 17:00 to 19:00 with the WRK time code and the OT1 hour type. On the current work day, the employee has 9 hours of WRK from 2:00 to 11:00, which are calculated by the rule as 6 hours of REG (2:00 to 8:00) and 3 hours of OT1 (8:00 to 11:00). Although the hours on the previous day are within the 8 hours of specified rest time, those hours should not be eligible since OT1 was not specified in the Work Detail Hour Types parameter.
The issue occurs because yesterday's eligible hour types are calculated using the hour types from both the Hour Set Description and Work Detail Hour Types parameters.
Outcome
Fixed by adding a new rule parameter named "Limit to Eligible Details" under the Can Continue From Yesterday parameter. By default, the Limit to Eligible Details parameter is not selected to preserve the current behavior. When the Limit to Eligible Details parameter is selected, only the configured eligible parameters will be used to calculate the minutes from yesterday. Using the scenario above, the rule would calculate 8 hours of REG and 1 hour of OT1 on the current work day, as the OT1 hours on the previous day would not be eligible.
The hour types in the Hour Set Description parameter are still used to determine the rest period between yesterday and today.
14521620
POST-16654
When trying to open a shift swap request in mobility to accept it or reject it, a system error occurs with a warning.
Outcome
Fixed.
14523069, 14752947
POST-16672
Break time is not excluded when work time is calculated by the Daily Overtime Plus Rule, Weekly Overtime Plus Rule, and Guarantees Plus Rule.
Outcome
Introduced new parameter Deduct Breaks from Schedule Duration when configuring these rules. This parameter allows users to exclude all breaks, exclude unpaid breaks, or include all break time.
14523397
POST-16809
When configuring an EMP_VAL field to show on the employee information card in the timesheet and LFSO schedule, the value of the field is not displayed. The issue occurs when the EMP_VAL has been configured as a DataPickerUI and a date format has been specified.
Outcome
Fixed.
14525690
POST-16703
After a manager updates the employee rate on the timesheet, the Change Time Code Hour Type Duration Rule changes this worked rate back to the employee base rate when the rule triggers.
Outcome
Fixed by adding a new option named Use Current Rate. When this option is selected, the rule uses the current rate instead of the base rate. By default, this option is cleared to preserve the existing behavior.
14529729
POST-16742
If an employee is on a fixed shift, the start time and end time on the timesheet is not updated as expected. The issue occurs with work details that have the UAT time code.
When the WORK_SUMMARY_START_END_SET_TO_SHIFT registry parameter is set to False, only work details with paid hour types (non-zero multiplier) are considered when adjusting the start and end times displayed on the timesheet.
Outcome
Fixed by adding a new option named ALL_DETAILS to the WORK_SUMMARY_START_END_SET_TO_SHIFT registry parameter. When the registry parameter is set to ALL_DETAILS, all work details (paid and unpaid) are considered when adjusting the start and end times displayed on the timesheet.
14535885
POST-16865
When a manager adds a comment to an employee's timesheet that contains illegal characters, a warning message is not displayed that the comment could not be saved.
Outcome
Fixed. If the comment contains illegal characters, an input validation error is displayed.
14540251, 14548707
POST-16751
In the Payroll Close Wizard, a system error occurs when running an off-cycle payroll export for terminated employees.
The issue occurs when employee history includes a pay group that does not have an associated export type.
Outcome
Fixed by validating all pay groups that are included in the off-cycle payment.
14543969
POST-16831
When a user has page-level View access to the timesheet, the employee information card does not load. An application error is displayed.
Outcome
Fixed by using a GET request instead of a POST request to retrieve the employee card data.
14551821
POST-16806
In a custom Engagement form, if you click Edit and select the Union check box and then save, a blank page appears.
Outcome
Fixed by setting the maximum parameters limit to 10,000.
14555398
POST-16870
The Time Code Summary column on the timesheet does not sum up hours for the same time code.
Outcome
Fixed.
14625670
POST-17188
The Employee Work Type override field (EMPWRKTYP_NAME) cannot be configured to show on the employee information card in the Timesheet, Supervisor Approval Worksheet, ASV, One-time Scheduler, or Master Rotation screens.
Outcome
Fixed. The employee information card has been enhanced to show the Work Type and Employment Type fields.
14628146
POST-17218
When viewing the current pay period in the Supervisor Approval Worksheet, the wrong date range is displayed upon clicking the right arrow button to load the next pay period.
Outcome
Fixed.
14634765
POST-17199
Users cannot drag and drop to re-order the condition set when configuring the Weekly Overtime Plus Rule.
Outcome
Fixed by enabling drag and drop functionality for condition sets in the Weekly Overtime Plus Rule.
14659253
POST-17316
When applying the Work Premium override in the timesheet, the selected time code value is not shown. The issue occurs when the PREMIUM_EDITS_APPLY registry is set to PRECALC.
Outcome
Fixed. Work Premium overrides with override type 1300 now reference PREM_TCODE_NAME field for localization.
14678904
POST-17435
When employees in ETM are looking at their transactions and click on the buttons at the bottom of the screen to change the date, the screen appears to refresh but the date stays the same.
Outcome
Fixed.
14683007
POST-17451
An error occurs when running the Payroll Close Wizard and Asynchronous Payroll task.
Outcome
A plugin should always be used with a Payroll Export. The validation message has been improved to say "Plugin is required for the Payroll Export task."
14696834
POST-17518
When the WORK_SUMMARY_START_END_SET_TO_SHIFT registry parameter is set to True, only the first shift is considered when setting the work summary start and end times displayed on the timesheet. For example, if the employee has two schedules (7:00 to 12:00 and 16:00 to 20:00), the work summary end time is set to 12:00 instead of 20:00.
Outcome
Fixed by adding a new option named ALL_SHIFTS to the WORK_SUMMARY_START_END_SET_TO_SHIFT registry parameter. When the registry parameter is set to ALL_SHIFTS, all shifts are considered when setting the work summary start and end times displayed on the timesheet. With this option, the earliest scheduled start time and the latest scheduled end time are used.
14787693
POST-17786
Employees are not receiving the correct shift premium from the Shift Premiums Rule. The rule is not calculating for all zone time periods when the employee is not scheduled or is scheduled to an OFF shift.
Outcome
Fixed.
14796255
POST-17806
When running a custom Work Detail Import task, the connection pool is exhausted.
The core class com.workbrain.app.ta.db.OverrideAccess initiates a new connection, but does not release the connection after it's done.
Outcome
Fixed. Instead of relying on the framework to release a borrowed connection, the connection is released explicitly after usage.