Ideas

Currently, it's only possible to add elements. Some cases require, that I want to exclude specific elements from the list. Therefore, I would like to have a "Behaviour" option to exclude the elements given to the Picklist filter.

There should be an option to restrict a group of users access to the data available in a database only to not perform manual changes, for example within a view of a report in Jedox Web / Jedox Excel Add-in. Additionally, these users should be able...

When setting up the SAML mapping using SVS scripts, it is not possible to fill the display name and email address field of the new user with the information from the active directory. Only the user name can be set. This has to be done manually aft...

Have the cloud console also in the customer infrastructure in BYOI settings. Avoid "talking home"

Define within the subset, if a drilldown is possible on a consolidated element within a picklist.

currently this is far too small, we need to login every time

For Excel export (as is already the case with PDF export) it should be possible to export multiple frames at the same time. It should behave in the same way as PDF export with frames. So "use for export" should have the same effect on the Excel e...

For spot data checks, I find it long to switch from modeler to designer, create a spreadsheet, edit the spreadsheet, create a view. I would expect a direct view from Modeler.

We have lots of groups and folders and maintenance is heavy. Each time a new group is created, we have to review almost all secured folders. My suggestion would be to manage this through cube rules.

As a customer, I would like to be able to access the SVS Editor via Administration (<CTRL>+<M>) and not under Modeler (<CTRL>+<P>). Reasons: 1. Security: ste_olap is the only way to restrict access to the SVS editor. Secur...