My ideas: Jedox Cloud

This idea is more in regards to the infrastructure, not Platform, but there's no feature request category for infrastructure. The customer wants to limit crashes to a report instead of the entire instance. That may not be possible. But, an idea co...

When an Environment is copied from one server to another e.g., LIVE to DEV. the process does not copy the passwords stored in Global Connections. If this is unavoidable for security reasons, please deactivate schedules by default. To many times I'...

Currently, cloud console users can create security rules that restrict inbound traffic, allowing connections only for the specified IP addresses or IP ranges (IP whitelisting). See also: https://knowledgebase.jedox.com/jedox/maintenance/cloud-cons...

Admins want more control over patches and upgrades that are currently automatically applied to their environments. They would like a toggle that holds off upgrades of any sort until they decide they are ready to receive the latest greatest. If a f...

Our customers often use several identity providers for user authentication. Different for different companies in the group in different countries. We would need to be able to add next providers and specify it's priority. => if user is not found...

Right now it is possible to multiselect groups to adjust user and role assignments. It would be nice, if the user settings for the groups could also be done for more groups at the same time. An use case would be to set the default report folders.

There seems to be only one global setting for the pre-shared key for all VPNs of an instance (or company VPN group of instances). This setting should be within the VPN setting and not a global setting outside. The PSK is shown in the settings of e...

Currently Jedox has no permission concept OOTB that allows the administrator to allocate a permission to models, Designer, ETL out of the box. From a security perspective this creates a loophole, as users can access things through ETL rules, that ...

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