Difference between revisions of "Draft: RN/DigitalChannels/100.0.147.0000"

From Genesys Documentation
Jump to: navigation, search
(Created page with "{{ComponentRN |ComponentId=074d8cb2-e6a5-4df8-97d2-d1044727c558 |JQL=project = NEXUS AND id = NEXUS-10837 or id = NEXUS-10713 or id = NEXUS-10239 |DeploymentTypeId=ec194bf2-b7...")
 
Line 11: Line 11:
 
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 
|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.
 
|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 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
 
{{Issue
Line 17: Line 17:
 
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 
|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.
 
|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 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
 
{{Issue

Revision as of 12:00, June 13, 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, Private Edition
Release Number 100.0.147.0000 (Change release number)
Release Type
Highlight Performance improvements.
Boilerplate(s) Used
Release Date 2023-06-14
Private Edition Release Date 2023-06-14
Mixed Mode Release ReleaseDate
Private Edition Containers List
JQL project = NEXUS AND id = NEXUS-10837 or id = NEXUS-10713 or id = NEXUS-10239
Links Links to customer-facing pages in use:
Test Links Links to test pages (for RN Admins only)

None yet!

No results