|
|
| (3 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | {{ComponentRN
| + | #REDIRECT [[Draft:RN/DigitalChannels/100.0.143.8169]] |
| − | |ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558
| |
| − | |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)
| |
| − | |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
| |
| − | |ReleaseDate=2023-04-12
| |
| − | |Highlight=New tooltip explanations and fixes in the agent interface.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10702
| |
| − | |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.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-10698
| |
| − | |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.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-10678
| |
| − | |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.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-10677
| |
| − | |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.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-10676
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=CX Contact users are now able to send test SMS messages. Previously, the “Send Test SMS” button would not work in certain cases because the message ID was undefined.
| |
| − | |LocalContent=CX Contact users are now able to send test SMS messages. Previously, the “Send Test SMS” button would not work in certain cases because the message ID was undefined.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10654
| |
| − | |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*.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-10652
| |
| − | |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.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-10637
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=When a chat session is created without any contact attributes, the contact will still be created. Previously, contact creation was skipped when no contact attributes were provided to create or find a contact. This caused issues with how Digital Channels serviced that interaction. Now the behavior has been changed so that an “empty” contact will be created with a unique contact ID and associated with the chat session even if no contact attributes are provided. It is still recommended that customers require their end consumers to provide some contact information when starting a chat session. It is not possible to re-associate the chat session with a different contact, although agents can edit created contacts if is allowed by assigned permissions.
| |
| − | |LocalContent=If a chat session is started without any contact attributes, an empty contact is created with a unique contact ID and associated with the chat session, ensuring that the chat session is properly tracked and managed. Previously, a contact creation was skipped when no contact attributes were provided to create or find a contact. This caused issues with how Digital Channels handled that interaction.
| |
| − | | |
| − | It is still recommended that customers require their end consumers to provide some contact information when starting a chat session. It is not possible to re-associate the chat session with a different contact, although agents can edit created contacts if they have the required permissions.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10622
| |
| − | |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.
| |
| − | |LocalContent=During an SMS interaction, agents can now hover over the character counter to display a tooltip explaining how the counter works.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10585
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=Videos sent by customers via the Facebook Messenger channel were not displayed in the agent desktop properly. This is now resolved.
| |
| − | |LocalContent=Videos sent by customers through Facebook Messenger channel are now be displayed properly on the agent desktop.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10534
| |
| − | |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.
| |
| − | |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
| |
| − | |TicketNumber=NEXUS-9813
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=In some cases, an agent would unsubscribe from a contact but still receive notifications as if subscribed and the contact would show up again in the Communications tab after logout/login. This issue has been fixed.
| |
| − | |LocalContent=Agents previously encountered an issue where they would unsubscribe from a contact, but still receive notifications as if they were subscribed, and the contact would reappear in the '''Communications''' tab after logging out and logging back in. This issue has now been fixed.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-8097
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=Previously, if a contact subscription is allowed agent will be subscribed to contact when accept a consultation chat from another agent. The behavior has been changed, agent is no longer subscribed to contact when engaged in consultation, only the agent who is handling interaction with consumer if subscribed (if subscription is not disabled)
| |
| − | |LocalContent=Previously, agents were automatically subscribed to a contact when they accepted a consultation chat from another agent. This behavior has been changed so that agents are no longer subscribed to the contact during a consultation chat, unless contact subscription is not disabled. Only the agent who is directly handling the interaction with the consumer will be subscribed to the contact.
| |
| − | }}
| |
This is a draft page; it has not yet been published.
