Ideas

Challenge: - Users has to cpature additional data set in historic LC using cutom paste view, beyond financial statements in LC

In the report of "Scope of Consolidation" -> Tab "Scope", currently all the Partner Entities are shown for the setting, regardless of which Scope is selected. If there are many Partner Entities in System, the list will be very long and difficul...

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

current design, the Journal Entry list has to be uploaded in Report Designer, and then be loaded to Model by going back to Report, entering the file name and click on load Journal Entry. it's not user freindly. Sometimes due to User Right Restrict...

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.

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

Please add a documentation on how to add an additional dimension. Which reports need to be adjusted? Which Integrator processes? Which rules? The documentation would help to enhance the solution for customers faster.

Today's subset editor only lets you sort elements by one criterion (element, alias, attribute, etc.). It is often necessary to sort on several criteria, for example first on an attribute and then on the name of the element. This is not possible wi...