Ideas

Today's subset editor only lets you sort elements by one criterion (element, alias, attribute, etc.). It is often necessary to sort on several criteria, for example first on an attribute and then on the name of the element. This is not possible wi...

The user is confused, when adding a new report, or published an existing one, that the report does not show in the menu. When a user adds new reports or publishes existing ones, the user wants to get a pup-up message with a hint that the user must...

Link input cells with the existing Input Style from the stylesheet to visually highlight editable areas and enhance user guidance.

Challenge: Currently users are allowed to save/ post data to the closed periods. Eg: 2022.Dec, financial report is approved and published. Users are not supposed to alter/ change this data. However, currently in Jedox it is possible.

We have a customer who is very happy with the drill through functionality in Jedox. It pulls out all the transactions that makes up the number in the cube cell but it doesn't show the sum of all the lines. Is is possible to add the total or have i...

Buttons in "Posting Journal Entry" move to the top instead of having them at bottom. Because if there are many JEs to be posted, the user need to scroll all the way to the bottom, but the step before of selecting All JEs is at the top. Sometimes t...

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

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