Jedox Ideas

Let us know how we can make Jedox even better!

ADD A NEW IDEA

All ideas

Showing 1233

Dynamic implementation of report rights by Integrator

As an implementation expert or power user I would like to define which user group gets access to which report. Example: admin gets rights to all 30 reports, planner gets access to 20 reports and viewer gets access to 5 reports. Currently it is pos...
about 2 years ago in Jedox Best Practice Accelerator (BPA) / Foundation 0 Future Consideration

Replace the very noticeable splashing error notification with a more subtle error notification

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

"Offline" input template

In the future I would like to se the ability to use Jedox input templates in a mode, where the user needs to press a save button before uploading plan changes. Currently Jedox very aggressively sends all inputs back to the server for each input, b...
about 4 years ago in Jedox Platform / Jedox Web Navigation 0 Future Consideration

Offline rules

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

Hide ETL projects in Integrator if (reading) access is only granted with non-Integrator group

When a user is assigned to groups with different roles, where one role (e.g. designer) has access to Integrator and another (e.g. editor) has only access to reports, rights for ETL projects are “combined”. E.g. the group with access to Integrator ...
about 2 years ago in Jedox Platform / Jedox Web Navigation 0 Future Consideration

Hide Reports in Designer if (reading) access is only granted with non-Designer group

When a user is assigned to groups with different roles, where one role (e.g. designer) has access to Designer and another (e.g. editor) has only access to Reports section, rights for folder groups / reports are “combined”. E.g. the group with acce...
about 2 years ago in Jedox Platform / Jedox Web Navigation 0 Future Consideration

New Subset option: Show all missing parents/ancestors up to root level

When filtering e.g. by free text name or attribute, it's very typical that the result might only show base elements or elements from different levels. In dimensions, consolidated elements (i.e. parents/ancestors) usually provide additional, useful...
about 2 years ago in Jedox Platform / Jedox Web Navigation 0 Future Consideration

Better user management in the ODATA HUB

The possibilities to influence user authorisation in the ODATA Hub are currently very limited. When it comes to integrating Jedox into an existing data architecture, the ODATA Hub with the REST interface is a good option. However, it is currently ...
about 2 years ago in Jedox Platform / OData Hub & Power Platform Connector 2 Future Consideration

Stronger authentication in the ODATA HUB

In the enterprise environment, the Basic Auth in the ODATA Hub is not sufficient and it becomes necessary to use stronger authentication methods. A best practice here would be the additional authentication with a client certificate.
about 2 years ago in Jedox Platform / OData Hub & Power Platform Connector 0 Future Consideration

Splashing command withrules by default

In splashing command like "copy", the default is "norules". If I want to take rule-based values into account I have to explicitly specify "withrules": copy Actual;2018 withrules This is difficult to understand for end users. I would be able to cha...
about 2 years ago in Jedox Platform / Jedox Web Navigation 1 Future Consideration