POST 7.0.0.3 resolved issues
Total: 16 issues
----------------
Incident # 13496414
POST-13860
MVS Callout causes UDF1 to populated with a N
When using the Shift Edit callout, the shift detail objects are populated from the details of the shift being edited. If the Flag 1 column is configured as a CheckboxUI and the UDF 1 column is configured as a StringUI, the check box value is incorrectly copied to the UDF 1 column and displayed as Y or N, depending on whether the check box is selected.
Outcome
Fixed the ShiftDetailData constructors.
----------------
Incident # 13530911
POST-13909
Select a yellow shift at the bottom and click the Mark Unfilled button, screen did not persist at the bottom
In a Relief Queue with lots of unfilled shifts that require scrolling, when selecting a yellow shift at the bottom of the screen and clicking the Mark Unfilled button, the screen jumps back to the top upon refreshing. The scroll position should be persisted to display the selected shift.
Outcome
Fixed by passing value of current scroll position on form submit and restoring it on receiving the response.
----------------
Incident # 14122634
POST-15457
Invalid Property error when saving employee shift preferences pattern
When trying to save an employee shift preference pattern, an error occurs and the form cannot be saved. The error occurs when the team has 6 day parts in its day part set and there are 6 shift types assigned to the team.
Outcome
Fixed by ensuring the shift types list is unique for both shift preferences and shift preferences overrides.
----------------
Incident # 14138055
POST-15476
Partial LTA Overrides in Mobility My Schedule are displayed with the wrong start time.
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.
----------------
Incident # 14149522
POST-15533
Cannot remove comma between Employee Last Name and Employee First Name in different modules
When the FULLNAME_FORMAT registry parameter is set to [EMP_FIRSTNAME] [EMP_LASTNAME], a comma is still displayed between the first name and last name of a new employee in the LFSO schedule and Supervisor Approval Worksheet.
Outcome
Fixed by getting data from the EMP_FULLNAME column instead of the EMP_FIRSTNAME, EMP_LASTNAME columns.
----------------
Incident # 14158762
POST-15558
Missing Language Translations in 6.2.4.31
There are missing translations on 6.2.4.31 that apply to all languages.
Outcome
Fixed by adding code and translations.
----------------
Incident # 14288015
POST-15843
Archiving import transactions fails with error: ORA-12899: value too large for column "ARCHIVE"."WBINT_IMPORT"."WBIMP_MSG"
When archiving import transactions, the archive task fails if the archive records have import failures with error messages that exceed 255 characters.
Outcome
Fixed by increasing the length of the WBINT_IMPORT.WBIMP_MSG column from 255 to 1000.
----------------
Incident # 14291237
POST-15850
Apply Base Rate after Post Calculation Work Detail
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.
----------------
Incident # 14301002
POST-15864
Core Payroll Export Issue
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.
----------------
Incident # 14312381
POST-15929
Performance issue where Relief Queue screen is frozen after the Preset button was used
The Relief Queue screen becomes frozen upon loading a preset, forcing the refresh of the browser.
Outcome
Fixed. A loading indicator is displayed while the Relief Queue is loading, preventing user action.
----------------
Incident #
POST-16033
QA Issues for "MVS Type 1: localization ability (the diamond) isn't present."
Localization is not available in various areas of MVS.
Outcome
Fixed by adding code to pick the translations for the Employment Type and Work Type filters in the ASV. Also added localization code and English defaults for the Relief Queue hover.
----------------
Incident # 14325782
POST-16135
Accrual Plans show balances earlier than the start date and end date
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.
----------------
Incident # 14297394
POST-16147
"Employee History was not found or was not loaded" when importing new employee hire date
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.
----------------
Incident # 14365240
POST-16204
NPE Being Thrown Intermittently When Calling wbData.getClocks
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.
----------------
Incident # 14370818
POST-16225
Attempting to reprocess all of the masters after the script fix and getting error
After running the script provided for POST-15634, an incorrect error occurs when trying to reprocess all of the Master Rotations:
Shift not effective for whole period
Outcome
Fixed issue with the shift attributes cache not updating properly as previous cached values were being overwritten. Also added fix for the shift team cache.
----------------
Incident # 14371401
POST-16273
Timesheet messed up after new version of MR published
After a new version of a Master Rotation is published, the timesheet still reflects the employee's shifts from the previous version. The total hours in the ASV are incorrect too.
Outcome
Fixed by adding migration to cancel overrides that are associated with deleted shifts.
----------------