Published: 26 August 2020
|
CONTENTS |
|---|
|
/*<![CDATA[*/ div.rbtoc1764668039149 {padding: 0px;} div.rbtoc1764668039149 ul {list-style: none;margin-left: 0px;} div.rbtoc1764668039149 li {margin-left: 0px;padding-left: 0px;} /*]]>*/ New features Changes and improvements Fixed issues Known issues |
New features
Merging multiple ACD queues into one WFM queue – To create more reliable forecasts, it is now possible to merge multiple ACD queues into one WFM queue. As a result of this merging, values for the new queue are calculated based on values for all merged ACD queues. Read more about this functionality: Managing Queues.
Changes and improvements
No changes at this time.
Fixed issues
|
Reference number |
Description |
|---|---|
|
WFM-1662 |
It was not possible to save a schedule if Daylight Saving Time occurred during the schedule period. |
|
WFM-1668 |
Google calendar was not syncing changes. |
|
WFM-1406 |
When a schedule was created from a template and this template was created in a different time zone, the new schedule was shifted by one day and 24h elements were missing. |
|
WFM-1675 |
A datepicker component (the calendar used to select a date) on the Create New Schedule screen was partially hidden under the header when the application was opened in a smaller window. |
|
WFM-1527 |
The scheduled elements were shifted by one hour during Daylight Saving Time on the My Schedule screen. |
|
WFM-1698 |
In same specific cases, the range of the currently edited forecast adjustment was highlighted as being in collision with its own range. |
Known issues
|
Reference number |
Description |
|---|---|
|
WFM-1663 |
Upload of historical data fails if the process takes more than 60 seconds. |