Ideas

Scenario:There is a long running ETL job and the Jedox server or part of services went down or "crashes". After the (re-)start of the components/services the ETL jobs are marked as failed or aborted. Here there is need for a feature or a new optio...

Introduce a native Jedox connector for Xero, enabling connection and extraction of key financial data like Trial Balance, Aged Payables, Journals, and other standard reports. Encryption and OAuth 2.0 authentication to comply with Xero's security s...

We have a customer who is very happy with the drill through functionality in Jedox. It pulls out all the transactions that makes up the number in the cube cell but it doesn't show the sum of all the lines. Is is possible to add the total or have i...

Integrator: Enable writeback via load for JDBC connections Users expect that writeback is also supported by JDBC connections.

The current REST Connector only supports one connection setup from JEDOX -> Server. This means that each accessing server must first open an incoming port. When an incoming port is opened, further steps must be initiated to secure the server. T...

Buttons in "Posting Journal Entry" move to the top instead of having them at bottom. Because if there are many JEs to be posted, the user need to scroll all the way to the bottom, but the step before of selecting All JEs is at the top. Sometimes t...

We are using various rules and sometimes they have to be properly sorted afterwards. It would make the handling easier, if the rules can be sorted via drag and drop option rather than having to click 15 times on the sort arrow on the right side. I...

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,

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

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