Ideas

Currently rules are calculated in the moment when the user queries the data. It would be great to have the option to shift the timing to the point when the user changes data. So the result of the calculation would be stored/persisted when the use...

Macros assigned to filter-comboboxes (to set dynarange-variables) are executed BEFORE data is updated. A function similar to __open() that is triggered after palo-data has been changed, e.g. in dynaranges, would allow macro-treatment of the new ...

In the case of bar line chart etc. Sometimes the labels of the first chart and the labels of the second chart overlap. Therefore, I want a function that automatically adjusts the position so that they do not overlap.

In Modeler in dimension attribut e.g. "Name" should be shown for multiple languages by default or based on selection & activate search functionality. Use case: Currently as a user I need to select each time I open the dimension the Name German...

Currently: Language selection is currently based on the Jedox system. Use case A: Jedox is available for e.g. Korean language, but the build application has only translations for English or German. In that case currently a workaorund need to check...

All actions should have the possibility to have an optional return code/description to provide information about the execution. This could then be sent to a variable/named range/range to be processed in a subsequent action. This effectively allows...

A new (sample) svs script that drills not to the drillthrough dialog, but to an external website, with parameters passed from the intersection in the cube. When executing a drillthrough, a redirection to an external website like Salesforce should ...

This action could be a standalone action, or an extension to the Read/Write Action. Instead of a single number and one set of coordinates, the user can specify multiple coordinates and values. The dialog would be grouped by "Values", similar to th...

Ability to undo an entry in a cube from audit log / drill history. This option should only be available for admin users. The "undo" action may not always have been activated before entering data that someone wants to undo. If there was an option f...

If a function name in a FieldTransform is changed, it should be automatically updated in other functions it is used in. Perhaps it should also be updated in the Input Column of the Target-Area and following transforms.