Difference between revisions of "RN/AgentDesktop/9.0.000.91"
From Genesys Documentation
(Published) |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
|ComponentId=acaca529-aedd-4820-8557-4966ab8490db | |ComponentId=acaca529-aedd-4820-8557-4966ab8490db | ||
|JQL=labels = "wwe-march-22" | |JQL=labels = "wwe-march-22" | ||
| − | |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a | + | |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1 |
|ReleaseDate=2022-03-22 | |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. | ||
| 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. | |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. | |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. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=GAPI-32533 | ||
| + | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
| + | |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. | ||
| + | |||
| + | {{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 '''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. | ||
| + | |||
| + | {{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://my-application.com?url=https://my-app.com/page.aspx#session&interactionid=xxxx, | ||
| + | *Use this: https://my-application.com?url=https://my-app.com/page.aspx%23session&interactionid=xxxx | ||
| + | |3}} | ||
| + | |||
| + | Previously, due to the double encoding, the case with the hash ‘#’ character wasn’t supported by Workspace. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=GAPI-31259 | ||
| + | |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72 | ||
| + | |LocalContent='''Update:''' Agent Workspace now supports CX Contact labels for user-defined fields. | ||
}} | }} | ||
Latest revision as of 19:21, July 28, 2022
Component RN Definition[edit source]
| Component | Agent Workspace |
|---|---|
| Deployment Type | Genesys CX on AWS, Genesys CX on Azure |
| Release Number | 9.0.000.91 (Change release number) |
| Release Type | |
| Highlight | The Interaction notification and Team Communicator Recents list now displays the contact name and the number of missed calls from the contact. |
| Boilerplate(s) Used | |
| Release Date | 2022-03-22 |
| Private Edition Release Date | |
| Mixed Mode Release ReleaseDate | |
| Private Edition Containers List | |
| JQL | labels = "wwe-march-22" |
| Links | Links to customer-facing pages in use: |
| Test Links | Links to test pages (for RN Admins only) |
| Issue | Issue Category | Description | SupportingDocumentation |
|---|---|---|---|
| Issue | Issue Category | Description | SupportingDocumentation |
| GAPI-33291 | New | To be complaint with WCAG 2.1 level AA, the contrast ratio of the placeholder text in the Search... | |
| GAPI-32949 | New | For environments using browser-based WebRTC, agents who are on a consultation call can now mute and ... | |
| GAPI-32268 | New | If the contact name is available in the SIP header and is not present in the Contact Directory... | |
| GAPI-30936 | New | When displaying interactions in the Details tab of the History view, Workspace now only ... | |
| GAPI-31259 | New | Update: Agent Workspace now supports CX Contact labels for user-defined fields. | |
| GAPI-33561 | Resolved Issue | When the Pending State feature is configured, the After Call Work (ACW) duration displayed in ... | |
| GAPI-33258 | Resolved Issue | Changing the phone type from WebRTC to Generic in Agent Setup no longer prevents agents ... | |
| GAPI-32533 | Resolved Issue | Workspace now correctly handles URLs set in an application running in an iframe in INTERNAL and BACK... |
Contents
Comments or questions about this documentation? Contact us for support!