Skip to Main Content
Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

Jedox Platform

Showing 1205

Drill-by feature rights flexibility

Our users cannot use the drill-by feature (or the new dynatable feature) because they have some restrictions on their rights within a cube - even though the rights don't affect what they would see. For example, if they can't access a legal entity,...
8 months ago in Jedox Platform / Planning & Analytics 1 Future Consideration

Remove "Session Data Missing" Warning during Login

The "Session Data Missing" warning indicates that the session cookie was not found. I don't think that it still serves a purpose and it is shown for almost every user.
over 3 years ago in Jedox Platform / Jedox Web Navigation 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...
4 months ago in Jedox Platform / Integrator 0 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...
8 months ago in Jedox Platform / In-Memory DB 0 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,
almost 6 years ago in Jedox Platform / In-Memory DB 3 Future Consideration

Add Radio Buttons in Jedox Web

Currently I used several checkboxes and macro for disable checkboxes and guarantee than only one checkbox is selected when one checkbox is selected.
almost 6 years ago in Jedox Platform / Jedox Web Navigation 2 Not Planned

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 #.
almost 6 years ago in Jedox Platform / In-Memory DB 0 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 ...
4 months ago in Jedox Platform / Access & Rights Management 0 Future Consideration

% RAM used in Cloud Console needs to note how much RAM is available

You note the RAM usage in the cloud console, but how much total RAM is available it not shown. So it is an imcoplete KPI for decision making.
over 1 year ago in Jedox Platform / Cloud Console & Administration 0 Planned

AI follow up prompts and cross cube analysis

When you have data in more than one cube, asking AI to leverage more than one cube to bring back a result is the ultimate AI concept. It would require the AI to be able to understand relations in the data and perhaps prompt with a clarification qu...
about 1 year ago in Jedox Platform / AI & Automation 0 Future Consideration