Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


Overview

Version 7.1.0.1 includes enhancements and fix 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 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 group name is displayed on eMite UI. This enhancement will assist in working around a limitation that AWS SSO currently has.


Bug Fixes

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

    • The name of the 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 displayed.

    • 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 that was causing a “No data to display” error when 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 that was resulting in a member within a Dimension appearing on the dashboard even after de-selecting it from the cube report editor.

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

  • No labels