Ideas

We have clients who archive previous databases from prior years (but these are still saved on the Jedox server so they can access the database if needed). By default, Jedox loads all databases into memory at server startup. This means the inactive...

Dear Jedox, I believe it is very useful to access the log files within the integrator. However, accessing the log files is no longer possible due to Kubernetes infra. It would be nice to have an alternative. Would it be possible to create an API f...

Recently, we introduced a password policy for users. On the platform itself nowhere is explained how the policy should look like. Users need to google or check in KB for that information. It could be a small display below or icon "i" where on the ...

It is desired that after a new user has been created by the admin with a default password, the corresponding user is forced to enter a new password. Gladly with the desired password complexity from https://feedback.jedox.com/ideas/JS-I-462

Adding a description field to the Database would allow better documentation of the type of data in the database. Dimension and Cube descriptors are helpful, and this would enhance the documentation. Tags would also be useful (like Dimension "Type"...

Challenge: Currently users are allowed to save/ post data to the closed periods. Eg: 2022.Dec, financial report is approved and published. Users are not supposed to alter/ change this data. However, currently in Jedox it is possible.

You note the RAM usage in the cloud console, but how much total RAM is available it not shown. So it is an imcoplete KPI for decision making.

We need to understand how many Cores are avilable to get any use out of the CPU usage KPI. 70 % usage on two core is a lot different from 70% usage of 16 core.

Currently it is possible to use multiple hierarchy filters in a subset formula to present multiple hierarchies (e.g. show two of 4 nodes from second level in a dimension). If the hierarchy filter instead would allow for an array of elements, this ...

A simple and understandable password validation at the create user dialog would make the process more understandable and there would be no need for unnecessary and annoying hint dialogs.