Versions Compared

Old Version 1

changes.mady.by.user Arielle Kaye Odeste

Saved on

compared with

New Version Current

changes.mady.by.user Arielle Kaye Odeste

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: SDCM-471
Table of Contents

...

Overview

Version 7.1.0.1 (build 907) includes enhancements and fix fixes for critical bugs that were identified after the release of eMite 7.1.0.0.

...

Product Enhancements

  • Pipe character on dimensions - Values within Dimensions can now include a pipe (’|’) character. Limitation around the use of pipe symbols has been removed by replacing the underlying logic.

  • Group name on single sign-on - AWS Single Sign-On Group Name - eMite’s AWS SSO integration can now fetch the Group Name (meaningful text) instead of Group ID (system-generated alphanumeric value) during Single Sign-on so that a clear the actual group name is displayed on eMite UI. This enhancement will assist in working around a limitation that AWS SSO currently has.

Bug Fixes

...

Bug Fixes

  • Fixed an issue that was causing scrolling not to work when eMite was embedded within the Genesys Cloud UI.

  • Fixed an issue where pipe (’|’) characters within dimension values were causing issues with filtering on pages.

  • Fixed an issue that was sometimes preventing all other real-time datablocks within a page from reconnecting from an idle browser session, when a single datablock had real-time enabled, but no message group was selected.

  • Fixed an issue that was causing a discrepancy between the status datablock and drillthrough datablock when comparing records in the real-time “QueueConversations” message group.

  • Fixed an issue that was causing measures to be missing from the ‘Choose Datasource’ screen when configuring the status datablock for real-time messages.

  • Fixed an issue that was causing multiple issues if the number of records being exported from a drillthrough was if it had more than 5,000 records. The issues were:

    • The name of the Renamed columns reverted back to the original ones if they were renamed for easy reading.The number of columns in the drill through reverted back to that of the original index from a set of columns that the user had chosen to be displayedtheir original names when exported.

    • Hidden columns were being included in the export.

    • The order of columns reverted back to that of the original index from the order in which columns were arranged by the user .

  • Developed an interim fix to handle the issue reported that measures are missing from the Choose Datasource screen in the status data block for real-time messages.

  • Fixed a bug

    • were not being maintained in the export.

  • Fixed an issue that was causing a “No data to display” error when a drillthrough was linked to cube report via a comma-analyzed field.

  • Fixed a bug that was causing a discrepancy between the status datablock and drillthrough datablock when comparing records in real-time “QueueConversations” message group.Fixed a bug an issue that was resulting in a member within a Dimension dimension appearing on the dashboard even after de-selecting it from the cube report editor.

  • Fixed a bug an issue in the Filter selection of status datablock that was leading to the incorrect representation of applied filters.

  • Fixed an issue that was causing long text to not wrap within the text editor datablock.

...

Known Issues

  • The data onboarded by the Agent Activity adapter does not display data in specific cases. The root cause has been identified and a fix will be provided shortly.

  • The user experience of the hamburger menu is currently being improved.

  • Some datablocks are corrupted when upgrading from older versions to 7.1.0. This can be resolved by recreating the datablocks.

  • KPIs in older eMite versions that were using Target KPI in their definition may not work properly after upgrading to eMite 7.1.0. This can be resolved by recreating the KPI. During the upgrade, a script will be run to notify customers if there are any KPIs that need to be recreated.

  • Status data block rarely shows '0' value when configured to use RealTimeQueueStatus. This can be resolved by reloading the page.

  • “.date” property has been deprecated in the new ElasticSearch version. Virtual members with RETURN script that were using .date shall be recreated using “.value” instead of “.date”. In addition, the RETURN scripts that use “@<any fieldname>” shall be recreated.