Recently I have seen a lot more requirements for traceability of calculations for users. i.e. easy abiliy to understand how a value was calculated. This is coming up as a 'critical' requirement in functional requirements quite often. I know we hav...
Drillthrough decimal symbol same as on screen/report
Decimal symbols are currently linked to the user-locale. English setting will give a dot (.) as decimal symbol whereas the Dutch setting, for example, will give a comma (,)
This feature works on the screens/reports, but this does not happen wit...
Better calculation stack when tracing a rule calculated cell with overlapping rules
In complex planning situations, separate rules calculating identical cube areas are required, using CONTINUE and STET statements. This has the advantage of separating out logic branches to make calculations easier to read in the Rules Editor in Mo...
Validate element name with 2 or more consecutive space characters
According to the Knowledgebase element names with 2+ following spaces are not allowed. However, the creation of these elements still work. Only when using the elements in the Spreadsheet, strange issues appear. For example the default element is u...
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...
Whe you have a lot of attributes in an dimension, you always have to scroll to the right to maintain all attributes. But as the first column (element name) is not fixed, the element names get out of the screen. So you always loose the link between...
Add an attribute to the time dimension to categorize dimension element (year, month, day)
Everything is in the title, but for some specification here's the complete idea : What ? Add an attribute "Category" or "TimeType" that categorize element in the dimension. So for element like : 2022-01-01 or 2023-05-01 the attribute should have t...
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 #.
Possibility to splash a string to aggregated cell so every base cell will have the same string afterwards. Practically this would mean adding support for splashing strings via splash operation ! and also adding support for copy operation with stri...
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 hav...