Ideas

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

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

As a customer, I would like to be able to access the SVS Editor via Administration (<CTRL>+<M>) and not under Modeler (<CTRL>+<P>). Reasons: 1. Security: ste_olap is the only way to restrict access to the SVS editor. Secur...

Currently, user access for a model in reports and integrator projects has to be defined in different places. It would be helpful if access to a model could be granted from a single location.

The dropdown to select cube in the "Data Filter" tab of Subset Editor lists all cubes in the current database, even those which don't contain the dimension for which the subset is created. Using a cube without this dimension doesn't make sense, an...

Right now, you can only do one at a time. It would be great if there was a method to select multiple/groups of workbooks to either mark with a tag, or set resources

in #_GROUP_DIMENSION_ cube this is really complex to know what is the right for a certain group since it can be inherited from upper levels, for instance: Europe N West France R this would be great to be able to see that, say using a "flag" t...

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