Difference between revisions of "Draft: RN/DigitalChannels/100.0.143.0000"

From Genesys Documentation
Jump to: navigation, search
(Created page with "{{ComponentRN |ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558 |JQL=issue in (NEXUS-10534, NEXUS-10622, NEXUS-10702, NEXUS-8097, NEXUS-9813, NEXUS-10585, NEXUS-10637, NEXUS-1...")
 
Line 10: Line 10:
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|Content=When an agent hovers a mouse over the status checkmark next to a message, the time of delivery receipt and/or read receipt will now be shown in the tooltip text.  Note: Delivery receipts are only available for WhatsApp and SMS channels, and read receipts are only available for the WhatsApp channel. 
 
|Content=When an agent hovers a mouse over the status checkmark next to a message, the time of delivery receipt and/or read receipt will now be shown in the tooltip text.  Note: Delivery receipts are only available for WhatsApp and SMS channels, and read receipts are only available for the WhatsApp channel. 
−
|LocalContent=When an agent hovers a mouse over the status checkmark next to a message, the time of delivery receipt and/or read receipt will now be shown in the tooltip text.  Note: Delivery receipts are only available for WhatsApp and SMS channels, and read receipts are only available for the WhatsApp channel. 
+
|LocalContent=When an agent hovers over the status checkmark next to a message, the tooltip text will now display the time of delivery receipt and/or read receipt.  
 +
 
 +
'''Note''': Delivery receipts are only available for WhatsApp and SMS channels, while read receipts are only available for the WhatsApp channel.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 16: Line 18:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=For WhatsApp interactions, the read receipt checkmark indicator is now displayed in blue.  Previously, the read checkmark and the delivery checkmark were not distinguishable because they were both gray.
 
|Content=For WhatsApp interactions, the read receipt checkmark indicator is now displayed in blue.  Previously, the read checkmark and the delivery checkmark were not distinguishable because they were both gray.
−
|LocalContent=For WhatsApp interactions, the read receipt checkmark indicator is now displayed in blue. Previously, the read checkmark and the delivery checkmark were not distinguishable because they were both gray.
+
|LocalContent=For WhatsApp interactions, the read receipt checkmark indicator is now displayed in blue, distinguishing it from the delivery checkmark, which remains gray. Previously, both the read checkmark and the delivery checkmark were gray, making them indistinguishable.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 22: Line 24:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=The active interaction indicator is now accurately hidden on the Communication tab when the interaction is not active.  Previously, when an agent unsubscribed from a contact during an interaction, completed the interaction, and then searched for the same contact, the active interaction indicator was still displayed next to the contact name in the Communication tab.  In addition, the creation of an outbound interaction failed in this case.  These issues are now resolved.  
 
|Content=The active interaction indicator is now accurately hidden on the Communication tab when the interaction is not active.  Previously, when an agent unsubscribed from a contact during an interaction, completed the interaction, and then searched for the same contact, the active interaction indicator was still displayed next to the contact name in the Communication tab.  In addition, the creation of an outbound interaction failed in this case.  These issues are now resolved.  
−
|LocalContent=The active interaction indicator is now accurately hidden on the Communication tab when the interaction is not active.  Previously, when an agent unsubscribed from a contact during an interaction, completed the interaction, and then searched for the same contact, the active interaction indicator was still displayed next to the contact name in the Communication tab.  In addition, the creation of an outbound interaction failed in this case.  These issues are now resolved.  
+
|LocalContent=The active interaction indicator will no longer be displayed next to the contact name in the '''Communication''' tab when the interaction is not active. Previously, if an agent unsubscribed from a contact during an interaction, completed the interaction, and searched for the same contact again, the active interaction indicator would still be displayed next to the contact name. This caused the creation of an outbound interaction to fail.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 28: Line 30:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=The URL verification button under the chat conversation window is now disabled unless a URL is entered into the chat input field.  Previously, the button was clickable and opened a blank window.
 
|Content=The URL verification button under the chat conversation window is now disabled unless a URL is entered into the chat input field.  Previously, the button was clickable and opened a blank window.
−
|LocalContent=The URL verification button under the chat conversation window is now disabled unless a URL is entered into the chat input field. Previously, the button was clickable and opened a blank window.
+
|LocalContent=The URL verification button under the chat conversation window is now disabled when there is no URL entered in the chat input field. Previously, the button was clickable and opened a blank window.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 40: Line 42:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=Previously, when the latest version of the Advanced Chat UI is enabled in agent desktop and the option {{privilege.chat-nexus.communication.can-send}} was set to *false* or *not set* an agent wasn’t able to send messages not only from Communication tab as expected, but from chant interaction view. This issue has been fixed.  If the option is set to *false*, the message send bar will be hidden from the agent only in Communication view.  To allow agents to send chat messages from Communication tab this option should be set to *true*.
 
|Content=Previously, when the latest version of the Advanced Chat UI is enabled in agent desktop and the option {{privilege.chat-nexus.communication.can-send}} was set to *false* or *not set* an agent wasn’t able to send messages not only from Communication tab as expected, but from chant interaction view. This issue has been fixed.  If the option is set to *false*, the message send bar will be hidden from the agent only in Communication view.  To allow agents to send chat messages from Communication tab this option should be set to *true*.
−
|LocalContent=Previously, when the latest version of the Advanced Chat UI is enabled in agent desktop and the option {{privilege.chat-nexus.communication.can-send}} was set to *false* or *not set* an agent wasn’t able to send messages not only from Communication tab as expected, but from chant interaction view. This issue has been fixed.  If the option is set to *false*, the message send bar will be hidden from the agent only in Communication view.  To allow agents to send chat messages from Communication tab this option should be set to *true*.
+
|LocalContent=Previously, when agents used the latest version of the Advanced Chat UI and the option <code>privilege.chat-nexus.communication.can-send</code> was set to ''false'' or ''not set'', they were unable to send messages not only from the Communication tab but also from the chat interaction view. This issue has been fixed.  
 +
 
 +
If the option is set to ''false'', the message send bar will only be hidden from the agent in the Communication tab. To allow agents to send chat messages from the Communication tab, this option should be set to ''true''.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 46: Line 50:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|Content=Previously, the markdown editor button disappeared when an agent switched from a Chat interaction to an SMS interaction and then back to Chat. This has been resolved.
 
|Content=Previously, the markdown editor button disappeared when an agent switched from a Chat interaction to an SMS interaction and then back to Chat. This has been resolved.
−
|LocalContent=Previously, the markdown editor button disappeared when an agent switched from a Chat interaction to an SMS interaction and then back to Chat. This has been resolved.
+
|LocalContent=The markdown editor button no longer disappears when an agent switches from a Chat interaction to an SMS interaction and then back to Chat.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 58: Line 62:
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|Content=During an SMS interaction, an agent can now hover a mouse over the character counter for a tooltip explaining how the counter works.
 
|Content=During an SMS interaction, an agent can now hover a mouse over the character counter for a tooltip explaining how the counter works.
−
|LocalContent=During an SMS interaction, an agent can now hover a mouse over the character counter for a tooltip explaining how the counter works.
+
|LocalContent=During an SMS interaction, agents can now hover over the character counter to display a tooltip explaining how the counter works.
 
}}
 
}}
 
{{Issue
 
{{Issue
Line 70: Line 74:
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|Content=When a Digital Channels message fails to send, an agent can now mouse over the error message to view more details on the reason for failure.
 
|Content=When a Digital Channels message fails to send, an agent can now mouse over the error message to view more details on the reason for failure.
−
|LocalContent=When a Digital Channels message fails to send, an agent can now mouse over the error message to view more details on the reason for failure.
+
|LocalContent=In Digital Channels, when a message fails to send, agents can now hover over the error message to view more details on the reason for failure.
 
}}
 
}}
 
{{Issue
 
{{Issue

Revision as of 08:01, April 3, 2023

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

Component RN Definition[edit source]

Component Digital Channels
Deployment Type Genesys CX on AWS, Genesys CX on Azure
Release Number 100.0.143.0000 (Change release number)
Release Type
Highlight New tooltip explanations and fixes in the agent interface.
Boilerplate(s) Used
Release Date 2023-04-12
Private Edition Release Date
Mixed Mode Release ReleaseDate
Private Edition Containers List
JQL issue in (NEXUS-10534, NEXUS-10622, NEXUS-10702, NEXUS-8097, NEXUS-9813, NEXUS-10585, NEXUS-10637, NEXUS-10652, NEXUS-10654, NEXUS-10676, NEXUS-10677, NEXUS-10678,NEXUS-10698)
Links Links to customer-facing pages in use:
Test Links Links to test pages (for RN Admins only)

None yet!

No results

Retrieved from "https://all.docs.genesys.com/Draft:RN/DigitalChannels/100.0.143.0000 (2025-07-20 14:17:14)"