RN/AgentDesktop/9.0.000.91 - Revision history

WikiSysop at 19:21, July 28, 2022

2022-07-28T19:21:09Z

WikiSysop at 17:45, July 18, 2022

2022-07-18T17:45:49Z

WikiSysop at 11:15, June 9, 2022

2022-06-09T11:15:38Z

WikiSysop at 18:30, April 26, 2022

2022-04-26T18:30:33Z

WikiSysop at 16:00, April 7, 2022

2022-04-07T16:00:32Z

WikiSysop at 15:15, April 7, 2022

2022-04-07T15:15:57Z

WikiSysop at 15:00, April 7, 2022

2022-04-07T15:00:33Z

Mwest: Published

2022-04-06T13:48:06Z

Published

Jumunn: Published

2022-03-22T23:45:44Z

Published

Jumunn: Published

2022-03-22T23:42:27Z

Published

New page

{{ComponentRN
|ComponentId=acaca529-aedd-4820-8557-4966ab8490db
|JQL=labels = "wwe-march-22"
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
|ReleaseDate=2022-03-22
|Highlight=The Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact.
}}
{{Issue
|TicketNumber=GAPI-33561
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=\[WWE]\[AWS] \[AZURE] \[PRIVATE]When the Pending State feature is configured, the After Call Work (ACW) duration displayed in the My Channels panel and the Global State tooltip now correctly starts from 00:00 when the call is released. Previously, if an agent set the Voice channel to ACW while the call was active, the ACW duration displayed when the call was released was, in some situations, reported as started when the agent made the manual state change.
|LocalContent=When the '''Pending State''' feature is configured, the After Call Work (ACW) duration displayed in the '''My Channels''' tab and the '''Global State''' tooltip now correctly starts from 00:00 when the call is released. Previously, if an agent set the Voice channel to ACW while the call was active, the ACW duration displayed when the call was released was, in some situations, reported as started when the agent made the manual state change.
}}
{{Issue
|TicketNumber=GAPI-33291
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=\[WWE]\[AWS] \[AZURE] \[PRIVATE]To be complaint with WCAG 2.1 level AA, the contrast ratio of the placeholder text in the Search fields is improved.
|LocalContent=To be complaint with WCAG 2.1 level AA, the contrast ratio of the placeholder text in the '''Search''' fields is improved.
}}
{{Issue
|TicketNumber=GAPI-33258
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=\[AWS Azure PE] Changing the phone type from *WebRTC* to *Generic* in Agent Setup no longer prevents agents from logging in to Agent Workspace
|LocalContent=Changing the phone type from '''WebRTC''' to '''Generic''' in Agent Setup no longer prevents agents from logging in to Agent Workspace
}}
{{Issue
|TicketNumber=GAPI-32949
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=\[WWE]\[AWS] \[AZURE] \[PRIVATE]For environments using browser-based WebRTC, agents who are on a consultation call can now mute and unnute the consultation call when the main call is released. These operations are available from the consultation toolbar.
|LocalContent=For environments using browser-based WebRTC, agents who are on a consultation call can now mute and unmute the consultation call when the main call is released. These operations are available from the Consultation toolbar.
}}
{{Issue
|TicketNumber=GAPI-32268
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=\[WWE]\[AWS] \[AZURE] \[PRIVATE]If the contact name is available in the SIP header and is not present in the Contact Directory, the Interaction notification and Team Communicator Recents list now displays the contact name and the number of missed calls from the contact. Please contact Genesys to enable this feature.
|LocalContent=If the contact name is available in the SIP header and is not present in the '''Contact Directory''', the Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact. Please contact Genesys to enable this feature.
}}
{{Issue
|TicketNumber=GAPI-30936
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=\[WWE]-\[AWS] \[AZURE]- \[PRIVATE]When displaying interactions in the Details tab of the History view, Workspace now only sends requests for attachments to UCS for the Email channel. Currently, attachment display in the Details tab is supported only for Email interactions.
|LocalContent=When displaying interactions in the '''Details''' tab of the '''History''' view, Workspace now only sends requests for attachments to UCS for the Email channel. Currently, attachment display in the '''Details''' tab is supported only for Email interactions.
}}

@@ Line 64: / Line 64: @@
 |TicketNumber=GAPI-31259
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
-|LocalContent='''Update:''' Agent Desktop now supports CX Contact labels for user-defined fields.
+|LocalContent='''Update:''' Agent Workspace now supports CX Contact labels for user-defined fields.
 }}

@@ Line 4: / Line 4: @@
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 |ReleaseDate=2022-03-22
-|Highlight=*The Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact.
+|Highlight=*'''Updated''': 06/01/22 to include GAPI-31259
 *Updated information for the resolved issue GAPI-32533.
 }}
@@ Line 61: / Line 63: @@
 Previously, due to the double encoding, the case with the hash ‘#’ character wasn’t supported by Workspace.
 }}

@@ Line 50: / Line 50: @@
 {{NoteFormat|This change might break existing integrations depending on how the custom URL is currently formatted and how the Web server handles it.|1}}
-'''UPDATE:''' Workspace now also encodes URLs associated with the '''interaction.web-content''' option (refer to [https://docs.genesys.com/Documentation/HTCC/9.0.0/IWWDep/ConfigUI#WebApp Enabling integration of web applications]), if Workspace determines that the URL defined by this option contains no encoded content. Workspace scans the URL to find a percent ‘%’ character followed by hexadecimal values (for example, '%23'). If no encoded content is found, Workspace encodes the URL using the '''EncodeURI''' javascript function. This function excludes specific characters from encoding processing. Refer to the [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI EncodeURI documentation] for information.
+'''UPDATE:''' Workspace now also encodes URLs associated with the '''Customer Location''' option (refer to {{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=External_URLs}}), if Workspace determines that the URL defined by this option contains no encoded content. Workspace scans the URL to find a percent ‘%’ character followed by hexadecimal values (for example, '%23'). If no encoded content is found, Workspace encodes the URL using the '''EncodeURI''' javascript function. This function excludes specific characters from encoding processing. Refer to the [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI EncodeURI documentation] for information.
 Previously, Workspace systematically encoded URLs, even if they already contained encoded characters.

@@ Line 4: / Line 4: @@
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 |ReleaseDate=2022-03-22
-|Highlight=* The Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact.
+|Highlight=*The Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact.
-* Updated information for the resolved issue GAPI-32533.
+*Updated information for the resolved issue GAPI-32533.
 }}
 {{Issue
@@ Line 48: / Line 48: @@
 |LocalContent=Workspace now correctly handles URLs set in an application running in an iframe in INTERNAL and BACKGROUND modes. Previously, Workspace tried to encode URLs that were already encoded.
-'''Note:''' This change might break existing integrations depending on how the custom URL is currently formatted and how the Web server handles it.
+{{NoteFormat|This change might break existing integrations depending on how the custom URL is currently formatted and how the Web server handles it.|1}}
 '''UPDATE:''' Workspace now also encodes URLs associated with the '''interaction.web-content''' option (refer to [https://docs.genesys.com/Documentation/HTCC/9.0.0/IWWDep/ConfigUI#WebApp Enabling integration of web applications]), if Workspace determines that the URL defined by this option contains no encoded content. Workspace scans the URL to find a percent ‘%’ character followed by hexadecimal values (for example, '%23'). If no encoded content is found, Workspace encodes the URL using the '''EncodeURI''' javascript function. This function excludes specific characters from encoding processing. Refer to the [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI EncodeURI documentation] for information.
@@ Line 54: / Line 54: @@
 Previously, Workspace systematically encoded URLs, even if they already contained encoded characters.
-'''Warning:''' Characters not escaped by the '''EncodeURI''' function could corrupt the final URL requested by Workspace. The following example includes a URL containing the hash '#' character as a value of a query parameter. In this scenario, the request URL sent to the Web server is truncated. To prevent the truncation of the requested URL sent to the Web server, replace the hash character with '%23’:
+{{NoteFormat|Characters not escaped by the '''EncodeURI''' function could corrupt the final URL requested by Workspace. The following example includes a URL containing the hash '#' character as a value of a query parameter. In this scenario, the request URL sent to the Web server is truncated. To prevent the truncation of the requested URL sent to the Web server, replace the hash character with '%23’:
-*Instead of this: https&#58;//my-application.com?url=https&#58;//my-app.com/page.aspx#session&interactionid=xxxx,
+*Instead of this: https&#58;//my-application.com?url&#61;https&#58;//my-app.com/page.aspx#session&interactionid&#61;xxxx,
-*Use this: https&#58;//my-application.com?url=https&#58;//my-app.com/page.aspx%23session&interactionid=xxxx
+*Use this: https&#58;//my-application.com?url&#61;https&#58;//my-app.com/page.aspx%23session&interactionid&#61;xxxx
 Previously, due to the double encoding, the case with the hash ‘#’ character wasn’t supported by Workspace.
 }}

@@ Line 4: / Line 4: @@
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 |ReleaseDate=2022-03-22
-|Highlight=The Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact.
+|Highlight=* The Interaction notification and Team Communicator '''Recents''' list now displays the contact name and the number of missed calls from the contact.
 }}
 {{Issue
@@ Line 55: / Line 56: @@
 '''Warning:''' Characters not escaped by the '''EncodeURI''' function could corrupt the final URL requested by Workspace. The following example includes a URL containing the hash '#' character as a value of a query parameter. In this scenario, the request URL sent to the Web server is truncated. To prevent the truncation of the requested URL sent to the Web server, replace the hash character with '%23’:
-*Instead of this: https://my-application.com?url=https://my-app.com/page.aspx#session&interactionid=xxxx,
+*Instead of this: https&#58;//my-application.com?url=https&#58;//my-app.com/page.aspx#session&interactionid=xxxx,
-*Use this: https://my-application.com?url=https://my-app.com/page.aspx%23session&interactionid=xxxx
+*Use this: https&#58;//my-application.com?url=https&#58;//my-app.com/page.aspx%23session&interactionid=xxxx
 Previously, due to the double encoding, the case with the hash ‘#’ character wasn’t supported by Workspace.
 }}

@@ Line 41: / Line 41: @@
 |Content=\[WWE]-\[AWS] \[AZURE]- \[PRIVATE]When displaying interactions in the Details tab of the History view, Workspace now only sends requests for attachments to UCS for the Email channel. Currently, attachment display in the Details tab is supported only for Email interactions.
 |LocalContent=When displaying interactions in the '''Details''' tab of the '''History''' view, Workspace now only sends requests for attachments to UCS for the Email channel. Currently, attachment display in the '''Details''' tab is supported only for Email interactions.
 }}