Ideas

When creating a new dimension, or cube, in Modeler, and using one of the available templates, the "Description" for this new object is ignored (it can be set afterwards in the dimension / cube properties). It would be more feasible if the user cou...

In integrator it would be very helpful to be able to see the variables that are used in an integrator process in the FlowGraph. This could be shown in each job/load or even next to each integrator step in the FlowGraph. This gives you a better ove...

The navigation history (back/forward) within Jedox Web would benefit from several improvements. It would be nice if the location of back/forward would be shown in the mouseover instead of generic "Back" and "Forward" (e.g. "Report Designer > De...

The customer wants to see in the Administration -> Licenses, the date and time when the license has been created to track the validity.

In HFM you could when loading data, set a setting they called replace by security. Basically what it did, was to use security settings to determined how to replace data. This way you could load data, and have the settings determine how to overwrit...

To speed up filling out header parameters in Rest Connection and avoid typos, it would be good to have already predefined list of known headers, e.g. Accept, Accept-Encoding, Authorization, Content-Type etc. To make it more flexible we can remain ...

when using a variable set by a groovy script, the variable is initialized when the job or load is executed, not when it is needed in the flow of the job. this is a problem when using tokens for APIs whose validity is limited in time. The token is ...

Experienced Jedox model builders often write rules without using the rule editor, but by typing the rule formula directly into the formula field. When opening (existing) complex rules it can cause long waiting times while the rule editor "translat...

This new function will allow to change the value of variable during an ETL job. We can already do it in groovy but could be interesting to implement it directly in fieldtransform function or as a component type

Currently Jedox determines text direction based on the first character. Meaning that if text starts with a Latin character and is followed by, for example, hebrew letters the Right-to-Left Alignment is not applied.