Ideas

Currently, when downloading a dimension file, attributes are represented in all database languages, each in a dedicated column. It would be nice to have the option to include/exclude languages while exporting a dimension via the download wizard. B...

As a SuperPlänner, I want to set due dates depending on start dates, so that I don't need to enter fix dates. That would avoid potential errors and would safe time when defining the process. This idea was raised by @Marving Ludger "We see we can o...

Normally, Whether SSO is enabled or not,it is possible to activate/deactivate users in Jedox at "Administration" > "Users" or by entering "1" in "inactive" column in the relevant system cubes. But, When SSO is enabled, it may cause end-users to...

When you attempt a number that impacts many cells, Jedox give you a warning that you are potentially impacting more then you intend. It gives you the option through the Planning Assistant to modify it. However, when you delete a large number with ...

when renaming an element that is used in a rule template, the rule is not updated accordingly and must be changed manually. This would be really helpful if this could occur automatically (alternative would be a supervision server event "onRuleChan...

Sometimes the large subset option is not suitable for all users (e.g. 1 user needs it because a huge amount of elements are to be displayed, and another not) ; the possibility to make the option variable would be really helpful

The concept of Jedox models is really great to split a big EPM applicationinto different manageable modules (modularization). Example: You could have 3 different models for planning sales of products, production of products purchasing of material ...

In 2020.2 we can assign multiple users to groups, etc. Could we use the same UI gestures for multiple operations, like when adding dimension elements to a parent, rather than the right click gestures or dragging?

In Modeller group databases, cubes, dimensions by groups (e.g. all of sales in one group) --> smaller list

Currently the rules are pointed directly to a point in which it is calculated Like this where the rule is calculated for all Month_Inv, but then ignores the "~" using if. ['Cost Driver':'LB_AREA_BBR', 'Investment Measure':'Amount', 'Version':{'Sce...