Difference between revisions of "RN/DigitalChannels/100.0.126.4147"
From Genesys Documentation
(Published) |
(Published) |
||
| Line 2: | Line 2: | ||
|ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558 | |ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558 | ||
|JQL=issue in (NEXUS-9609, NEXUS-9337, NEXUS-9623) | |JQL=issue in (NEXUS-9609, NEXUS-9337, NEXUS-9623) | ||
| − | |DeploymentTypeId= | + | |DeploymentTypeId=577e188b-36c5-4733-86a7-e1d0d6564aff |
| − | |ReleaseDate=2022-08- | + | |ReleaseDate=2022-08-31 |
| − | |MixedModeReleaseDate=2022-08- | + | |MixedModeReleaseDate=2022-08-31 |
| − | |Highlight=Digital Channels supports | + | |Highlight=Digital Channels now supports reporting of attached user data for public social interactions. |
}} | }} | ||
{{Issue | {{Issue | ||
| Line 11: | Line 11: | ||
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72 | |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72 | ||
|Content=In new UI if media option is configured an agent will not see channel switcher buttons for not allowed channels and will not be able to create an outbound interaction for this medias | |Content=In new UI if media option is configured an agent will not see channel switcher buttons for not allowed channels and will not be able to create an outbound interaction for this medias | ||
| − | |LocalContent=Agents can now see the digital channels that were configured for them to use, and the disabled channels are no longer displayed | + | |LocalContent=Agents can now see the digital channels that were configured for them to use, and the disabled channels are no longer displayed in the channel icons at the bottom of the '''Conversation''' and '''Communication''' tabs. The agents are only able to start outbound interactions with the allowed channels. |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
}} | }} | ||
{{Issue | {{Issue | ||
| Line 27: | Line 21: | ||
<br /> | <br /> | ||
Alternatively, use the '''Digital Channels Admin''' UI to get '''Standard Responses'''. There, the issue does not exist. | Alternatively, use the '''Digital Channels Admin''' UI to get '''Standard Responses'''. There, the issue does not exist. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=NEXUS-9451 | ||
| + | |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72 | ||
| + | |Content=Digital Channels now supports the data reporting of public social interactions (Facebook public and Twitter Public messages). Previously, only private messages on Facebook and Twitter were supported. | ||
| + | |LocalContent=Digital Channels now supports the reporting of attached user data for public social interactions (for Facebook and Twitter). Previously, only private messages on Facebook and Twitter were supported. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=NEXUS-8349 | ||
| + | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
| + | |Content=\[KNOWN ISSUE]:When an agent downloads an attachment from a Twitter or Facebook message, the file name might contain caption text and have no file extension.*Workaround:* The agent can rename the attachment file and add the appropriate file extension using one of the supported file types: *.jpg, *.png, *.gif.\[Resolved Issue]Attachments in Twitter or Facebook messages are now downloaded with the complete file names and extensions. Previously, the file name might contain caption text and had no file extension. | ||
| + | |LocalContent=Attachments in Twitter and Facebook messages are now downloaded with the complete file names and extensions. Previously, the file names contained caption text and had no extension. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=NEXUS-9305 | ||
| + | |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72 | ||
| + | |LocalContent=The Nexus AI Connector now considers the Google Dialogflow CX DTMF settings. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=NEXUS-9484 | ||
| + | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1 | ||
| + | |LocalContent=Agents can now click an image in a chat interaction to expand it. Previously, when the agent had multiple interactions, the images were not expanded. | ||
| + | }} | ||
| + | {{Issue | ||
| + | |TicketNumber=NEXUS-9110 | ||
| + | |IssueCategoryId=7677e764-86f7-44e3-92bc-f13b59c71260 | ||
| + | |LocalContent='''Limitation:''' Chat interactions do not support Standard Responses consisting of HTML tags or a combination of HTML and plain texts. In chat interactions, use plain text in Standard Responses. | ||
}} | }} | ||
Revision as of 16:12, September 7, 2022
Component RN Definition[edit source]
| Component | Digital Channels |
|---|---|
| Deployment Type | Mixed mode |
| Release Number | 100.0.126.4147 (Change release number) |
| Release Type | |
| Highlight | Digital Channels now supports reporting of attached user data for public social interactions. |
| Boilerplate(s) Used | |
| Release Date | 2022-08-31 |
| Private Edition Release Date | |
| Mixed Mode Release ReleaseDate | 2022-08-31 |
| Private Edition Containers List | |
| JQL | issue in (NEXUS-9609, NEXUS-9337, NEXUS-9623) |
| Links | Links to customer-facing pages in use: |
| Test Links | Links to test pages (for RN Admins only)
None yet! |
| Issue | Issue Category | Description | SupportingDocumentation |
|---|---|---|---|
| Issue | Issue Category | Description | SupportingDocumentation |
| NEXUS-9609 | New | Agents can now see the digital channels that were configured for them to use, and the disabled chann... | |
| NEXUS-9451 | New | Digital Channels now supports the reporting of attached user data for public social interactions (fo... | |
| NEXUS-8349 | Resolved Issue | Attachments in Twitter and Facebook messages are now downloaded with the complete file names and ext... | |
| NEXUS-9484 | Resolved Issue | Agents can now click an image in a chat interaction to expand it. Previously, when the agent had mul... | |
| NEXUS-9724 | Known Issue | When a user creates a Standard Response with Rich Media templates in the Standard Responses ma... | |
| NEXUS-9110 | Known Issue | Limitation: Chat interactions do not support Standard Responses consisting of HTML tags or a c... |
Contents
Comments or questions about this documentation? Contact us for support!