|
|
| Line 1: |
Line 1: |
| − | {{ComponentRN
| + | #REDIRECT [[Draft:RN/DigitalChannels/100.0.147.8795]] |
| − | |ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558
| |
| − | |JQL=project = NEXUS AND id = NEXUS-10837 or id = NEXUS-10713 or id = NEXUS-10239
| |
| − | |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
| |
| − | |ReleaseDate=2023-06-14
| |
| − | |PrivateEditionReleaseDate=2023-06-14
| |
| − | |Highlight=Performance improvements.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10837
| |
| − | |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
| |
| − | |Content=Digital Channels now enables the ability to define the customer’s time zone for the session, and will record it properly in the chat transcript in UCS. The time zone can be defined at the tenant level via option *timezone* in the *chat* section or by attaching user data key *nexus_timezone* at the session creation. Time is specified in minutes from the GMT+0 time zone (e.g., {{GMT+2 will be specified by the value 120, while GMT-5 is represented by the value -300}}.). A future enhancement will leverage this capability when emailing chat transcripts using Multicloud CX Email.
| |
| − | |LocalContent=Digital Channels now enables the ability to define the customer’s time zone for the session and records it properly in the chat transcript in UCS. The time zone can be defined at the tenant level via the '''timezone''' option in the '''chat''' section or by attaching the user data key '''nexus_timezone''' at the session creation. Time is specified in minutes from the GMT+0 time zone (For example, GMT+2 will be specified by the value 120 and GMT-5 is represented by the value -300). A future enhancement will leverage this capability when emailing chat transcripts using Multicloud CX Email.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10713
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=Memory usage by Digital Channels has been decreased significantly to improve performance. Previously, Digital Channels Core was accumulating memory over runtime but not properly releasing certain objects related to chat sessions, causing memory to grow over time.
| |
| − | |LocalContent=Memory usage by Digital Channels is decreased to improve performance. Previously, Digital Channels Core was accumulating memory over runtime but did not properly release certain objects related to chat sessions, causing the memory to increase over time.
| |
| − | }}
| |
| − | {{Issue
| |
| − | |TicketNumber=NEXUS-10239
| |
| − | |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
| |
| − | |Content=Simple Notifications are now correctly delivered to consumers on the WhatsApp channel. Previously, when an agent tried to send a Simple Notification, an error message was displayed.
| |
| − | |LocalContent=Simple Notifications are now correctly delivered to consumers on the WhatsApp channel. Previously, when an agent tried to send a Simple Notification, an error message was displayed.
| |
| − | }}
| |
This is a draft page; it has not yet been published.
