Difference between revisions of "RN/AgentWorkspace/9.0.000.98"
From Genesys Documentation
(Created page with "{{ComponentRN |ComponentId=acaca529-aedd-4820-8557-4966ab8490db |JQL=labels = "wwe-september-22" |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 8b480b3c-2733-433a-916...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 6: | Line 6: | ||
|PrivateEditionReleaseDate=2022-09-29 | |PrivateEditionReleaseDate=2022-09-29 | ||
|Highlight=Support for messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. | |Highlight=Support for messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. | ||
| + | |Containers=*wwe-nginx-9.0.6.tgz | ||
| + | *gws-ui-workspace:9.0.000.98 | ||
}} | }} | ||
{{Issue | {{Issue | ||
| Line 18: | Line 20: | ||
|Content=\[WWE]\[AWS] \[Azure]:Agent Workspace can now control which attached data keys are excluded during the creation of an inline forwarded email. The default excluded attached data keys (ContactId, EmailAddress, FirstName, LastName, PhoneNumber, toAddresses) can be removed from exclusion and custom attached data keys can be added.Previously, it was not possible to change this list of excluded attached data keys.Please contact Genesys to adjust this behavior\[Private]:Agent Workspace can now control which attached data keys are excluded during the creation of an inline forwarded email. The default excluded attached data keys (ContactId,EmailAddress,FirstName,LastName,PhoneNumber,toAddresses) can be removed from exclusion and custom attached data keys can be added. Use the *email.inline-forward.exclude-case-data-keys* option to configure this behavior. Previously, it was not possible to change this list of excluded attached data keys. | |Content=\[WWE]\[AWS] \[Azure]:Agent Workspace can now control which attached data keys are excluded during the creation of an inline forwarded email. The default excluded attached data keys (ContactId, EmailAddress, FirstName, LastName, PhoneNumber, toAddresses) can be removed from exclusion and custom attached data keys can be added.Previously, it was not possible to change this list of excluded attached data keys.Please contact Genesys to adjust this behavior\[Private]:Agent Workspace can now control which attached data keys are excluded during the creation of an inline forwarded email. The default excluded attached data keys (ContactId,EmailAddress,FirstName,LastName,PhoneNumber,toAddresses) can be removed from exclusion and custom attached data keys can be added. Use the *email.inline-forward.exclude-case-data-keys* option to configure this behavior. Previously, it was not possible to change this list of excluded attached data keys. | ||
|LocalContent=Agent Workspace can now control which attached data keys are excluded during the creation of an inline forwarded email. The default excluded attached data keys (ContactId, EmailAddress, FirstName, LastName, PhoneNumber, toAddresses) can be removed from exclusion and custom attached data keys can be added. Previously, it was not possible to change this list of excluded attached data keys. Please contact Genesys to adjust this behavior. | |LocalContent=Agent Workspace can now control which attached data keys are excluded during the creation of an inline forwarded email. The default excluded attached data keys (ContactId, EmailAddress, FirstName, LastName, PhoneNumber, toAddresses) can be removed from exclusion and custom attached data keys can be added. Previously, it was not possible to change this list of excluded attached data keys. Please contact Genesys to adjust this behavior. | ||
| − | + | ||
| − | '''For Private Edition''', use the '''email.inline-forward.exclude-case-data-keys''' option to configure this behavior. | + | '''For Private Edition''', use the '''email.inline-forward.exclude-case-data-keys''' option to configure this behavior. |
| − | |SupportingDocumentation= | + | |SupportingDocumentation=[https://docs.genesys.com/Options:Genesys_Web_Services:interaction-workspace:email-inline-forward-exclude-case-data-keys email.inline-forward.exclude-case-data-keys] |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 27: | Line 29: | ||
|Content=\[WWE]\[AWS] \[Azure]:Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are configured for auto-answer after a timeout duration. Unlimited ringing time is configured by setting the value of the ringtone duration to -1. Previously in this scenario, when the interaction notification was displayed, the ringtone did not always play.\[Private]:Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are configured for auto-answer after a timeout duration. Unlimited ringing time is configured by setting the ringtone duration to -1 using *<media-type>.ringing-bell* option. The auto-answer timeout duration is configured by setting the value of the *<media-type>.auto-answer.timer* option. Previously in this scenario, when the interaction notification was displayed, the ringtone did not always play. | |Content=\[WWE]\[AWS] \[Azure]:Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are configured for auto-answer after a timeout duration. Unlimited ringing time is configured by setting the value of the ringtone duration to -1. Previously in this scenario, when the interaction notification was displayed, the ringtone did not always play.\[Private]:Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are configured for auto-answer after a timeout duration. Unlimited ringing time is configured by setting the ringtone duration to -1 using *<media-type>.ringing-bell* option. The auto-answer timeout duration is configured by setting the value of the *<media-type>.auto-answer.timer* option. Previously in this scenario, when the interaction notification was displayed, the ringtone did not always play. | ||
|LocalContent=Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are configured for auto-answer after a timeout duration. Unlimited ringing time is configured by setting the value of the ringtone duration to '''-1'''. Previously in this scenario, when the interaction notification was displayed, the ringtone did not always play. | |LocalContent=Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are configured for auto-answer after a timeout duration. Unlimited ringing time is configured by setting the value of the ringtone duration to '''-1'''. Previously in this scenario, when the interaction notification was displayed, the ringtone did not always play. | ||
| − | + | ||
| − | '''For Private Edition''', unlimited ringing time is configured by setting the ringtone duration to -1 using '''<media-type>.ringing-bell''' option. The auto-answer timeout duration is configured by setting the value of the '''<media-type>.auto-answer.timer''' option. | + | '''For Private Edition''', unlimited ringing time is configured by setting the ringtone duration to -1 using '''<media-type>.ringing-bell''' option. The auto-answer timeout duration is configured by setting the value of the '''<media-type>.auto-answer.timer''' option. |
| − | |SupportingDocumentation= | + | |SupportingDocumentation=[https://docs.genesys.com/Options:Genesys_Web_Services:interaction-workspace:-media-type-zringing-bell <media-type>.ringing-bell] and [https://docs.genesys.com/Options:Genesys_Web_Services:interaction-workspace:-media-type-zauto-answer-timer <media-type>.auto-answer.timer] |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 54: | Line 56: | ||
|Content=\[WWE]\[AWS] \[Azure]:To better handle inline images from standard responses used as a signature, Agent Workspace now embeds the images in an email interaction by default. Restrictions configured for image size and file type for attachments are also applied to images from standard responses used as a signature.\[Private]:To better handle inline images from standard responses used as a signature, Agent Workspace now embeds the images in an email interaction by default. Restrictions configured for image size and file type for attachments are also applied to images from standard responses used as a signature. The *email.signature.process-embedded-images.enable* option is no longer supported. | |Content=\[WWE]\[AWS] \[Azure]:To better handle inline images from standard responses used as a signature, Agent Workspace now embeds the images in an email interaction by default. Restrictions configured for image size and file type for attachments are also applied to images from standard responses used as a signature.\[Private]:To better handle inline images from standard responses used as a signature, Agent Workspace now embeds the images in an email interaction by default. Restrictions configured for image size and file type for attachments are also applied to images from standard responses used as a signature. The *email.signature.process-embedded-images.enable* option is no longer supported. | ||
|LocalContent=To better handle inline images from standard responses used as a signature, Agent Workspace now embeds the images in an email interaction by default. Restrictions configured for image size and file type for attachments are also applied to images from standard responses used as a signature. | |LocalContent=To better handle inline images from standard responses used as a signature, Agent Workspace now embeds the images in an email interaction by default. Restrictions configured for image size and file type for attachments are also applied to images from standard responses used as a signature. | ||
| − | + | ||
| − | '''For Private Edition''', the '''email.signature.process-embedded-images.enable''' option is no longer supported. | + | '''For Private Edition''', the '''email.signature.process-embedded-images.enable''' option is no longer supported. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 61: | Line 63: | ||
|IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400 | |IssueCategoryId=a8930ebb-8e46-4ecd-993f-cdd2d61bc400 | ||
|Content=\[WWE]\[Private Only]:The following Case Data date field options (link to doc) now also support the same configuration values as the corresponding options in Workspace Desktop Edition:* date.time-format* date.time-display-format | |Content=\[WWE]\[Private Only]:The following Case Data date field options (link to doc) now also support the same configuration values as the corresponding options in Workspace Desktop Edition:* date.time-format* date.time-display-format | ||
| − | |LocalContent=The following Case Data date field options | + | |LocalContent=The following Case Data date field options now also support the same configuration values as the corresponding options in Workspace Desktop Edition: |
*'''date.time-format''' | *'''date.time-format''' | ||
*'''date.time-display-format''' | *'''date.time-display-format''' | ||
| + | |SupportingDocumentation=[https://docs.genesys.com/Documentation/HTCC/9.0.0/IWWDep/CustomerCase Customer Case] | ||
}} | }} | ||
{{Issue | {{Issue | ||
| Line 94: | Line 97: | ||
#The reference attached data is set or updated either by the agent or as part of the interaction with non-ASCII characters that get encoded by Agent Workspace. | #The reference attached data is set or updated either by the agent or as part of the interaction with non-ASCII characters that get encoded by Agent Workspace. | ||
#Non-reference attached data is updated. | #Non-reference attached data is updated. | ||
| − | + | ||
'''For Private Edition''', previously, in the following scenario, a web application that was configured to be updated by attached data was incorrectly updated by unrelated attached data: | '''For Private Edition''', previously, in the following scenario, a web application that was configured to be updated by attached data was incorrectly updated by unrelated attached data: | ||
| Line 101: | Line 104: | ||
#The web application is configured to react in some way when the attached data was updated (that is, the value of the '''attached-data-update-handle-mode''' option is set to 1 or 2). | #The web application is configured to react in some way when the attached data was updated (that is, the value of the '''attached-data-update-handle-mode''' option is set to 1 or 2). | ||
#The reference attached data is set or updated either by the agent or as part of the interaction with non-ASCII characters that get encoded by Agent Workspace. | #The reference attached data is set or updated either by the agent or as part of the interaction with non-ASCII characters that get encoded by Agent Workspace. | ||
| − | #Non-reference attached data is updated. | + | #Non-reference attached data is updated. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 127: | Line 130: | ||
|Content=\[WWE]\[AWS]\[AZURE]:Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. Please contact Genesys to enable this behavior.\[PRIVATE]:Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. Use the privilege.chat-nexus.can-use-contact-history-detail option in the Agent or Agent Group Annex to enable this feature._Add Link to WWE PE Guide._ | |Content=\[WWE]\[AWS]\[AZURE]:Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. Please contact Genesys to enable this behavior.\[PRIVATE]:Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. Use the privilege.chat-nexus.can-use-contact-history-detail option in the Agent or Agent Group Annex to enable this feature._Add Link to WWE PE Guide._ | ||
|LocalContent=Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. Please contact Genesys to enable this behavior. | |LocalContent=Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. Please contact Genesys to enable this behavior. | ||
| − | + | ||
| − | '''For Private Edition''', use the '''privilege.chat-nexus.can-use-contact-history-detail''' option in the Agent or Agent Group Annex to enable this feature. | + | '''For Private Edition''', use the '''privilege.chat-nexus.can-use-contact-history-detail''' option in the Agent or Agent Group Annex to enable this feature. |
|SupportingDocumentation={{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Agent_Annex}} | |SupportingDocumentation={{Link-AnywhereElse|product=PEC-AS|version=Current|manual=ManageCC|topic=Agent_Annex}} | ||
}} | }} | ||
Latest revision as of 14:30, October 13, 2022
Component RN Definition[edit source]
| Component | Agent Workspace |
|---|---|
| Deployment Type | Genesys CX on AWS, Private Edition |
| Release Number | 9.0.000.98 (Change release number) |
| Release Type | |
| Highlight | Support for messages in the Contact History views for Chat, Facebook Messenger, and Twitter Direct Message interactions. |
| Boilerplate(s) Used | |
| Release Date | 2022-09-27 |
| Private Edition Release Date | 2022-09-29 |
| Mixed Mode Release ReleaseDate | |
| Private Edition Containers List |
|
| JQL | labels = "wwe-september-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 |
| WWE-1715 | New | Agent Workspace can now control which attached data keys are excluded during the creation of an inli... | email.inline-forward.exclude-case-data-keys |
| WWE-1549 | New | To better handle inline images from standard responses used as a signature, Agent Workspace now embe... | |
| WWE-766 | New | For environments using Genesys Softphone, agents who are on a consultation call can now mute and unm... | |
| WWE-126 | New | Support for Google Agent Assist for Chat interactions. Please contact Genesys to enable this feature... | Agent Assist tab |
| WWE-56 | New | Agent Workspace now supports rich messages in the Contact History views for Chat, Facebook Messenger... | Agent and Agent Group Annex |
| WWE-1749 | Resolved Issue | Agent Workspace now correctly displays the number of pending interactions in the Workbins tree when ... | |
| WWE-1665 | Resolved Issue | Agent Workspace now supports unlimited ringing time for ringtones for agent accounts that are config... | <media-type>.ringing-bell and <media-type>.auto-answer.timer |
| WWE-1612 | Resolved Issue | In the Print Preview view, after an agent opens an email interaction from the a workbin, Agent... | |
| WWE-1609 | Resolved Issue | If the list of Corporate Favorites is overridden by a strategy, the Corporate Favorites are now corr... | |
| WWE-1602 | Resolved Issue | Agent Workspace can now save changes made by agents to drop-down fields in the Case Data view ... | |
| WWE-1505 | Resolved Issue | In the History and Interaction Search views, Agent Workspace now correctly performs adva... | |
| WWE-1503 | Resolved Issue | Agent Workspace now correctly handles attachments for completed email interactions forwarded from th... | |
| WWE-1342 | Resolved Issue | Web applications associated to the interaction view in EXTERNAL, HIDDEN, or BACKGROUND mode are no l... | |
| WWE-1115 | Deprecations | Internet Explorer v11 is no longer a supported browser for Agent Workspace as it is officially retir... | |
| WWE-1540 | Private Edition | The following Case Data date field options now also support the same configuration values as the cor... | Customer Case |
Contents
Comments or questions about this documentation? Contact us for support!