Difference between revisions of "Draft: RN/DigitalChannels/100.0.143.0000"
From Genesys Documentation
| 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= | + | |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 | {{Issue | ||
| Line 68: | 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 | + | |LocalContent=Videos sent by customers through Facebook Messenger channel are now be displayed properly on the agent desktop. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 80: | Line 82: | ||
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | |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. | |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= | + | |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 | {{Issue | ||
| Line 86: | 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, | + | |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. |
}} | }} | ||
Revision as of 08:31, 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