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

From Genesys Documentation
Jump to: navigation, search
Line 3: Line 3:
 
|JQL=labels = wwe-march-23
 
|JQL=labels = wwe-march-23
 
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
|ReleaseDate=2023-04-18
+
|ReleaseDate=2023-04-20
|Highlight=Third-party dependency updates to maintain security and reliability.
+
|Highlight=Resolved issues and improvements.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 10: Line 10:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE]_Agent Workspace now performs the SmartFailover recovery in better way, thanks to voice channel status improvements. Previously, under certain circumstances, the SmartFailover recovery was mistakenly performed._
 
|Content=[WWE]_Agent Workspace now performs the SmartFailover recovery in better way, thanks to voice channel status improvements. Previously, under certain circumstances, the SmartFailover recovery was mistakenly performed._
|LocalContent=[WWE]_Agent Workspace now performs the SmartFailover recovery in better way, thanks to voice channel status improvements. Previously, under certain circumstances, the SmartFailover recovery was mistakenly performed._
+
|LocalContent=Agent Workspace now performs the SmartFailover recovery in better way, thanks to voice channel status improvements. Previously, under certain circumstances, the SmartFailover recovery was mistakenly performed.
 
}}
 
}}
 
{{Issue
 
{{Issue
 
|TicketNumber=WWE-2762
 
|TicketNumber=WWE-2762
|IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
+
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE]:[AWS][Azure]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Please contact Genesys to enable this behavior.[Private]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Use the {{teamcommunicator.enable-lazy-loading.enabled-browsers}} new option to configure this feature for other browsers:* *Default Value*: IE11* *Valid Values*: Comma-separated list of browser names from the following list: {{IE11}}, {{Chrome}}, {{Firefox}}, {{Edge}}* *Dependencies*: teamcommunicator.enable-lazy-loading* Specify the list of browsers for which lazy loading in Team Communicator is enabled
 
|Content=[WWE]:[AWS][Azure]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Please contact Genesys to enable this behavior.[Private]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Use the {{teamcommunicator.enable-lazy-loading.enabled-browsers}} new option to configure this feature for other browsers:* *Default Value*: IE11* *Valid Values*: Comma-separated list of browser names from the following list: {{IE11}}, {{Chrome}}, {{Firefox}}, {{Edge}}* *Dependencies*: teamcommunicator.enable-lazy-loading* Specify the list of browsers for which lazy loading in Team Communicator is enabled
|LocalContent=[WWE]:[AWS][Azure]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Please contact Genesys to enable this behavior.[Private]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Use the {{teamcommunicator.enable-lazy-loading.enabled-browsers}} new option to configure this feature for other browsers:* *Default Value*: IE11* *Valid Values*: Comma-separated list of browser names from the following list: {{IE11}}, {{Chrome}}, {{Firefox}}, {{Edge}}* *Dependencies*: teamcommunicator.enable-lazy-loading* Specify the list of browsers for which lazy loading in Team Communicator is enabled
+
|LocalContent=To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Please contact Genesys to enable this behavior.<!--[Private]:To reduce the latency when a large number of results have to be displayed in Team Communicator, lazy loading is now available in Team Communicator for all browsers. Previously, lazy loading was available only in Internet Explorer 11 and latency might appear when a large number of results have to be displayed in Team Communicator with other browsers. Use the &lbrace;&lbrace;teamcommunicator.enable-lazy-loading.enabled-browsers&rbrace;&rbrace; new option to configure this feature for other browsers:* *Default Value*: IE11* *Valid Values*: Comma-separated list of browser names from the following list: &lbrace;&lbrace;IE11&rbrace;&rbrace;, &lbrace;&lbrace;Chrome&rbrace;&rbrace;, &lbrace;&lbrace;Firefox&rbrace;&rbrace;, &lbrace;&lbrace;Edge&rbrace;&rbrace;* *Dependencies*: teamcommunicator.enable-lazy-loading* Specify the list of browsers for which lazy loading in Team Communicator is enabled-->
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 22: Line 22:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE][AWS][Azure]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.[Private]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.
 
|Content=[WWE][AWS][Azure]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.[Private]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.
|LocalContent=[WWE][AWS][Azure]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.[Private]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.
+
|LocalContent=In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.<!--[Private]:In Agent Workspace, WebRTC agents stops now the related streams when the call is ended. Previously, is some situations, the microphone could stay active.-->
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 28: Line 28:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=[WWE]:[AWS][Azure][Private]:* The display name of the "workitem" media is now localized as other media. Previously "Display Name" property of the corresponding Business Attribute was used.* The display name of the "chat" media is now correctly translated in Canadian (fr-ca). It was previously truncated to 8 characters. It is now "clavardage" instead of "clavard.".* The translation of "My Interaction Queues" in both French (fr-fr) and Canadian (fr-ca) is updated. It is now "Mes files d'attente d'interactions" instead of "Mes files d'attente interactions".
 
|Content=[WWE]:[AWS][Azure][Private]:* The display name of the "workitem" media is now localized as other media. Previously "Display Name" property of the corresponding Business Attribute was used.* The display name of the "chat" media is now correctly translated in Canadian (fr-ca). It was previously truncated to 8 characters. It is now "clavardage" instead of "clavard.".* The translation of "My Interaction Queues" in both French (fr-fr) and Canadian (fr-ca) is updated. It is now "Mes files d'attente d'interactions" instead of "Mes files d'attente interactions".
|LocalContent=[WWE]:[AWS][Azure][Private]:* The display name of the "workitem" media is now localized as other media. Previously "Display Name" property of the corresponding Business Attribute was used.* The display name of the "chat" media is now correctly translated in Canadian (fr-ca). It was previously truncated to 8 characters. It is now "clavardage" instead of "clavard.".* The translation of "My Interaction Queues" in both French (fr-fr) and Canadian (fr-ca) is updated. It is now "Mes files d'attente d'interactions" instead of "Mes files d'attente interactions".
+
|LocalContent=The display name of the "workitem" media is now localized as other media. Previously "Display Name" property of the corresponding Business Attribute was used.* The display name of the "chat" media is now correctly translated in Canadian (fr-ca). It was previously truncated to 8 characters. It is now "clavardage" instead of "clavard.".* The translation of "My Interaction Queues" in both French (fr-fr) and Canadian (fr-ca) is updated. It is now "Mes files d'attente d'interactions" instead of "Mes files d'attente interactions".
 
}}
 
}}
 
{{Issue
 
{{Issue
 
|TicketNumber=WWE-237
 
|TicketNumber=WWE-237
|IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400
+
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=_[WWE]:__[AWS][Azure]_The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. Please contact Genesys to enable this behaviour.  [Private]The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. This can be done using the corresponding options: 'contact.myhistory-advanced-search-state-filter', 'contact.history-advanced-search-state-filter', and 'contact.all-interactions-advanced-search-state-filter'.
 
|Content=_[WWE]:__[AWS][Azure]_The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. Please contact Genesys to enable this behaviour.  [Private]The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. This can be done using the corresponding options: 'contact.myhistory-advanced-search-state-filter', 'contact.history-advanced-search-state-filter', and 'contact.all-interactions-advanced-search-state-filter'.
|LocalContent=_[WWE]:__[AWS][Azure]_The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. Please contact Genesys to enable this behaviour.  [Private]The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. This can be done using the corresponding options: 'contact.myhistory-advanced-search-state-filter', 'contact.history-advanced-search-state-filter', and 'contact.all-interactions-advanced-search-state-filter'.
+
|LocalContent=The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. Please contact Genesys to enable this behaviour.  <!--[Private]The Agent Workspace now allows users to configure the values of the interaction state filter drop-down used in advanced search for the 'My History', 'Contact History', and 'Interaction Search' pages. This can be done using the corresponding options: 'contact.myhistory-advanced-search-state-filter', 'contact.history-advanced-search-state-filter', and 'contact.all-interactions-advanced-search-state-filter'.-->
 
}}
 
}}

Revision as of 07:00, April 20, 2023

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

Component RN Definition[edit source]

Component Agent Workspace
Deployment Type Genesys CX on AWS, Genesys CX on Azure
Release Number 100.0.005.0394 (Change release number)
Release Type
Highlight Resolved issues and improvements.
Boilerplate(s) Used
Release Date 2023-04-20
Private Edition Release Date
Mixed Mode Release ReleaseDate
Private Edition Containers List
JQL labels = wwe-march-23
Links Links to customer-facing pages in use:
Test Links Links to test pages (for RN Admins only)

No results