Overview

Nectar DXP is Nectar's secure public cloud infrastructure on Amazon Web Services (AWS). Nectar cloud services can be found at:

• us.nectar.services
• eu.nectar.services

Technical Notes

If you are using Foundation APM, release 2021.3 must be installed prior installing Nectar DXP. For more information, contact Nectar Support.

Important Note for Nectar DXP API Users:

The format for authenticating with the Nectar DXP API has changed in this release. From 1.16.0 onwards, authentication must be done using an Basic Authorization header that encapsulates the username and password in Base64 format. The format must follow this convention:

• Key = 'Authorization'
• Value = 'Basic '+ base 64 encoding of a user ID and password separated by a colon

Example:

1. Username: tferguson@nectarcorp.com  Password: VeryStrongPassword!!!
2. Username/Password separated by colon:  tferguson@nectarcorp.com:VeryStrongPassword!!!
3. Encoded to Base64: dGZlcmd1c29uQG5lY3RhcmNvcnAuY29tOlZlcnlTdHJvbmdQYXNzd29yZCEhIQ==
4. Final auth header value:  "Basic dGZlcmd1c29uQG5lY3RhcmNvcnAuY29tOlZlcnlTdHJvbmdQYXNzd29yZCEhIQ=="

The authorization header must be included with every API call.

Nectar DXP PowerShell Module Users

If you use the Nectar DXP PowerShell module, you must upgrade to version 3.83 or later. To upgrade, type:

Upgrade-Module Nectar10

or if you installed the module as CurrentUser:

Upgrade-Module Nectar10 -Scope CurrentUser

New Features

1. Avaya:
   • Added Avaya CDR/CDS time-zone offset for multiple Avaya systems in a single RIG.
   • Introduced a new insight called "Poor call quality caused by Network".
2. Analytics:
   • Added the ability to cancel report processing.
   • Added a response code filter to the Quality Details widget.
   • Changed Tenant field to be visibility only for admin roles during template creation.
   • Removed redundant 'Report' from the Report type field in the wizard.
   • Changed the template wizard 'Tenant' field to default to none selected.
   • Reports and Templates default type will be set to 'User' in their respective wizards.
   • New "Self-Service" admin roles introduced.
3. Conversation Journey View:
   • Admin:
     • Added "Conversation Journey" option in session type under the Alerts and Notifications screen.
     • Added the ability to rebuild/update the stitching in the Admin → Advanced Configuration → Data Mart screen.
   • Avaya, Nectar Diagnostics session Details now have an added "View Journey" button.
   • Analytics:
     • Updated the logic in Analytics (Report/Templates) to support filtering by “Conversation Journey” the session type.
   • Call Details Page (Historic):
     • Introduced a new session type called "Conversation Journey".
     • Populated Insights: Session list and per Card based on the info from the legs.
     • Populated Insights per leg by hovering over the insight counter (tooltip).
     • Created new process for stitching Avaya and Diagnostic datasets, with storing results(conversation journey level).
     • Introduced a generation "Nectar id"(group level).
     • Introduced a new "Agent" insight type based on information from Legs.
     • Populated data from conversation journey "session" into corresponding components (Sessions, Quality).
     • Session list:
       • Included 'conversation journey ' into session list data sets.
       • Populated "Modality" column and support corresponding filter.
       • Populated "Server" column and support corresponding filter.
       • Populated "Response" column and support corresponding filter.
       • Added the ability to navigate the user to the Conversation Journey.
   • Conversation Journey Page:
     • Introduced "Cards" (Avaya, Nectar Diagnostics) review legs details.
     • Introduced new functions to populate conversation journey page: Summary, Legs Summary and Conversation timeline.
     • Navigate the user to the particular session (Avaya Nectar Diagnostics).
     • Populate "Conversation journey" concept to stand-alone Avaya Aura CM sessions.
     • Legs Summary: Introduce "Cards" (Avaya, Nectar Diagnostics) review legs details.
     • Conversation timeline: Distribute legs through time.
     • Summary: Introduced new component with general info.
   • Summary: Populated data from conversation journey "session" into corresponding components (Sessions, Quality, Locations)
   • User Overview: Page adaptation: Introduce the ability to filter by "Conversation Journey".
4. Events: Current/Historic Events components: switch source to optimize
5. New Global filters:
   • Analytics: Response Code filter: Call Details Historic Widgets: Align grouping logic
   • Call Details: Historic/User Overview: Response Code filter: Combine options to one list (except Cisco)
   • Session type: Code refactoring for "All" selected case
   • Response Code: Added code description into the session list
   • Quality Details: Added "Response" code filter and Corresponding column to the session list
6. Added an option to disable event acknowledgement to the RIG
7. MS Teams:
   • Admin: Data Source configuration: Teams: Provide option in Teams configuration to enable loading of devices
   • Add Teams audio/video codec/ freeze duration, etc. information to Call Details Advanced screen
8. Nectar Score: Session/Session list: Revise logic of color coding through DXP
9. Portal SSO authentication:
   • Added SSO support for Super Admins
   • We now allow users to create, and use personal API access tokens for API authentication instead of basic auth (backend)
   • Changed the default unsuccessful login attempts for lockout to 5 for user logins.

Improvements

1. Analytics:
   • Analytics: SLA widget: Improve data formatting approach for SLA values
2. Nectar Diagnostics: Improve stitching Avaya/Cisco and ND sessions to cover sessions with participants
3. UI/UX improvements:
   • Nectar Diagnostics icon update
   • Update of the Icons Hovering Pattern
   • Components colors update
   • Dashboards: Section Redesign (move Cisco Under "Platforms "section)

Bug Fixes

1. 404 Error page appears on redirecting to User Overview page
2. Admin. Data source configuration. RIG DB configuration could not be updated
3. Analytics:
   • Audit Log: 'Data_Source' is marked as a resource for Analytics records
   • FireFox browser: Create Report wizard layout corrupted under FF browser
4. Cluster view: Nectar Integration screen: Events counter is not displayed
5. Filters: All users are checked in 'Users/Endpoint' filter if only one is selected
6. Service Provider users: EULA not loaded due to 403 error
7. User Overview. Cisco WebEx: Endpoint Client platform is not appearing in user information card