Difference between revisions of "Draft: RN/AgentWorkspace/100.0.004.0309"

From Genesys Documentation
Jump to: navigation, search
(Tag: New redirect)
 
Line 1: Line 1:
{{ComponentRN
+
#REDIRECT [[Draft:RN/AgentWorkspace/100.0.004.0312]]
|ComponentId=acaca529-aedd-4820-8557-4966ab8490db
 
|JQL=((project = GAPI AND component in ("Workspace Web Edition", "Workspace Web Edition Deployment Guide", "Workspace Web Edition Help", "Workspace Web Edition - Localization", "GWS Workspace Service", "Gplus Adapter for Salesforce")) OR ( project = "Agent Workspace" ))  AND labels = wwe-february-23
 
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 
|ReleaseDate=2023-03-17
 
|Highlight=Resolved issues and improvements.
 
}}
 
{{Issue
 
|TicketNumber=WWE-2665
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE][AWS][Azure]:Agent Workspace now avoids the auto mark done for Consultation calls. Contact your Genesys Representative to enable this functionality.[Private]:Agent Workspace now avoids the auto mark done for Consultation calls. To enable this feature, set the value of the *voice.consultation.mark-done-on-release* option to *false*.
 
|LocalContent=Agent Workspace now avoids the auto mark done for Consultation calls. Contact your Genesys Representative to enable this functionality.
 
<!--For Private Edition, Agent Workspace now avoids the auto mark done for Consultation calls. To enable this feature, set the value of the '''voice.consultation.mark-done-on-release''' option to <code>false</code>.--!>-->
 
}}
 
{{Issue
 
|TicketNumber=WWE-2608
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|LocalContent=Agent Workspace now avoids duplicating messages in Genesys Digital Channels interactions. Previously, some messages could be duplicated in case of connection issues in backend.
 
}}
 
{{Issue
 
|TicketNumber=WWE-2584
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=TBD
 
|LocalContent=For the '''Interaction Queue''' view, a manual refresh isn’t considered now if the previous refresh was done in less than 5 seconds.
 
<!--For Private Edition, for the '''Interaction Queue''' view, a manual refresh isn’t considered now if the previous one was done less than 5 seconds before.-->
 
}}
 
{{Issue
 
|TicketNumber=WWE-2583
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=TBD
 
|LocalContent=For the '''Contact Center Statistics''' tab, a manual refresh isn’t considered now if the previous refresh was done in less than 5 seconds.
 
<!--For Private Edition, for the '''Contact Center Statistics''' tab, a manual refresh isn’t considered now if the previous one was done less than 5 seconds before.-->
 
}}
 
{{Issue
 
|TicketNumber=WWE-2395
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE]:[AWS][Azure]:[Approved Text]: In Agent Workspace, WebRTC agents can now correctly retrieve a call in a ringing state. Previously, when the WebRTC agent tries to retrieve a call in a ringing state, the music in queue or ringback tone was not heard by the agent.[Private]:[Approved Text]: In Agent Workspace, WebRTC agents can now correctly retrieve a call in a ringing state. Previously, when the WebRTC agent tries to retrieve a call in a ringing state, the music in queue or ringback tone was not heard by the agent.
 
|LocalContent=In Agent Workspace, WebRTC agents can now correctly retrieve a call in a ringing state. Previously, when the WebRTC agent tries to retrieve a call in a ringing state, the music in queue or ringback tone was not heard by the agent.
 
<!--For Private Edition, in Agent Workspace, WebRTC agents can now correctly retrieve a call in a ringing state. Previously, when the WebRTC agent tries to retrieve a call in a ringing state, the music in queue or ringback tone was not heard by the agent.--!>-->
 
}}
 
{{Issue
 
|TicketNumber=WWE-2386
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|Content=[WWE]:[AWS][Azure]:[IX Version]Agent Workspace now allows you extend the duration for which the native toasts are displayed on Chrome and Edge browsers. This allows agents to act on the toasts when Agent Workspace is not in focus for a certain duration. Contact your Genesys Representative to enable this feature.[Private]: [IX Version]Agent Workspace now allows you extend the timeout duration for which the native toasts are displayed on Chrome and Edge browsers. This allows agents to act on the toasts when Agent Workspace is not in focus for a certain duration. To enable this feature, use the following options:* *interaction.native-toast.extend-timeout* to extend the timeout duration of native toasts for all media types. * *interaction.native-toast.&lt;media-type&gt;.extend-timeout* to override the configuration per media.
 
|LocalContent=Agent Workspace now allows you extend the duration for which the native toasts are displayed on Chrome and Edge browsers. This allows agents to act on the toasts when Agent Workspace is not in focus for a certain duration. Contact your Genesys Representative to enable this feature.
 
<!--For Private Edition,  to enable this feature, use the following options:
 
 
 
* '''interaction.native-toast.extend-timeout''' - to extend the timeout duration of native toasts for all media types.
 
* '''interaction.native-toast.&lt;media-type&gt;.extend-timeout''' - to override the configuration per media.-->
 
}}
 
{{Issue
 
|TicketNumber=WWE-2346
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=_[WWE]:__[AWS][Azure][Private]:_The *Processed by* field is now set to *Unknown User* in History or Interaction Search when the related agent has been deleted. Previously, the *Processed by* field was empty in the same scenario.
 
|LocalContent=The '''Processed by''' field is now set to '''Unknown User''' in '''History''' or '''Interaction Search''' when the related agent has been deleted. Previously, the '''Processed by''' field was empty in the same scenario.
 
}}
 
{{Issue
 
|TicketNumber=GAPI-36932
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[Workspace API][Azure][AWS]Reacts appropriately to internal error condition during routed chat consultation, avoiding endless loop for API clients such as Agent Desktop.[GWS][PE]Reacts appropriately to internal error condition during routed chat consultation, avoiding endless loop for API clients such as Agent Desktop.[WWE]:[AWS][Azure][Private]:A chat consultation received by an agent is now stopped if the main chat interaction from which the consultation was created has been placed in a queue or a workbin. Previously, in such situation, the chat consultation was not stopped which affected targeted agent capacity to receive a new chat.
 
|LocalContent=A Chat consultation received by an agent is now stopped if the main Chat interaction from which the consultation originated was placed in a queue or workbin. Previously, in such a situation, the Chat consultation was not stopped which affected the target agent capacity to receive a new chat.
 
}}
 
{{Issue
 
|TicketNumber=GAPI-36408
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE][AWS][Azure]Agent Workspace now performs the SmartFailover recovery when Voice Channel connectivity is lost. Previously, under certain circumstances, the SmartFailover recovery was not performed.[GWS] [PE]Agent Workspace now performs the SmartFailover recovery when Voice Channel connectivity is lost.
 
|LocalContent=Agent Workspace now performs the SmartFailover recovery when the Voice Channel connectivity is lost. Previously, under certain circumstances, the SmartFailover recovery was not performed.
 
<!--For Private Edition, Agent Workspace now performs the SmartFailover recovery when Voice Channel connectivity is lost.--!>-->
 
}}
 

Latest revision as of 12:01, March 13, 2023

This is a draft page; it has not yet been published.