Draft:RN/DigitalChannels/100.0.145.0000 - Revision history

WikiSysop: Redirected page to Draft:RN/DigitalChannels/100.0.145.8466

2023-05-10T13:30:58Z

Redirected page to Draft:RN/DigitalChannels/100.0.145.8466

Santhosh Annamalai at 06:08, May 10, 2023

2023-05-10T06:08:22Z

WikiSysop at 09:00, May 8, 2023

2023-05-08T09:00:45Z

WikiSysop: Created page with " {{ComponentRN|ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558|JQL=https://genesysjira.atlassian.net/browse/NEXUS-10817|ReleaseNumber=}}{{Issue|JiraType=Task|TicketNumber=NE..."

2023-05-08T08:30:43Z

Created page with " {{ComponentRN|ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558|JQL=https://genesysjira.atlassian.net/browse/NEXUS-10817|ReleaseNumber=}}{{Issue|JiraType=Task|TicketNumber=NE..."

New page

{{ComponentRN|ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558|JQL=https://genesysjira.atlassian.net/browse/NEXUS-10817|ReleaseNumber=}}{{Issue|JiraType=Task|TicketNumber=NEXUS-10785|LastUpdated=May 05, 2023 6:14 AM|Content=For some Digital Channels sessions, the agent or consumer could not resume the conversation in the session after a significant pause in communication (e.g. more than 3 days) due to an internal error. This issue is now fixed, and the agent or consumer will be able to resume communication in such sessions until the session is expired due to inactivity timeout. This fix applies to new sessions only.|LocalContent=For some Digital Channels sessions, the agent or consumer could not resume the conversation in the session after a significant pause in communication (e.g. more than 3 days) due to an internal error. This issue is now fixed, and the agent or consumer will be able to resume communication in such sessions until the session is expired due to inactivity timeout. This fix applies to new sessions only.|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}

← Older revision		Revision as of 13:30, May 10, 2023
Line 1:		Line 1:
−	~~{{ComponentRN~~	+	#REDIRECT [[Draft:RN/DigitalChannels/100.0.145.8466]]
−	~~\|ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558~~
−	~~\|JQL=https~~://~~genesysjira.atlassian.net/browse/NEXUS-10817~~
−	~~\|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1~~
−	~~\|ReleaseDate=2023-05-10~~
−	~~\|ReleaseNumber=~~100.0.145.~~0000~~
−	~~\|PrivateEditionReleaseDate=2023-05-10~~
−	~~\|Highlight=Security improvements as well as resolved issues related to contact subscriptions, nicknames, and image attachments.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-9624, NEXUS-10472~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	~~\|LocalContent=Security, observability, and resiliency improvements.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-10785, NEXUS-10310~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|Content=For some Digital Channels sessions, the agent or consumer could not resume the conversation in the session after a significant pause in communication (e.g. more than 3 days) due to an internal error. This issue is now fixed, and the agent or consumer will be able to resume communication in such sessions until the session is expired due to inactivity timeout. This fix applies to new sessions only.
−	\|LocalContent=Previously, in some Digital Channels sessions, the agent could not resume the conversation in the session after a significant pause in communication (for example, more than 3 days) due to an internal issue. This issue is now fixed, and the agent can now resume communication in such sessions until the session is expired due to inactivity timeout. This fix applies to new sessions only.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-10779~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=Previously, in some chat sessions, agents could not upload and send JPEG attachments. This issue is now fixed.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-10748~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=Status check marks indicating that a message is sent, delivered, and read is now shown for messages sent by a chatbot. Previously, these check marks were only visible for messages sent by agents.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-10707~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=In some cases, an agent who had already unsubscribed from a contact was receiving both the Show/Dismiss pop-up toast notification and the Accept/Reject pop-up toast notification upon an incoming Twitter or Facebook interaction, as if they were still subscribed. This issue is now fixed.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-10667~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=If a chat session is created with only a nickname provided, the session uses the nickname as the contact’s first name. Previously, the nickname was not sent to the agent desktop, so the agent desktop was displaying the contact ID (a string of characters) instead of the contact’s name.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-9851~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=Previously, the connection between Digital Channels and the agent desktop could stop working if the network gets disconnected after an agent login or during chat, due to an issue in the network connection retry logic. This issue is now fixed as the retry logic functions properly.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=NEXUS-8693~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	\|LocalContent=Previously, if an agent unsubscribed from a contact after a Twitter or Facebook public interaction, and then received a new interaction from the same contact, the agent was not subscribed to the contact again. This issue is now fixed, and the agent is now subscribed to the contact after accepting an interaction when subscriptions are enabled.
−	}}

@@ Line 4: / Line 4: @@
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1
 |ReleaseDate=2023-05-10
 |PrivateEditionReleaseDate=2023-05-10
 |Highlight=Security improvements as well as resolved issues related to contact subscriptions, nicknames, and image attachments.

@@ Line 1: / Line 1: @@
 {{ComponentRN
 |ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558
-{{ComponentRN|ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558|JQL=https://genesysjira.atlassian.net/browse/NEXUS-10817|ReleaseNumber=}}{{Issue|JiraType=Task|TicketNumber=NEXUS-10785|LastUpdated=May 05, 2023 6:14 AM|Content=For some Digital Channels sessions, the agent or consumer could not resume the conversation in the session after a significant pause in communication (e.g. more than 3 days) due to an internal error.  This issue is now fixed, and the agent or consumer will be able to resume communication in such sessions until the session is expired due to inactivity timeout. This fix applies to new sessions only.|LocalContent=For some Digital Channels sessions, the agent or consumer could not resume the conversation in the session after a significant pause in communication (e.g. more than 3 days) due to an internal error.  This issue is now fixed, and the agent or consumer will be able to resume communication in such sessions until the session is expired due to inactivity timeout. This fix applies to new sessions only.|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1}}
+|JQL=https://genesysjira.atlassian.net/browse/NEXUS-10817