My ideas: Jedox Cloud

R Script logs are not returned in the cloud log files, which is hard for debugging in case a rs transformation failed during a job execution. Those log files should be included into the log session in the cloud console.

With the security of data becoming more important, there is also a need for pseudonymizing entered data. Maybe there could be a solution from Jedox that separates sensitive data from the rest of the data (e.g. separating PIIs from the rest of the ...

VPN seems to be a problem with Jedox Cloud in many cases. Also many customers do not like it in principle. It would be helpful to have a "Jedox Connector Tool" that you could setup to run locally to get data from local systems and push them into t...

For some partners, the main contact by the Jedox Support should be the partner instead of the customer. It would be great if this contact could be chosen by the customer or partner instead of always contacting the person from the contract.

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"

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

When using custom developments on cloud, update process can be very painful since you have to update all manually using the sftp access for each environment One suggestion would be to allowing git to sync directories.

Currently we need to create a ticket for that. It would be beneficial to adjust the token via cloud console to be more flexible.

In Jedox Cloud environments with Network Restrictions (IP allowlisting) enabled, all externally exposed service endpoints should consistently enforce the same network-level access controls. Currently, certain endpoints (e.g., Web/UI and OLAP APIs)...