POST 7.0.0.20 resolved issues
Total: 13 issues
----------------
Incident # 14815317, 14918692
POST-17842
After generating schedule there are no shifts posted and process dates have not changed
Shifts from a Shift Template (ST) are not generated if the schedule is generated for the ST when a Staffing Requirements Template (SRT) is also selected that has already been used to generate workload.
Outcome
Fixed by changing the code for overlap validation when generating both workload and unassigned shifts. A soft stop warning is displayed if there are conflicts with the workload (SRT) only.
----------------
Incident # 14819242
POST-17927
Print function in ASV only showing unassigned shifts for one team
When printing the ASV using the print button in the application, only unassigned shifts appear. This is occurring in all environments.
Outcome
Fixed.
----------------
Incident # 14845818
POST-17934
Missing localisations in MVS
In the MVS scheduling screens some localisations are missing from the language pack.
Outcome
Fixed.
----------------
Incident # 14896289
POST-18045
Date Selection dropdown issue in SAW
In SAW, when the user enters a manual date range, the Date Selection field does not automatically resolve to "Manual Date Range".
This issue was caused by the fix in POST-17218. In that issue, the wrong date range was displayed when navigating to the next or previous pay period.
Outcome
Fixed. If the date selection does not depend on the pay group, then the field is set to "Manual Date Range" when any date is selected.
----------------
Incident # 14867598
POST-18081
'RA_FUT_BALANCE_ERROR' Error Message
'RA_FUT_BALANCE_ERROR' error encountered when booking off shift as PTO.
Outcome
Fixed.
----------------
Incident # 1
POST-18159
Number Format exceptions seen on Self Scheduling
SimpleDateFormat is not thread safe due which causes concurrency issues.
Outcome
Fixed. Limited the scope of SimpleDateFormat to method level instead of class level.
----------------
Incident # 14933184
POST-18173
Time format changes from 24hr clock to 12hr clock upon clicking "Tab" button within the TimeSheet
In the Timesheet the shift times are displayed using the 24hr clock i.e. 07:00. However, when the user clicks on one of the start or end times then clicks away from that cell, the time is displayed as a 12 hr format i.e. 7:00a. The time returns to the 24hr clock format when a recalc on the timesheet is performed by the user or when 'Submit' for that day is clicked.
Outcome
Fixed.
----------------
Incident # 14934702
POST-18193
The "previous" and "next" buttons in Time Off Approval are not correctly localized
On the Time Off Approval page, the translations of the Next and Previous buttons are incorrect for German, French European, and Italian.
Outcome
Fixed. Localization options have also been added for the Next and Previous buttons.
----------------
Incident # 13798309
POST-18240
Three issues raised after the deployment of the hotfix (POST-18009) including the fix POST-17647
Three issues raised after the deployment of the hotfix (POST-18009), including the fix POST-17647. Customer is using a custom import task.
Outcome
Fixed. Modified logic to add a new home team if the new termination date is within the existing termination team period.
----------------
Incident # 14655848
POST-18370
Missing Workbrain field Locale Data entries for English Locale
Outcome
Fixed.
----------------
Incident # 14975055
POST-18389
Invalid UI and Incorrect dates in Mobility
Outcome
Fixed.
----------------
Incident # 15015970
POST-18421
Total Hours increases by 1 hour when adding Work Detail with End Time between 00:00-00:59
When Work Detail is manually added on timesheet on 1st November 2020, if the End Time crosses over 1st November to 2nd November where the time is between 00:00-00:59 the hours increase by 1 hour since the application is saving the End Time as 1 hour greater. (However, DST had ended earlier on 1st November @ 2am).
Outcome
Fixed.
----------------
POST-18429
Backport Request - WFM-25962 to 7.0.0.x
When a posted shift billboard transaction was successful, the Workflow Manager (Maintenance > System Administration > Toolkit > Form / Workflow Manager) is reporting a status of "Pending".
Outcome
Fixed.
----------------