All ideas

Integration with Microsoft and enhanced chat/collaboration features are asked very often by customers and prospects. With small icons in every Toolbar we would solve this requirement in an easy and very useful way.

If you have a cell in Jedox web with a data validation applied to it, and you drag the cell across a range, the data validation is applied to the other cells in the target range the references within the data validation formula are not updated. On...

We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...

it could be usefull to have a new log level "Info+" : sometimes it is useful to log informations that are relevant and that you want to catch attention to, but you do not want to cause a warning. A new method "LOG.infoPlus()" or something would be...

I want to execute an action from an hyperlink formula to delete an element and add an "Are you sure" message. I could do this with an action, but as I cannot execute actions from the hyperlink formula I have to create an additional report with the...

Goal: Show error message to the end-user without any action. Example: users can currently click on a button and execute an ETL job without selecting the correct (base) elements in the comboboxes (e.g., choosing "All cost centers" is not allowed). ...

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.

I want to restrict e.g. PALO.EL formulars for all my platform users as performance suffers from its usage. The function "Ignore order of arguments" in the individual setting section would allow for this on an individual level. But I cannot check t...