WFM maintenance 7.0.0.45 resolved issues
POST-21338
Incident # 15581119, 15487889
Daily Publish task not creating shifts on days where shifts are missing
When the schedule is published using the Daily Publish task, all the shifts on a certain day are missing in the ASV.Outcome
Fixed. If an error occurs during the Daily Publish task, the publish date of the task is not updated. Any unpublished shifts will be published on the next day. If the issue persists on the next day, a daily notification is sent regarding the issue until the issue is resolved.
POST-21614
Incident # 15903134
Seeing shift id errors in job scheduler log post upgrade and post HF
When publishing schedules in ASV, shift ID errors are shown in the Job Scheduler log though the schedule does publish.
Outcome
Fixed. This issue is a regression of POST-18935.
POST-21684
Incident # 15886794
Warnings in System Health Check
After setting the INPUT_VALIDATION registry to True, a warning is still displayed in the System Health Check.
Outcome
Fixed by ignoring the case of the registry value.
POST-21819
Incident # 15966096
Problem with DB upgrade, Flyway took 5.5 hours to complete
Flyway upgrade from 6.2.4 to 2021.10.01 took 5.5 hours to complete.
Outcome
Fixed by modifying the update query in migration to improve performance.
POST-21905
Incident # 15863275
ASV - entering or reverting a book-off takes a long time to process
When entering or cancelling a book off in the ASV, it takes a long time for the request to be processed. There are only 13 employees on the schedule and the time period selected is one week.
Outcome
Fixed by implementing caching to reduce the number of database hits when getting the pay group-related data. The query fetchSize setting can be adjusted using the RECORD_DATA_LIMIT registry parameter.
POST-22242
Incident # 16099881
Shift Configuration: time out issue when creating new shift
When creating a shift in Shift Configuration, a timeout error occurs upon clicking Save.
Outcome
Fixed by adding an index and increasing batch size to improve performance.
POST-22422
Incident # 1
Backport WFMCM-5911 - Job Scheduler Task Monitoring
Job Scheduler statistics now log messages every 300 seconds by default. You can configure how often the statistics are logged in the system/EnterpriseScheduler/Monitoring/LOG_INTERVAL. This registry can be configured to a minimum of 60 seconds and a maximum of 300 seconds (default).
The messages use this format:
JobScheduler stats: affinity=<affinity>, max_pool_size=<##>, idle=<##>, active=<##>, tasks=<##>, threads=<##>, unnamed_threads=<##>, task_details=[Task1], [Task2], . . . [TaskN]
Since each task or task child thread typically consumes one connection, the number of threads and tasks provides guidance of how connections are being used.
Additionally, the top tasks based on CPU time are logged using this format:
JobScheduler top thread: name=<ThreadName>, ID=<Thread#>, CPU time(sec)=<##>>
You can configure how many top thread rows are shown in the system/EnterpriseScheduler/Monitoring/NUM_THREAD_DETAILS registry parameter. This registry can be configured to a minimum of 1 and a maximum of 10.
POST-22479
Incident # 16203345
Null Pointer Error when loading Staffing Center
When loading the Staffing Center for selected dates, a NullPointerException occurs. The issue occurs while loading non-MVS shift information for an employee that does not have a job configured.
Outcome
Fixed by adding null condition.
POST-22568
Backport POST-18299 to 7.0.0.x
After running a custom mass off cycle payroll task, customer is getting the following error: "ORA-01795: maximum number of expressions in a list is 1000".
Outcome
Fixed. Modified the code to execute query in batches.
POST-22569
Backport POST-18501 to 7.0.0.x
payrollService.getEmployeeReadiness throws an error when receiving over 1000 employees
Outcome
Fixed by modifying the code to execute query in batches.