RN/AgentDesktop/9.0.000.86 - Revision history

WikiSysop at 19:21, July 28, 2022

2022-07-28T19:21:00Z

WikiSysop at 12:30, July 26, 2022

2022-07-26T12:30:45Z

Matthew.west@genesys.com: Published

2021-10-29T20:05:58Z

Published

Matthew.west@genesys.com: Published

2021-09-20T16:50:45Z

Published

Tanya.ivanova@genesys.com: Published

2021-09-17T21:13:40Z

Published

Matthew.west@genesys.com: Published

2021-09-17T20:18:21Z

Published

Matthew.west@genesys.com: Published

2021-09-16T17:47:01Z

Published

New page

{{ComponentRN
|ComponentId=acaca529-aedd-4820-8557-4966ab8490db
|JQL=labels = WWE-September-21
|DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1
|ReleaseDate=2021-09-16
|Highlight=Resolved issues and improvements.
}}
{{Issue
|TicketNumber=GAPI-30312
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=[WWE]:[AZURE]:The scroll bar in Team Communicator for the transfer, conference, and consultation functions no longer disappears when an agent scrolls up and down the list of suggestions.
|LocalContent=The scroll bar in '''Team Communicator''' for the transfer, conference, and consultation functions no longer disappears when an agent scrolls up and down the list of suggestions.
}}
{{Issue
|TicketNumber=GAPI-30278
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=[WWE]:[AWS AZURE PRIVATE?]:Agent Desktop now correctly re-establishes connection to the softphone in the following scenario:# A long network disconnection occurs.# The agent keeps open a tab with Agent Desktop and the disconnection occurs during this session.# The agent opens a new tab to log in to Agent Desktop while the other tab is still open.
|LocalContent=Agent Desktop now correctly re-establishes connection to the softphone in the following scenario:

#A long network disconnection occurs.
#The agent keeps open a tab with Agent Desktop and the disconnection occurs during this session.
#The agent opens a new tab to log in to Agent Desktop while the other tab is still open.
}}
{{Issue
|TicketNumber=GAPI-30271
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=[WWE]:[AWS AZURE PRIVATE?]:If a very short network disconnection occurs, Agent Desktop no longer displays notification messages to agents. Previously, Agent Desktop displayed both connection loss and connection back in service notifications every time a micro-disconnection occurred.
|LocalContent=If a very short network disconnection occurs, Agent Desktop no longer displays notification messages to agents. Previously, Agent Desktop displayed both connection loss and connection back in service notifications every time a micro-disconnection occurred.
}}
{{Issue
|TicketNumber=GAPI-29822
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=[WWE]:[AWS AZURE PRIVATE?]:For Internet Explorer users, the Threaded view button no longer appears to be active in the My History view when Advanced Search is selected. Note: For all supported browsers, the Threaded view is not supported for Basic (Quick) or Advanced Search in the My History and Contact History views.
|LocalContent=For Internet Explorer users, the Threaded view button no longer appears to be active in the '''My History''' view when '''Advanced Search''' is selected. '''Note''': For all supported browsers, the '''Threaded''' view is not supported for '''Basic''' (Quick) or '''Advanced Search''' in the '''My History''' and '''Contact History''' views.
}}
{{Issue
|TicketNumber=GAPI-29800
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=[WWE]: [AWS AZURE PRIVATE]: Manual column width adjustment of the My History, Interaction Search, and Contact History grid views has been improved. Previously, there were issues that prevented the column width from being manually adjusted. Now, the mouse can be used as expected to adjust column widths, and when the width of one column is adjusted manually, the other columns adjust automatically to compensate so that all columns always fit 100% of the space available.
|LocalContent=Manual column width adjustment of the '''My History''', '''Interaction Search''', and '''Contact History''' grid views has been improved. Previously, there were issues that prevented the column width from being manually adjusted. Now, the mouse can be used as expected to adjust column widths, and when the width of one column is adjusted manually, the other columns adjust automatically to compensate so that all columns always fit 100% of the space available.
}}
{{Issue
|TicketNumber=GAPI-27623
|Content=[API - SCAPI][Azure/AWS] The Service Client API now provides events when an outbound campaign state is updated.
|LocalContent=The Service Client API now provides events when an outbound campaign state is updated.
}}

@@ Line 2: / Line 2: @@
 |ComponentId=acaca529-aedd-4820-8557-4966ab8490db
 |JQL=labels = WWE-September-21
-|DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a, 5439f1be-1868-4091-b058-1667389b6ce1
+|DeploymentTypeId=5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
 |ReleaseDate=2021-09-16
 |PrivateEditionReleaseDate=2021-09-17
@@ Line 8: / Line 8: @@
 *Private Edition: Support for the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
 *{{PrivateEditionBoilerplate|Boilerplate=gke-eap-high}}
-|Containers=Docker: gws-ui-workspace:9.0.000.86
+|Containers=*wwe-nginx-9.0.4.tgz
+*gws-ui-workspace:9.0.000.86
 }}
 {{Issue

@@ Line 7: / Line 7: @@
 |Highlight=*Resolved issues and improvements.
 *Private Edition: Support for the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
 |Containers=Docker: gws-ui-workspace:9.0.000.86
@@ Line 58: / Line 59: @@
 *Workspace Web Edition is deployed using ServiceAccounts that use the '''restricted''' Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom '''genesys-restricted''' SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the '''genesys-restricted''' SCC has been deprecated. If you previously deployed Workspace Web Edition using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy Workspace Web Edition so that you use arbitrary UIDs.
 |SupportingDocumentation={{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide|topic=Configure|anchor=Security}}
 }}

@@ Line 55: / Line 55: @@
 |LocalContent=Workspace Web Edition now supports the use of arbitrary, or random, user IDs (UIDs) in OpenShift.
 *The securityContext settings exposed in the default '''values.yaml''' file specify the user and group IDs for the genesys user (<tt>500:500:500</tt>). You must override these Helm chart values if you want OpenShift to use arbitrary UIDs.
 *Workspace Web Edition is deployed using ServiceAccounts that use the '''restricted''' Security Context Constraint (SCC). In an earlier implementation, Genesys required you to deploy all private edition services using a ServiceAccount associated with the custom '''genesys-restricted''' SCC, to control permissions for the genesys user (500). Genesys now expects OpenShift to use arbitrary UIDs in your deployment, and the '''genesys-restricted''' SCC has been deprecated. If you previously deployed Workspace Web Edition using the '''genesys-restricted''' SCC, Genesys recommends that you redeploy Workspace Web Edition so that you use arbitrary UIDs.
 |SupportingDocumentation={{Link-AnywhereElse|product=PEC-AD|version=Current|manual=WWEPEGuide|topic=Configure|anchor=Security}}
 }}

@@ Line 4: / Line 4: @@
 |DeploymentTypeId=8b480b3c-2733-433a-9166-eab2c2d0663a, 5439f1be-1868-4091-b058-1667389b6ce1
 |ReleaseDate=2021-09-16
-|PrivateEditionReleaseDate=2021-09-20
+|PrivateEditionReleaseDate=2021-09-17
 |Highlight=*Resolved issues and improvements.
 *Private Edition: Support for the use of arbitrary, or random, user IDs (UIDs) in OpenShift.

@@ Line 20: / Line 20: @@
 |TicketNumber=GAPI-30278
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|Content=[WWE]:[AWS AZURE PRIVATE?]:Agent Desktop now correctly re-establishes connection to the softphone in the following scenario:# A long network disconnection occurs.# The agent keeps open a tab with Agent Desktop and the disconnection occurs during this session.# The agent opens a new tab to log in to Agent Desktop while the other tab is still open.
+|Content=[WWE]:[AWS AZURE PRIVATE?]:Agent Workspace now correctly re-establishes connection to the softphone in the following scenario:# A long network disconnection occurs.# The agent keeps open a tab with Agent Workspace and the disconnection occurs during this session.# The agent opens a new tab to log in to Agent Workspace while the other tab is still open.
-|LocalContent=Agent Desktop now correctly re-establishes connection to the softphone in the following scenario:
+|LocalContent=Agent Workspace now correctly re-establishes connection to the softphone in the following scenario:
 #A long network disconnection occurs.
-#The agent keeps open a tab with Agent Desktop and the disconnection occurs during this session.
+#The agent keeps open a tab with Agent Workspace and the disconnection occurs during this session.
-#The agent opens a new tab to log in to Agent Desktop while the other tab is still open.
+#The agent opens a new tab to log in to Agent Workspace while the other tab is still open.
 }}
 {{Issue
 |TicketNumber=GAPI-30271
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|Content=[WWE]:[AWS AZURE PRIVATE?]:If a very short network disconnection occurs, Agent Desktop no longer displays notification messages to agents. Previously, Agent Desktop displayed both connection loss and connection back in service notifications every time a micro-disconnection occurred.
+|Content=[WWE]:[AWS AZURE PRIVATE?]:If a very short network disconnection occurs, Agent Workspace no longer displays notification messages to agents. Previously, Agent Workspace displayed both connection loss and connection back in service notifications every time a micro-disconnection occurred.
-|LocalContent=If a very short network disconnection occurs, Agent Desktop no longer displays notification messages to agents. Previously, Agent Desktop displayed both connection loss and connection back in service notifications every time a micro-disconnection occurred.
+|LocalContent=If a very short network disconnection occurs, Agent Workspace no longer displays notification messages to agents. Previously, Agent Workspace displayed both connection loss and connection back in service notifications every time a micro-disconnection occurred.
 }}
 {{Issue