Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Clear

In-Memory DB

Rule Debugger/Impact Analysis Tool

It would be useful to have a rule debugging feature in the platform, rather than having to go to ' Browser.Live.{Client}.Jedox.com'. The browser feature is useful to identify rules that are most impactful on performance, but having it only accessa...
over 1 year ago in Jedox Platform / In-Memory DB Future Consideration

New Role for administration and editing of SupervisionServer SVS needed

A customer needs a new role, so that the OLAP Admins with full access to ste_palo can limit the access to the svs Editor in Jedox Suite!suggestion: ste_svs Full Access SVS Editor is available No Access SVS Editor is disabled, even if ste_palo is set
over 1 year ago in Jedox Platform / Access & Rights Management / In-Memory DB Future Consideration

Security mechanism to avoid system crashes

Triggering a cube extract with a lot of rule-based values inside of it leads to a platform crash (in-memory DB exceedes max amount). A mechanism the stops the action instead of letting the action crash the system would be great. The platform shoul...
over 1 year ago in Jedox Platform / In-Memory DB Future Consideration

Data Filter, extended zero suppression.

It would be very helpful to have the following filter option in the subset data filter. A filter option that displays all parent elements as soon as at least one child element has a value, even if the parent elements themselves are zero. (please s...
over 1 year ago in Jedox Platform / In-Memory DB / Planning & Analytics Future Consideration

SVS new Parameter for sep_error needed to show warnings or info messages without cancelling the writeback

Situation: we would like to inform the users about specific input fields and value combinations to be informed about possible mistake (value sign wrong or wrong range). sep_error(title,msg); Allthough the value has been written to the cube prior t...
over 1 year ago in Jedox Platform / In-Memory DB Future Consideration

To enable users to lock data at month and version dimension for fincon model

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...
over 1 year ago in Jedox Platform / In-Memory DB Future Consideration

Data/ Period Locking

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.
over 1 year ago in Jedox Platform / In-Memory DB / Planning & Analytics Planned

Holds need to be easier to see

It would be very useful to have an icon or other indication which cells are being held with a Hold Statement. Currently Doohickey's/Dept 1 is being held (highlighted in Yellow), but there is not a way to determine that from visually looking. Worse...
over 1 year ago in Jedox Platform / In-Memory DB / Planning & Analytics Future Consideration

In a cube with persisted relational ETL drillthrough data, allow cube-drilldown in areas where no relational data is available.

As of version 2023.4, the Jedox drillthrough capabilities have become a native functionality outside of the SVS scripts. In the KB it says for the mode automatic: drills through if ETL is available, or else drills down. This suggest that right-cli...
over 1 year ago in Jedox Platform / In-Memory DB Future Consideration

Modification for Actual Months rule template

From https://knowledgebase.jedox.com/jedox/in-memory-db/rule-templates-query-types.htm, Actual Months rule template, "If fiscal year is used, it returns a list of the first months of each fiscal year." The partner wants the rule template to give t...
almost 2 years ago in Jedox Platform / In-Memory DB Future Consideration