Ideas

At the present time we have 1 account per customer, this would be far more straightforward if we have 1 single account, from where we could access all the instances. Moreover, if I have to open 2 consoles at the same time it will not work in the s...

At the moment as an IT Admin I am directly taken to the instance view, instead of the company view in the Jedox Console. By providing a company wide perspective we could give admins more power to debug/troubleshoot existing outages.

When presenting jedox and its splashing function to others (e.g customers), it is often very disturbing that the error notification (that appears when you forget to enter "#" in addition to a number) is very noticeable. Consequently, the presentat...

I would like to propose the ability to switch a rules to only be evaluated on demand, and having the result written back to the db for performance considerations. This could be very useful as an alternative to using integrator jobs, then these rul...

Having the ability to customize spread commands based off of a clients choosing (i.e. 4-4-5, 4-5-4, 5-4-4, or custom)? This is highly important to clients using 4-4-5 calendar in Manufacturing, health, etc. It would be nice if you could set how th...

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

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

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

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