POST 7.0.0.4 resolved issues
Total: 11 issues
----------------
POST-15485
Norwegian Missing translations issues
Missing Norwegian translations in the application.
Outcome
Fixed the configurations and missing translations.
----------------
Incident # 14268918
POST-15764
Process Violations screen has no violation information
Process Violations pop-up is displayed as blank. This occurs when an employee is assigned to multiple rows in an MR and one of those rows is deleted.
Outcome
Fixed.
----------------
Incident # 14266547
POST-15809
Odd interaction between grace rule/LateLELL rules and Labor Metric Punches
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.
----------------
Incident # 14321968
POST-16134
TOR - inner query referring to non-existent table in database
Time Of Request (TOR) does not work and causes this error message:
"Validation Error: LeaveValidationAction: SQLException occurred during action process."
Outcome
Fixed by updating the code which references the removed table ES_RELIEF_TIME_CODE.
----------------
Incident # 14351743,14445029
POST-16157
Cancel book off screen displays an out of order sequence within the Work Dates
When canceling a book off in ASV after booking off multiple shifts in Mass Edit, the work dates are not sorted for the group of booked off shifts.
Outcome
Fixed by adding sorting for workDate.
----------------
Incident # 14347805
POST-16193
Creating day parts within a day part set not possible
Users cannot add multiple blank rows to the Day Parts form when creating a Day Part Set. This makes it difficult to add a Day Part Set, since the set must cover a full 24-hour period before it can be saved.
Outcome
Fixed.
----------------
Incident # 14377177
POST-16235
Weekly Overtime Plus rule creates OT premium with zero rate
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.
----------------
Incident # 14397195
POST-16262
Labor Metric Security does not allow calculation group and security group selection in the same row
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.
----------------
Incident # 14383977
POST-16349
Generating the schedules for shift patterns results the system to not properly handle shifts
Upon generating schedules with a couple of DC locations, the employee's scheduled start time is past the employee's day start time where employees are missing schedule in the Display a Schedule Page. Users are then forced to assign shifts to each and every employee that has missing shift.
Outcome
Fixed.
----------------
Incident # 1440612
POST-16395
Self Scheduler redirecting to the wrong page
When opening the Self Scheduler page in ETM, the /emvs/action/shiftPreferencesOverride.action page is opened instead of etm/modules/selfscheduler/selfScheduler.jsp.
Outcome
Fixed by disabling page submit on problematic pages.
----------------
Incident # 14425069
POST-16405
Flags in MR default to N even if UI is set to StringUI without any default value
Flags in MR always default to a value of N (false) when Flag fields are configured as StringUI. The default values are also sent to the Timesheet when MR shifts are published.
Outcome
Fixed by setting default values to null instead of N.
----------------