POST 7.1.0.9 resolved issues
Total: 12 issues
----------------
Incident # 14593753
POST-17712
Labour Metrics and Job not copied from latest Bulk Version while copying the MROTS templates
The latest labour metrics and job changes are still not copied to the MR template after testing the fix for POST-17206 on 7.0.0.12. This has been observed where there are multiple changes on bulk row versions.
Outcome
Fixed. Fixed by sorting row version before using it for copy. This ensures the version used for copy is always the latest one regardless of database.
----------------
Incident # 14947814
POST-18415
Localization Request for Mingle Environment Error Message "Error creating user session when processing SAML Response"
When an inactive user attempts to log in, they see an error message which causes confusion for them since the error is not clearly stated. As a result, the customer/consultants are requesting to change the message via localization where the correct language translations are also added.
Outcome
Fixed. Enabled Localization for every hard coded Exception identified. Utility function is written to localized the passed-in error ML string at required place and the function is used to Localize all the newly formed Exception Localization messages. Default English Localization is provided with the fix.
----------------
Incident # 15014867
POST-18491
Daylight Savings Time Firing for shifts ending prior to actual daylight savings time
Outcome
Fixed. Updated getOverride() in SubmitTimesheetAction to use addMinutesDSTAware when calculating the end time. This adjusts end time properly and the correct hours will be displayed when user submits on a day with DST.
Note: This fix is specific to scenarios where the system and server time zones are identical.
----------------
Incident # 15027348
POST-18518
No shifts are seen in schedule with Non Volume-driven best fit requirements configured for overnight shifts
When generating the schedule with NonVolume driven best fit requirements and the system failed to generate workload intervals for the cross midnight shifts, and as a result there are no shifts. The current core code is not considering and checking to increase the day value to generate the NonVolume driven workload intervals for cross midnight shifts.
Outcome
Fixed. Added code to check and increase day value for cross midnight shifts before creating workload intervals. The algorithm remains same for normal day shifts.
----------------
Incident # 15059802
POST-18574
New Time Off Request Form - Partial Day required
The 'Partial Day' field is not acting as required even if it is set to be.
Outcome
Fixed. Modified code to get field configuration data (mandatory field configuration) and added validation based on field configuration data.
----------------
Incident # 15064260, 15117375, 15221565
POST-18662
Employee Home Teams are not updated
After running an Employee Import, the home team is not always updated for rehired employees. For example, if an employee was not moved to TERMINATED TEAM in their last contract and the new contract is imported with a different home team, the previous home team information is retained. If an employee was moved to TERMINATED TEAM in their last contract and the new contract is imported with a different home team, the new home team assignment starts immediately after the previous contract. As a result, the assignment to TERMINATED TEAM between the contracts is lost.
Outcome
Fixed home team assignments during Employee Import and HR Refresh when the employee status is active and the Emp_Termination_Date field is less than the default termination date of 01/01/3000:
- If the employee is active and the configured termination date (termination_date) is less than 01/01/3000, then the employee's termination date is set to termination_date and the employee's team assignment is updated to TERMINATED TEAM with a date range of termination_date to 01/01/3000.
- If the employee is active and the termination date is empty or 01/01/3000, then there is no change to the employee record.
See "Termination date" in the Infor Workforce Management Time and Attendance Implementation and Administration Guide.
----------------
Incident # 13659032
POST-18733
Shift Invalid state error pops up when user floats an employee from his shift to multiple activity shift
Outcome
Fixed. Allow to send floatTo request without specifying activity override when floating to new shift. Layers and activities will be taken from shift configuration instead (the same as it is working in STC). It is still possible to select activity override but in case of shifts with many overlapping activities (eg MAD) will cause shift invalid state error.
----------------
Incident # 15127343
POST-18776
HTML Tags are seen in Timesheet work detail
HTML tags are displayed in work details on the timesheet. The issue occurs when bold tags are added in the localization.
Outcome
Fixed.
----------------
Incident # 1
POST-18919
SQL error is thrown when employee clicks on link in messages for Shift Bidding
When the employee is clicking on the link sent in the e-mail to participate in the shift/pattern bidding, a SQL error 'ORA-00933: SQL command not properly ended' getting thrown.
Outcome
Fixed. Removed the 'AS' keyword from the queries where it was used for table alias.
----------------
Incident # 14954434
POST-18965
SAW not loaded if precision=0 set on SAW_PAY and SAW_ACTUAL_PAY
When attempting to eliminate the decimals displayed for the cost values on SAW, the SAW_PAY and SAW_ACTUAL_PAY fields were configured with precision=0. However, when the SAW was re-loaded nothing would be displayed on the page.
Outcome
Fixed.
----------------
Incident # 15193363
POST-18982
An application error has occurred upon processing a bulk version of MR
Outcome
Fixed. Changed the code to use the batching.
----------------
Incident # 15236457
POST-19135
Multiple clicks when submitting a shift to the billboard from LFSO schedule can cause multiple records to be inserted leading to "IllegalStateException: Duplicate key" error
If we click on the Save button within the same time, the system is sending multiple requests with the same shifts before completed the 1st request which is creating duplicate records and showing the errors.
Outcome
Fixed. Added code changes on the script to do not allow the user to submit the same shift multiple times and it allows the user to submit it again if completed the previous submitted request.
----------------