Difference between revisions of "Draft: RN/DigitalChannels/100.0.143.0000"
From Genesys Documentation
| Line 42: | 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 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 | + | |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'', they were able to send messages from the Communication tab to 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 | + | If the option is set to ''false'', the message send bar will only be hidden from the agent. To allow agents to send chat messages, this option should be set to ''true''. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 56: | Line 56: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |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. | |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, | + | |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, 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. | 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. | ||
| Line 70: | Line 70: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |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. | |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 | + | |LocalContent=Videos sent by customers through the Facebook Messenger channel are now displayed properly on the agent desktop. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 88: | Line 88: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |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) | |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 | + | |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. Only the agent who is directly handling the interaction with the consumer will be subscribed to the contact if subscriptions are enabled. |
}} | }} | ||
Revision as of 05:00, April 12, 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