Release Notes: Fixed & Known Issues

The date provided for each update is the date it was ready for release. Watch for a notification about when your organization will receive it. It will generally be within two weeks of the given date.

Fixed Issues

24.3 Release

23 July 2024*

ACD

  • The point of contact audit history was missing some data. (AAD-25041)

  • In environments experiencing a sudden large increase in inbound emails, contact routing would sometimes slow down. (ORC-33453)

Admin

  • When changing a user's assigned role, the user continued to have the old role if the change was made through the Roles & Permissions page instead of from the Employees page. (SC-52708)

  • The list of agents in a team didn't match the list returned when the list was pulled using an API call. This was related to a brief server outage. (UH-39938)

CXone Agent applications

  • When an agent accepted a second interaction that resulted in a second screen popClosed A configurable pop-up window with information about the contact. It appears on an agent's screen after a certain event, usually when the agent connects to a contact. opening in a pop-up window, the new pop-up window was blank. (AW-26560)

  • Quick replies sometimes weren't available for outbound emails. (AW-27369)

  • Agents couldn't copy and paste URLs under the Add Link button in emails. (AW-27226)

  • When a conference call between two agents and a contact ended, the two agents were stuck in the conference. (AW-27091)

  • Custom details were deleted from a case if the agent tried to edit custom fields, the case was unassigned from the agent, or the custom fields were hidden. (AW-27574)

  • To type in a chat window, most of the agent typing area wasn't clickable. Agents had to click in the far left side of the text area to type in it. (AW-27016)

API

  • Very rarely, pulling an agent by ID would incorrectly report the agent ID as invalid. (API-13790)

  • All versions of PUT /teams/{teamId|teamuuid} were failing to update team details when using a teamuuid. (API-13554)

CXone Dashboard

  • In the Agent List Widget, the agent state details were sorted numerically instead of the actual time order. (CXCV-20699)

  • Resizing column headers led to reduced title visibility due to indentation and the sorting icon occupying space. (CXCV-14280)

  • The Agent List widget could not be re-sized to view more users. (CXCV-25999)

Digital Experience

  • Attempting to activate a new Twitter channel failed. (DE-109325)

  • When game mode was enabled for a chat channel, the Start button for the game was no longer available. (DE-107712)

Enlighten AutoSummary

  • Summarizations sometimes included incorrect order or account numbers. (ILLUM-10370, ILLUM-9840)

IEX WFM

  • RTA statuses were out of sync, causing agents to be shown as available when they were not logged in or scheduled. (INT-47560)

Partner Tools

  • Monitoring Gateway wasn't available for users in the EU region. (PSHM-19787)

Personal Connection

  • When a user uploaded a calling list with Use First Row as Column Names selected and and file didn't have a column header with the string 'ID', the process failed. (OB-19309)

CXone Recording

  • There were occasional instances when call recording was not available. The recording alert was "No connection to media server". (CXREC-62950)

Reporting

  • The Contact Detail report sometimes didn't include completed Personal Connection call attempts. (OB-19576)

  • The RTIG BI report sometimes timed out for even small amounts of data. (CXBI-5509)

  • BI report subscriptions sent two emails instead of one. (CXBI-5304)

Salesforce Agent

  • When agents drafted an email, then switched to view a chat, their email draft was deleted. (SF-13563)

  • When agents started a second call, or a new call for a conference or transfer, Salesforce refreshed. (SF-13596)

Studio

  • Inbound phone scripts that included the DNCLOOKUP action sometimes produced an error and dropped the call. (VOL-4062)

  • The FORWARD_EMAIL_DIGITAL action didn't include required data, which resulted in email not threading and creating a new case. (DE-102084)

  • The group filter is not working on the SU page. (CXWFM-50675)

2024-1 Cumulative Update 8

Published 9 July 2024*

ACD

  • In certain systems, calls were briefly unable to route to an agent. (VOL-4159)

  • Contacts configured with routing attributes sometimes routed to agents without the required attribute. (AOR-5419)

API

  • The GET and PUT /services/{version}/workflow-data API calls required the keywords ProfileID, ProfileName, and Description. They would not accept them in their expected camel case forms of profileId, profileName, and description. The keywords are now case insensitive. (API-13751)

  • For a short time, the InContactAPI restarted every 10 minutes, leading to CXone performance issues. (VOL-4346)

  • When the GET /scripts API call pulled a CXone Studio script that had been reverted to a previous version, it returned an inactive version of the script instead of the current one. (CXWS-16917)

MAX

Presence Sync

Reporting

  • The Contact Detail report sometimes didn't include completed Personal Connection call attempts. (OB-19576)

Routing

  • When an agent transferred an inbound call to a new agent, sometimes screen recording would continue to record. (ORC-33101)

  • Some calls were not recorded. These calls had an error that said "no connection to media server." (MS-15500)

CXone Studio

  • When a script contained the Workflow Execute action, attempting to open it in CXone Studio displayed in a blank Workspace page. (CXWS-18281)

Studio

  • In some environments, hold music configured by the MUSICStudio action stopped playing when the contact began routing to an agent. (VOL-3966)

CXone WFM

  • The group filter sometimes didn't work on the Scheduling Unit page. (CXWFM-50675)

Pipeline Update 159

Published 9 July 2024*

ACD

  • When contacts occurred at the same time as an AWS credential refresh period, the contact became stuck in an InQueue state. (ESC-68047)

Admin

  • The employee list file was out of date when downloaded from the Employees page. It was up to date when downloaded from Bulk Upload Portal. Both sources now contain up-to-date files. (UH-39698)

API

  • Some API calls to C700 were incorrectly using http instead of https. (PAPI-6758)

Digital Experience

  • When a contact clicked a rich media link from a message in a closed asynchronous chat, the action failed. (DE-89894)

  • When an agent added an attachment to a chat message, Digital Experience would sometimes include the attachment in the next message as well. (DE-109197)

  • Quick response for outbound emails showed a blank table instead of a populated one. (DE-108061)

CXone Recording

  • There was an issue filtering certain teams in Interactions. (CXREC-64518)

CXone Studio

  • When a script was in read-only mode, actions could be moved after a web editor was opened and closed. (CXWS-15649)

Out-of-Band Releases

Agent for SCV

23.6

Published 1 December 2023*

  • After logging in, the agent's status was set to offline instead of displaying the mapped unavailable code. (SF-12794)

  • When agents ended a call on mute, they received an error message. (SF-12758)

  • Calls occasionally failed after agents made multiple blind transfers or added callers. (SF-12808)

  • Calls weren't displayed in the UI after agents refreshed the page. (SF-12806)

  • After receiving an error, agents couldn't end a call until they refreshed the page. (SF-12828)

  • Agent status didn't change to Held Party Abandoned when the contact ended the call after being put on hold. (SF-12821)

  • When media access was denied, the agent received an error message. The message didn't include any troubleshooting information. (SF-12820)

  • The address book button was not displayed on the dial pad screen. (SF-12867)

  • When agents logged out of and then logged back in, their previous status changed to offline. (SF-12866)

  • Agents were unable to call other agents from the address book. When they placed the call, it would fail and an error message would display. (SF-12853)

  • Agent status didn't change to available at the end of a call. (SF-12822)

  • Agents were unable to make calls by selecting skills in the address book. (SF-12896)

  • Agents could see deactivated skills in the address book. (SF-12881)

  • Agents could see skills that weren't assigned to them in the address book. (SF-12950)

  • Non-available codes could not be seen in the publisher state. (SF-12914)

Performance Management (Legacy)

May 2024 Fixes

Published 28 May 2024*

  • When a user added a custom image to a Spotlight slide, the image didn't appear while the slide was being edited. (CS-20050, CS-20380)

  • After a user clicked Publish, the Publish bar was still available. (CS-20098)

  • The Queue Counter widget showed a "No data" message when it should have shown a value of 0. (CS-19873, CS-20036, CS-20088, CS-20268)

  • If a user made column adjustments on the shared dashboards, saved the changes, went to another WebView, and then returned, the column adjustment changes were reverted. (CS-18229, CS-19909, CS-20041, CS-19949, CS-20521, CS-18558, CS-19550)

  • The Gauge widget didn't show the correct data. (CS-20304)

  • The scroll bar in the wallboard date selection disappeared, making it difficult to select custom dates. (CS-20205)

  • When a user added the KPI Trend metric to the KPI Trend widget and applied the Today date filter, a "Something went wrong" or "No date" error message appeared. (CS-20182)

  • If a profile template had multiple supervisors selected and then a user updated it to select all company, team, or agent, the selection was reverted to the original supervisors. (CS-20033)

  • In the metrics selector, users couldn't reorder metrics by dragging and dropping them. (CS-19991, CS-20520)

  • When a user tried to upload the Exclude CDI Contacts file to the Custom Data Import page, the action never completed. (CS-19977, CS-19921)

  • When a user removed all assigned groups from metrics, the assignments reverted to their previous selection. (CS-19862)

  • The YTD date range filters began at 1 January 2023 instead of 1 January 2024. (CS-19310)

  • Games configured with a downward metric didn't award prizes to users with a metric value of 0. (CS-18864)

  • The Contact Arrival widget didn't show the correct data. (CS-20539)

  • The Interval widget didn't show accurate data when filtered by the Days of Week range for inbound queued calls. (CS-20256)

April 2024 Fixes

Published 16 April 2024*

  • When a user edited any setting for a dashboard widget that had a custom name, the custom name was replaced with the default name. (CS-19617, CS-19662, CS-19679, CS-19993)

  • The Summary and Interval widgets showed inaccurate data when the start date was set to the first day of the month and the end date was set to yesterday. (CS-18869, CS-19065)

  • When a user tried to remove a new or existing agent attribute assignment, the action failed and an error appeared. (CS-18568)

  • Some widgets incorrectly displayed the error message "Network connection lost." (CS-19412)

  • The Interval widget incorrectly showed a value of 0 for all days if the date range was set to "This Week" and included days from December 2023 and January 2024. (CS-19210)

  • When users received an invitation to join a game, the invitation wasn't listed on the Join tab of the Games widget until the beginning of the work day. (CS-18493)

Salesforce Agent

Fixed issues for the current Salesforce Agent release and the two previous releases are available on the Salesforce Agent Release History page.

Known Issues

These are the current unresolved issues in CXone products. If a known issue has a workaround, that information is included.

ACD

  • The Automated Chat Messaging Timeout setting in the default skill assigned to the point of contact overrides the setting in any skill the contact is transferred to. You cannot use scripting to override or maintain certain time out settings. So, be careful to avoid this issue when configuring scripts, skills, and points of contact.

Agent for SCV

  • When agents log in to Agent for SCV using the Integrated Softphone, the dialpad doesn't appear. Agents must refresh the browser to load it.

  • When a call disconnects, the call still appears on the screen below the dialpad.

CXone AppLink

  • CXone AppLink does not support multiple NICE Engage systems that are connected to a single CXone tenant.

  • Real-time capabilities, such as Real-Time Monitoring and Real-Time Authentication, are not supported in CXone for CXone AppLink users.

  • All agents imported from NICE Engage must have an email address listed in NICE Engage. Agents without an email address are not created in CXone and their calls are not imported. This does not include calls for basic recording and unmapped users.

  • Teams in NICE Engage are not automatically synchronized with CXone but can be uploaded via the Bulk Employee Upload tool.

  • CXone AppLink can only import up to 50 business data fields.

  • NICE Engage comments, annotations, and categorizations are not supported in CXone.

  • CXone Role-Based Access Control (RBAC) by skill is not supported in CXone for CXone AppLink users.

  • CXone AppLink only uploads H.264 screen recordings to CXone.

  • When playing back imported recordings in CXone, the CXone player does not display pause and resume indications for the recording.

  • A Quality Plan by skill cannot be generated in CXone for CXone AppLink users. You can create a Quality Plan according to a business data field if the skill is populated into that field.

  • Users in NICE Engage who are defined with multiple agents are imported into CXone as a single agent.

Digital Experience

  • Credit card masking with Workflow Automation is only supported for standard credit card format. Credit card issuers may change their range or formatting. Our pattern recognition only supports changes made through March 2024.

  • Chrome doesn't require third-party cookies by default. If you use Chrome as your browser while using Digital Experience with MAX, enable third-party cookies to avoid issues.

IEX WFM Integrated

  • Processing state collector events slows down when the load is heavy.

  • The state publisher restarts intermittently.

Interaction Analytics

  • The metrics for Average Duration and Average Silence do not calculate correctly for the Analytics Category Statistics report. These values are currently hidden in the report until they can be fixed.

  • AutoDiscovery can take a very long time to load and even time out while loading.

CXone Quality Management

  • Conference segments cannot be transcribed/categorized. For example, if an agent adds a participant to a call between them and a customer, the segment up until that point will be transcribed and categorized, but from that point and on, it will not be transcribed or categorized. This is applicable for users with CXone QM Advanced license.

CXone Recording and Playback

  • In the Teams filter, the number of searchable values cannot exceed 400. If there are more than 400 values, some values will not appear in the filter.

    Note that the text search works for all values in the Teams filter.

  • Skills and teams are assigned only to segments with an assigned leading agent. Interactions with no assigned agent include IVR, off-platform, and some outbound dialer interactions. For these interactions, skills and teams are not assigned and interaction-segment-based views are not applicable.

  • When the date range of a search starts before 1 July 2022, sorting by any of the behavioral metrics columns generates an error message. Subsequent filtering also generates the error message. To resolve the issue, close the message and sort on a column that is not behavioral metrics before continuing to filter. To avoid the issue, sort on any column except for behavioral metrics or set the date range for searches after 1 July 2022.

  • For Japanese, be sure to search for interactions using exact text.

  • When the duration of a complex digital channel interaction extends beyond 5 hours, the related segments icon does not appear by the related segments in that call. You can play back each interaction in the call separately, however, sometimes you cannot play back the entire interaction.

  • When a call is transferred to another agent who does not answer, the recorded segment is marked as a complex call. The segment appears in the search results with the Related Segments icon even though there are no related segments.

  • If there is a failover on the ACD side during a call, the recording will be available for search and playback after 5 hours from the call start. In a complex scenario with multiple segments, the call might not be recorded or it might be recorded with unexpected behavior, for example, without masking.

  • Chat and email:

    • For emails that were transferred or reskilled, the transferred/reskilled segment itself does not include the email transcript. Other segments do include the email transcript.

    • Playback does not support attachments.

    • The first segment in a chat only allows playback of the one segment. The full contact can be played back from subsequent chat segments.

  • For calls transferred to external phone numbers:

    • When transferring from the IVR, the external interaction is not recorded.

    • When using a cold transfer, the external interaction is recorded, even if there is a Do Not Record policy with the external participant’s phone number.

    • For a conference call, playing back a contact displays the name of external participant as Customer. In all other cases, the name of external participant appears as Other Participant.

    • The interaction between the customer and external participant is recorded in mono mode.

    • The segments transferred to external phone numbers do not display the agent names in the search grid because agents are not involved in such segments.

  • CXone Recording provides some limited support of silence suppression during the call when the carrier uses silence suppression to lower the bandwidth due to external issues and for a few seconds. We recommend that you work with NICE NetOps and the carrier to ensure silence suppression is disabled on the carrier side since it may reduce the quality of the call recording.

  • Screen recording policies allow you to define a period of recording the screen after the call has ended (after call work). After call work recording might exceed the defined time by up to two seconds.

  • If an agent logs in to MAX or Salesforce Agent on more than one computer at a time, when screen is recorded, it's recorded for all computers. For those recordings, the screen recording won't play back correctly.

  • For calls that include more than one screen recording, such as conference calls, consultations, and internal calls, the player only displays the screens of one of the agents during playback. The player indicates which agent's screens are being played back.

  • If a call is transferred from one agent to another, the screens of both agents are played back in the resolution of the first agent’s screen.

  • Screen recording is initiated up to 25 seconds after the agent logs in. Screen recording might not work properly during these 25 seconds. This issue only affects tenants configured with 100% screen recording.

  • Sometimes a black screen appears during playback:

    • There was a screen recording delay (milliseconds) due to latency. In this case, a black screen may appear at the beginning of the call to synchronize playback of the screen and voice recordings.

    • The agent ran an app with admin permissions during the call recording. In this case, screen recording stops when the UAC message appears.

      Screen recording restarts when the pop-up is closed. During playback, a black screen appears while screen recording was stopped.

  • The ScreenAgent application does not work properly if installed with administrative rights on a non-persistent VMWare Horizon VDI (Virtual Desktop Infrastructure).

    The alternatives are to install the application with non-administrative rights or to use a persistent environment.

  • If you download calls from Secure External Access that were recorded before December 10, 2018, you won’t be able to play them back.

    To save or play back a specific call (even if it was recorded before December 10, 2018), you can go to Search and find the call. Then, from the Player, you can play it back or download it.

Reporting

  • When an agent initiates an outbound email, the Digital Messages report does not include it in the Agent Messages count. The case IDs for outbound emails display as null in the Agent Messages column of the report.

  • Errors occur in the Activity Audit report and Change Audit report when the Time Period is set to more than the Last 7 days.

  • The Time Utilization report displays data for inactive agents. This happens when agents are deactivated, but their schedules have already been generated. The report will continue to display the agent's data for the duration of the generated schedule.

    For example, an agent's schedule was made in May 2023 and lasts until September 2023. The agent was deactivated in June 2023. Even though the agent is deactivated, their data still appears in the report until September 2023.

CXone Workforce Management

General CXone WFM
  • For CXone ACD users: CXone WFM shows all actual agent states sent by CXone ACD. CXone ACD sends data differently to CXone applications. This means that the data displayed in one app can be inconsistent with the ACD data in other apps.

    For example, dialer states are sent to Supervisor and Dashboard but not to CXone WFM. In these cases, they will either be displayed as available or won't be reported at all in CXone WFM.

  • If you activated CXone WFM for the first time after November 2022 and have the CXone ACD, the historical data may not be readily available to CXone WFM. Contact support to import the historical data from CXone ACD to CXone WFM.

  • Data of inactive agents for whom schedules were already published is retained. As a result, these inactive agents' data is getting populated in the adherence reports.

    This can be avoided. Deselect the inactive agents in the Filter Data while running the reports. This will exclude the inactive agents' data from getting populated in the adherence reports.

  • The inactive agents and their data are shown in the time utilization report. This occurs when agents' schedules for future dates are generated prior to deactivation. The agent's data will continue to be displayed in the report for the duration of the generated schedule.

    For example, Agent A's schedule was made on 1st May 23 and lasts until 30th September 23. Agent A was deactivated on 24 June 23. Even though Agent A is deactivated, the data will remain on the report until 30 September 23.

Intraday
  • If incorrect ACD data was received or no data was received at all, Intraday can still get updated with the correct data when the issue is solved. However, Intraday can only get data from the last 24 hours.

  • Intraday widget are no longer available in Dashboard app.

  • When exporting, the file may be missing data if you select more than 50 skills. To avoid missing data, try lowering the date range or exporting twice with a shorter date range for each export. Let's say you want to export 50 skills over 14 days. Try exporting twice, each export for 7 days.

RTA
  • Real-Time Adherence (RTA) displays agent adherence in real time. Because the page refreshes often, it’s recommended to have a focused view. This means that you limit the number of displayed agents to under 250. You can lower the number of displayed agents by using filters.

  • Some mapped activities may be displayed as unmapped in Real-Time Adherence. If this happens, try to enter the mapped activity in the ACD mapping page and click Submit.

Scheduling

In Schedule Manager, the net staffing values are not getting updated upon applying the Groups and Activity Codes filters.