Labor Forecasting and Schedule Optimization (LFSO)

14383977

POST-16349

Upon generating schedules with a couple of DC locations, the employee's scheduled start time is past the employee's day start time where employees are missing schedule in the Display a Schedule Page. Users are then forced to assign shifts to each and every employee that has missing shift.

Outcome

Fixed.

14279837

POST-15903

There is no employee loan request email when being the manager of both borrowing store and loaning store.

Outcome

Fixed. The restriction to not send email from the same user to him/herself has been removed.

14229990, 14214438

POST-15781

Original Cost and Current Cost fields in the LFSO Schedule screen display the cost with two decimal places even when the precision parameter is configured as 1 for these fields.

Outcome

Fixed by updating the code to consider the CurrencyUI field precision parameter for Original Cost and Current Cost fields.

14149522

POST-15533

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.

14531888

POST-16781

Unable to drag and drop shifts for the employees listed at the bottom of the page in the Daily View in LFSO as there is no possibility to scroll to the bottom of the page if the user picks up a shift. User can only assign the shifts to the employees visible on the page. Unable to use mouse scroll button.

Outcome

Fixed. Added the functionality that while dragging the shift, if the user reaches the end of the Daily View shift area, it will start to scroll automatically.

14516971

POST-16716

The Daily tab in the LFSO Schedule screen is not displaying the day of the week along with the dates displayed in the header.

Outcome

Fixed by passing the localized WeekDay string along with the date in the function that is responsible for creating the date headers in the Daily tab.

14498134

POST-16568

When trying to regenerate the schedule a second time or deleting the schedule after its regeneration, a "Unique constraint violated" error occurs.

Outcome

Fixed. Whenever regenerating any schedule, all the existing data related to that schedule is first deleted from the database. The newly returned data from the Dash server is then inserted using a new schedule ID instead of the same schedule ID.

14451391

POST-16557

When trying to create schedules for specific locations using a schedule profile or new definition, a "/ by zero" error occurs.

Outcome

Fixed.

14412486, 14409528

POST-16514

There is a time discrepancy between the shifts seen on the schedule (the correct time) and in the report (1 hr offset).

Outcome

Fixed. Used non-DST day to print time on time ticker.

14430258

POST-16384

When an employee posts a shift in mobility to the Shift Billboard, the user gets a message that the posting has been routed for approval, but the required approver user does not receive the message to approve the posting. This can occur when using Shift Billboard with LFSO due to the configuration of departments and parent locations.

Outcome

Fixed by updating the code to use the exact parent locations for the posted shift's team. The code also has been updated to pass the proper department location for schedule compliance validation.

14583069

POST-17006

Daily Tab doesn't display the schedule unless you are sorted by Location. It will not display if you are sorted by Employee.

Outcome

Fixed.

14523397

POST-16809

When configuring an EMP_VAL field to show on the employee information card in the timesheet and LFSO schedule, the value of the field is not displayed. The issue occurs when the EMP_VAL has been configured as a DataPickerUI and a date format has been specified.

Outcome

Fixed.

14449216

POST-16674

When the CAN_SUPERVISOR_APPROVE_OWN_AVAILABILITY registry parameter is set to TRUE, the start/end times saved on the Availability Pattern form are shifted down one day. For example, the times entered on Monday are moved to Tuesday.

The issue occurs when the DAY_WEEK_STARTS registry parameter is set to a day other than Monday.

Outcome

Fixed.

14133732

POST-16455

When running the SO SCHEDULE DATA Archiving Task, the archiving fails. The log indicates that the FK_OSBPOSTING_SKDSHFT_ID constraint was violated.

Outcome

Fixed by adding the archive tables creation schema scripts and the archive policy definitions for the required Shift Billboard tables.

729562

POST-17143

When using the Schedule Detail Import, breaks are not applied correctly on the timesheet. The issue occurs when "Is BRK" is not selected for the first break, but is selected for the second break, for example:

  • Full shift 11:30 to 20:00 (UAT)
  • Lunch 15:30 to 16:00 (SCHED-LUNCH), "Is BRK" is not selected
  • Break 16:00 to 16:15 (BRK), "Is BRK" is selected

In this scenario, BRK is not shown on the timesheet, though it was shown as applied in Import Transactions.

Outcome

Fixed by modifying the logic so that any number of overlapping intervals are tolerated while processing the shifts.

14642413

POST-17248

The Schedule Detail import takes too long to complete with over 500,000 records.

Outcome

These changes were made to improve performance on Oracle, SQLServer, and DB2 databases:

  • Reduce the number of required times required to load data for Grouped Transaction Types.
  • Optimized the SQLs for loading import data from WBINT_IMPORT table.

14631188

POST-17180

If the Employee's name contains an 'apostrophe', then while loading the Employee Availability Calendar for a team assigned to that employee in the Employee name list, the employee's name will contain the encoded HTML value of the 'apostrophe'.

Outcome

Fixed.

14604778

POST-17089

In the Employee Loan Cancellation maintenance form, the date format is appearing as MM/dd/yyyy when the SYSTEM_DATE_FORMAT registry parameter is set to yyyy/MM/dd.

Outcome

Fixed by modifying the code to get the date format specified in wbll_system_date_format based on user locale.

POST-17541

When a schedule is created from a profile for a Japanese user, the compliance messages are displayed in English.

Outcome

Fixed.

POST-17480

In a Schedule Detail import, shifts can be overwritten by later import records containing overlapping shifts.

Outcome

Fixed.

14618317

POST-17224

After removing sub locations of a store by changing their parent location, system errors occur when trying to reload the schedule. The issue occurs in a SQL environment.

Outcome

Fixed.

14658047

POST-17389

Japanese localization required for rejected shift swap message.

Outcome

Fixed.

14595092

POST-17674

An exception 'java.lang.NumberFormatException: For input string: "0,00"' occurs when creating an LFSO schedule.

Outcome

Fixed.

14741607

POST-17638

Shifts are not sorted in alphabetical order by employee names in the printed schedule when the LFSO Schedule screen is sorted by Employee in the Weekly view or the Daily view.

Outcome

Fixed by adding functionality to sort the employee groups in alphabetical order when printing the schedule. The employees are sorted for each group, for example Position or Location, in the generated PDF file.

14713948

POST-17573

When the registry parameter CREATE_SCHEDULE_USE_THREAD is set to JOB, an empty schedule is displayed when clicking the URL in the Workmail message received after generating an LFSO schedule. The Workmail is also not localized for Japanese.

Outcome

Fixed the schedule view URL link in the Workmail. Added Japanese localization for the Workmail message body and subject.

14608676

POST-17184

When trying to select an activity after adding a third split shift to an LFSO schedule, a timeout error occurs.

Outcome

Fixed by optimizing the query for the Activity lookup to reduce the execution time.

14772545

POST-17737

When running the Schedule Detail Import/Interface task, a few records are marked as ERROR without any error message.

Outcome

Fixed. When an exception occurs that does not contain any message such as a NullPointerException, a custom message "Exception while processing the shifts" along with the class name of that particular exception is assigned to the import record.

14772685

POST-17732

When the Schedule Detail Import uses files that have exactly 10000 records, the final sequential 18 records are not processed and end up in a PENDING status after the import task has completed.

Outcome

Fixed by correcting the logic used to identify the last batch of records to be processed.

14747636

POST-17705

When deleting the second portion of a split shift and then extending the end time of the first portion of the shift to the end time of the second portion that was deleted, an overlapping error occurs. The issue occurs when the Reassign Break/Meal Automatically after Shift Edit option is enabled.

Outcome

Fixed.

14603124

POST-17069

When the system is displaying the schedule with HOOP + Availability in daily view, the availability interval lines are created incorrectly which is causing the display issue.

Outcome

Fixed. Changed the code to code to generate the availability intervals appropriately in between the HOOP time intervals with the correct color.

14824923

POST-17892

A "!General Error" message is received by employees that request to swap or trade MVS shifts with skills that are on different days.

Outcome

Fixed.

14825970

POST-17873

An index out of bound error is returned when a user attempts to regenerate an LFSO schedule that is not associated with a staff group. While it is true that schedules that are not associated to a staff group, such as schedules created using the Simple Scheduler, cannot be regenerated, the resulting error message does not clearly indicate the issue to the user.

Outcome

Fixed by updating the error message to indicate that the current schedule cannot be regenerated since it is not associated with a staff group.

14783184

POST-17768

When going into Messages and viewing a submitted employee loan request, the \"Borrowing Store\" field is blank. Only the loaning store is populated (which is the store of the manager viewing the request).

Outcome

Fixed by adding a resolve DataSource query to display the borrowing store DBlookup.