Difference between revisions of "RN/GenesysWeb Services and Applications/9.0.003.25"

From Genesys Documentation
Jump to: navigation, search
 
Line 47: Line 47:
 
}}
 
}}
 
{{Issue
 
{{Issue
 +
|TicketNumber=GAPI-37462
 
|IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260
 
|IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260
|LocalContent=Agents might not be able to login to all digital media channels (chat, email, workitem, and so on.) in Interaction Server, when GWS Interaction Service is connected to multiple Interaction Servers through the Interaction Server Proxy or the cluster of Interaction Server Proxies. This scenario is common when separate Interaction Servers are deployed for different media channels.
+
|LocalContent=Agents might not be able to login to all digital media channels (chat, email, workitem, and so on.) in Interaction Server, when GWS Interaction Service is connected to multiple Interaction Servers through the Interaction Server Proxy or the cluster of Interaction Server Proxies. This scenario is common when separate Interaction Servers are deployed for different media channels. <br />
 
 
  
 
'''Workaround:''' Set the Stat Server option [https://docs.genesys.com/Documentation/Options/Current/RTME/Stat_Server-statserver#suppress-agent-status-updates-for-ixn-server suppress-agent-status-updates-for-ixn-server] to <code>true</code> for all Stat Servers (both reporting and routing). This will prevent Stat Server from triggering the distribution of the '''EventCurrentAgentStatus''' event by Interaction Servers after an agent is logged in. Before applying the workaround, ensure that there are no '''custom''' applications using this event. Note that this event is not used by any Genesys application.
 
'''Workaround:''' Set the Stat Server option [https://docs.genesys.com/Documentation/Options/Current/RTME/Stat_Server-statserver#suppress-agent-status-updates-for-ixn-server suppress-agent-status-updates-for-ixn-server] to <code>true</code> for all Stat Servers (both reporting and routing). This will prevent Stat Server from triggering the distribution of the '''EventCurrentAgentStatus''' event by Interaction Servers after an agent is logged in. Before applying the workaround, ensure that there are no '''custom''' applications using this event. Note that this event is not used by any Genesys application.
 
}}
 
}}

Latest revision as of 05:30, July 4, 2023

Component RN Definition[edit source]

Component Genesys Web Services and Applications
Deployment Type Private Edition
Release Number 9.0.003.25 (Change release number)
Release Type
Highlight Updates to the container base image and resolved issues.
Boilerplate(s) Used
Release Date 2023-05-25
Private Edition Release Date 2023-05-25
Mixed Mode Release ReleaseDate
Private Edition Containers List
JQL labels = GWSMay25
Links Links to customer-facing pages in use:
Test Links Links to test pages (for RN Admins only)

None yet!

Issue Issue Category Description SupportingDocumentation
Issue Issue Category Description SupportingDocumentation
GAPI-37294 Resolved Issue The GWS Workspace service now tries to rejoin the Chat session multiple times (up to 5 attempts with...
GAPI-35068 Resolved Issue API clients are now cleaned up and unregistered from Interaction Server after they got inactive and ...
GAPI-32066 Resolved Issue The Provisioning API's bulk import now supports a dedicated Use WebRTC column to control corre...
GAPI-36444 Resolved Issue Agents can now view all chats in applications that rely on Workspace API including Workspace Web Age...
GAPI-37462 Known Issue Agents might not be able to login to all digital media channels (chat, email, workitem, and so on.) ...
GAPI-37347 Private Edition Updated the third-party dependencies as part of an ongoing security best practice.
GAPI-37300 Private Edition Workspace Web Edition now uploads attachments with the MSG file extension for emails. To configure t...
GAPI-36904 Private Edition Improved delivering of unsolicited events from Interaction Server. Previously, some events might not...
Comments or questions about this documentation? Contact us for support!