Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

All ideas

Showing 987

ESG - Assign responsibilities per ESG data point

Background: In ESG reporting, ensuring data ownership and accountability is critical for transparency, audit readiness, and ongoing data quality. Currently, responsibilities for specific ESG data points are not clearly assigned within the system, ...
4 months ago in Jedox Solutions / ESG 1 Future Consideration

ESG - copy double materiality assessment to new year

Purpose: Allow users to duplicate the double materiality assessment data from one year to another (e.g., 2025 to 2026) to save time and maintain consistency, while allowing adjustments for the new year. Feature: Copy the double materiality assesss...
4 months ago in Jedox Solutions / ESG 0 Future Consideration

Subset editor, hierarchy tab: Range for element type not working/ specified

The hierarchy tab in the subset editor one can define, whether base, consolidated or both elements should be included in the selection (selections: "base", "consolidated", "none"). This setting can be linked to a range. However, passing one of the...
4 months ago in Jedox Platform / Jedox Web Navigation 0 Future Consideration

ESG - Flexible CO₂ Factor Mapping for Building Energy Consumption

Background: A customer requires the conversion of building energy consumption into CO₂ equivalents as a critical part of their emissions reporting. Proposed Idea: Introduce an additional features within the ESG solution to calculate not only for t...
4 months ago in Jedox Solutions / ESG 0 Future Consideration

Show Linked Components of ETL Jobs and Loads

ETL Jobs and Loads should display all the components that they are linked to and can be triggered by. For example, these should include scheduled jobs, and buttons in reports that reference them as actions. It would be great if the list is also al...
9 months ago in Jedox Platform / Integrator 1 Future Consideration

Hide specific databases in the modeler from users (similar to ste_palo, but per database)

Usually the ste_palo permissions can be used to control wether a user can see the Modeler in Jedox Web. However, there are cases where a user should be allowed to change a database from a report, but not from the modeler, but the same user should ...
9 months ago in Jedox Platform / Access & Rights Management 0 Future Consideration

Allow the Admin user account to be removed or deactivated in Jedox suite

Whilst you need to ensure that there is always at least 1 account that is a member of the Admin role (via a group), it does not need to be the default Admin user account that is shipped with the product. The issue is that this is a basic authentic...
over 3 years ago in Jedox Platform / Access & Rights Management 1 Future Consideration

Aggregate lists of elements for each dimension in PALO.DATA functions instead of single.

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,
about 6 years ago in Jedox Platform / In-Memory DB 3 Future Consideration

Rule Editor usability/GUI - grouping in folders

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...
about 6 years ago in Jedox Platform / In-Memory DB / Jedox Web Navigation 1 Future Consideration

Additional argument in PALO.DATA function to omit hashtag (#) sign for data splashing

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 #.
about 6 years ago in Jedox Platform / In-Memory DB 0 Future Consideration