Ideas

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...

The customer would like to use Token-Based Authentication for JDBC connection (NetSuite in this case) in addition to the User name and Password currently supported. As per Knowledge Base article https://knowledgebase.jedox.com/integration/connecti...

Sometimes SVS Scripts are using Subsets for the definition of InitCubeWorker functions. These will result in an error if the database has a loading delay. Therefore, the SVS will not start and users can't log in anymore. We need a function that we...

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...

It would be useful to allow a quick swap of To and From instead of manually recreating them.

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've been utilizing the OData Hub in a similar way to our previous use of etlclient.bat / etlclient.sh. Successfully, we are able to initiate a job and receive a status update, such as "Completed successfully". However, we're seeking a method to ...

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...

Create a new load type that allows writing to log files custom messages. Currently possible with LOG.info and a groovy script job. It would be better if groovy jobs were not required.