WFM general 7.1.0.21 resolved issues

Total: 6 issues

----------------

PLAT-11225

Publ API - SoFiscalYear

Public APIs have been added to retrieve the fiscal year.

----------------

PLAT-11342

Publ API - Whitelist

Added additional items to the API due to POST-20392.

----------------

WFM-32421

Badge swiped on a clock over an existing user swipe activity displays consecutive type validation message

When a badge is swiped or entered on a clock over an existing user swipe activity, the clock displays the consecutive type validation message. Two swipes (accepted and rejected) are saved to the clock with the same timestamp. Both swipe entries are for the badge that was swiped (or entered) first and not the badge that was scanned over an existing swipe activity.

Outcome

Fixed. The badge consumer is disabled while displaying the validation message.

----------------

WFM-32472

Embedded Clock Enhancement: Show message to indicate clock is waiting for response from WFM

After enabling swipe sharing across clocks, all the readers in the group that share swipes appear to freeze whenever any swipe occurs.

To fix this issue, a "Validating swipe" message is now displayed for all embedded clocks if swipe sharing is enabled for the reader and the validation requires the last swipe. The timeout of the message is the timeout of the swipe request + 500 milliseconds.

----------------

WFM-32979

Batch schedule generation completed with errors message is seen when batch scheduling is run for auto assignment

If the Mosel server generates unassigned shifts, the Batch Scheduling task fails with the error "Exception occurred with batch scheduling null". In another scenario, the task fails with the error "Transaction rolled back because it has been marked as rollback-only".

Outcome

Fixed by modifying the code to avoid the errors.

----------------

WFM-32980

"Exception occurred with batch scheduling null" is seen when batch scheduling AA task is run

When no groups are specified inside the schedule profile, the Batch Scheduling task completes with the message "Exception occurred with batch scheduling null".

While creating the schedule, if the Budget Rule is used, the task completes with the message "Exception occurred with batch scheduling null".

When the task fails while creating one of the schedules, the message "Exception occurred with batch scheduling null" is sometimes logged instead of a full message.

Outcome

Fixed all three scenarios. In the first scenario, the task now fails with the full message and the error "No group defined for profile - scheduleProfName" is logged.

----------------