Would like to have a way to configure a dimension block (example supervisor) so that when the criteria is selected, that a secondary filter can be associated and only show the children that are associated to the criteria in this case agents for a secondary level of filtering.

When creating a drillthrough datablock with an index search configuration of emite_awsconnectcontracttrace, the column labeled "AbandonedCall" is only reporting False even when it is an Abandoned call.

A tool, or button that allows my current research to be saved then, once saved (on another button) I can access to "My Saved Reports" so I can browse for that information, faster, on any another day.

This will help me to look for the same information, faster and more efficiently.

Ability to add week day to show as well as the date

We've been informed that there is currently a limit to only view 5,000 rows of data at a time in a cube, and only export 170,000 rows from a drillthrough in an Excel File.

Can these limits be increased so that we can see/export more rows?

The virtual index has a limitation of not allowing new index's to be added in future, meaning rework after developing the mapping and re-creating measures if you want to add a new index at a later date.

It would be better if we could add the index to an existing Virtual index. This would mean less rework and far better user experience. It will be common for new index's to become available after the initial VI was created.

With Virtual index's a common requirement is field mapping via Member groups to create common fields in order to report effectively across all combined data sets.

My Enhancement request is to include the ability in eMite to automatically suggest fields when you create the virtual index for mapping. For example, date fields, Fields which contain the same underlaying data even though the column names are different. This would reduce time and effort with a much better user experience.

It would be great to have the functionality to select more than one X-Axis at a time when creating a cube report, so that we get similar functionality to a Matrix (like in Microsoft SSRS) or an expanded Pivot Table (like in Microsoft Excel). This would allow for more detailed and spliced views and provide increased analytical value.

Add functionality for users to be able to reorder pages and page groups that have been Broadcasted

We would like the ability to alphabetically sort Member Group Labels that are created in KPI Admin --> Member Groups.

I want to filter about FR CS Group in qualityevaluationsemite cube. But I don't have the "Group" which in contained in the conditions of the virtual member FR CS Group. Is it possible to add the "Group" into qualityevaluationsemite?

We would like the front-end script of cube reports in table view to be upgraded so that field sizing and arrangements will be saved even with large datasets. Currently we can only retain our formatting with small datasets.

Working as a manager in a busy contact centre, sometimes we are completing other tasks such as admin, speaking with team members, meetings, actioning important emails etc meaning Emite is off our screen for some time. It would be really useful to be able to set a sound notification or pop up real time notification to let us know calls are waiting for instance so we can act accordingly even if completing other tasks.

Allowing simple calculations within the measures box, as per the attached image. Would be good to have addition, subtraction for a starter, so we avoid having to create too many steps in a kpi.

We would want something where the BCC or CC field can be hard coded, not something that can be free text anytime someone creates a new report schedule.

When data is exported, all values are in 'string' format even though the data is a number. This is happening only for Custom KPIs. System shall provide an option to assign appropriate data type for result of each Custom KPI

Related Jira ticket: https://jira.intersectalliance.com/browse/EMITE-4609

For any agent status data blocks based on Realtime Indexsearch Configuration, we would like to be able to see all agents immediately when the page is loaded, as opposed to now where agents will only appear when their State/Status updates.

We would like the ability to be able to see who has made updates to a KPI and what those updates were within the KPI Admin page.