POST 7.1.0.1 resolved issues
Total: 15 issues
----------------
Incident # 14380495
POST-16312
ASV - MEAL time changed to -30 when type in shift label with shift time crossed to Spring DST triggered error
In the ASV, when typing in a shift label with a shift time that crosses the spring DST, the duration of the break is changed to -30. If the user tries to save the shift, an error message "Shift details are not contiguous" is displayed.
Outcome
Fixed. DST is now taken into consideration when scheduling a shift in Details Edit mode.
----------------
Incident # 14572186
POST-17004
Bottleneck on SEQ_WRKS_ID
When running the recalc task simultaneously on four servers to test performance, the batch tasks are getting low throughput. The test was performed using SQL Server.
Outcome
Fixed by retrieving work summary IDs one at a time instead of in bulk.
----------------
Incident # 14680851
POST-17428
MR Field Parameters for Auto Row Naming are not respected if that element is hidden for a certain security group
When setting the default value for the Automatic Row Naming option in the MR/OTS creation page, the default value is not retained if the field is hidden to the user that is creating the rotation.
Outcome
Fixed. The default value is retained when a rotation is created with the field in view mode. The default value is also retained when the field is set to HiddenUI.
----------------
Incident # 14681287
POST-17444
Extension point for IDP initiated SSO
You can now configure an extension point for validating and parsing the SAML token in Mobility, WFM and ETM for IdP initiated SSO. This allows you to unify how the SAML response is handled by Mobility, WFM and ETM. The parser is specified in the /system/security/SAML/TOKEN_PARSER registry parameter.
For more information, see the Infor Workforce Management Registry Parameter Reference Guide.
----------------
Incident # 14667338
POST-17449
Incorrect Employee Calendars in Self-Scheduling
In ETM, when accessing the self-scheduling calendar from the link in Messages, the process dates are out-of-date. When accessing the calendar from Work Schedule > Self-scheduler, the adjusted dates are shown.
Outcome
Fixed. When clicking the link in Messages, the dates from the process definition are retrieved so that the self-scheduling calendar contains the most recent data.
----------------
Incident # 14788597
POST-17772
Determine expected behavior when publishing holiday shift from one template and publishing 2nd template
After generating some shifts for a holiday using a shift template (for example, 2 day shifts), and then generating shifts using a different template (for example, 5 day shifts with the same set of skills), a total of 7 day shifts were generated on the holiday. When publishing the second template, the system should have generated only three additional shifts on the holiday since two shifts were already generated from the first template.
Outcome
Fixed by adjusting logic to account for shifts created through schedule templates. Shifts are added to the schedule to fill any gaps between the number of shifts in the shift template and the team's existing schedule.
----------------
Incident # 14828560
POST-17874
Employee missing in message when a billboard shift is claimed
When a team member claims a manager posted shift in the billboard, the Employee field is blank in the messages sent to the posting and claiming employees.
Outcome
Fixed. For unassigned shifts claimed in the billboard, "Unassigned" is shown in the Employee field in ETM/desktop messages to match the messages in mobility.
----------------
Incident # 14797482
POST-17916
System error while running System Health Check that refers to weakPasswordService
When one or more user accounts have a null password in the WORKBRAIN_USER table, a system error occurs while running the System Health Check.
Outcome
Fixed.
----------------
Incident # 14841922
POST-17937
LFSO Roster - The fifth split shift shows all objects in the dropdown
When a fifth split shift is added on a day, all jobs/activities are displayed in the lookups, regardless of the selected department or location.
Outcome
Fixed. Only the jobs and activities available for the team are displayed.
----------------
Incident # 14747357
POST-17972
Original hours in Scheduling getting doubled/increased
Original hours in Scheduling getting doubled if the user copies schedules from one week to previous weeks.
Outcome
Fixed.
----------------
Incident # 14865129
POST-17976
Issues with special character & (ampersand)
When updating the XML of a mapping definition, the ampersand special character ('&') is replaced with '&' upon saving.
Outcome
Fixed.
----------------
Incident # 14888806
POST-18036
ORA-01795: maximum number of expressions in a list is 1000 while executing SELECT * FROM ES_SHIFT_LINK error when publishing MR/OTS or accessing Edit Template
A publishing error occurs when trying to publish an MR due to a query during the publishing process that tries to retrieve over 1000 records from the ES_SHIFT_LINK table.
Outcome
Fixed by updating the query to run in batches.
----------------
Incident # 14896212
POST-18044
Day Part disappear in shift configuration randomly after upgrade to 7.0
After editing a shift with a day part in Shift Configuration, the day part is not seen on the shift when loading the Shift Configuration on a different date and editing the same shift. When the shift is plotted on the MR/OTS, the coverage is only counted on the days where the day part can be seen in Shift Configuration.
Outcome
Fixed by updating the cache with the newly loaded shift attributes.
----------------
Incident # 14911034
POST-18082
Time incorrectly added to, or subtracted from, premiums inserted by Daily Overtime Plus Rule
Employees are being paid incorrect minutes on premiums inserted by the Daily Overtime Plus Rule. Employees are being given premium work detail hours that are incorrect by one minute (plus or minus, but usually plus) compared to what they should be. If the employee's existing work details carry an overtime work detail for 1 hour 30 minutes, along with another work detail that is also overtime, but for a different time code, and set to 30 minutes, then the premiums would be inserted to credit 1 hour 31 minutes, and 31 minutes, respectively. The expectation is that the premiums would carry the same exact hours/minutes as the work details to which they relate.
Outcome
Fixed. Defer the rounding of the timesheet minutes until all values have been merged with their respective double value; this increases the precision of timesheet calculation when merging premium details.
----------------
Incident # 14931954
POST-18153
Jar Signing Issues on Jenkins Builds
Outcome
Fixed.
----------------