Ideas

Even if element names are all short it is not possible to reduce the column width of the column Element in the dimension editor of the Modeler according to the element names because there seems to be a minimal width for that column. This minimal c...

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

Integration with Microsoft and enhanced chat/collaboration features are asked very often by customers and prospects. With small icons in every Toolbar we would solve this requirement in an easy and very useful way.

When you mark a cell as Writable in a web report it by default shows the L bracket. This is ugly, especially on a large blank area. The work around is to change the format of the cell, but why force everyone to go change the format. It is also not...

Navigating from a scheduled task in task scheduler to the actual ETL component (groovy/ standard job, etc) would be handy. Right clicking and selecting an option to navigate to the respective ETL component would save a lot of time in implementatio...

Dark mode like in Excel

Allowing Actions on Labels were initially disallowed because strictly speaking Labels should just be a visual object. However, labels have a lot more formatting capabilities than buttons, combo boxes or lists. For example, vertical centering, word...

For the moment, we can't have a scheduler action and then a download file action. (The download action is lauched before the end of the scheduler). It will be interresting to have the option "Wait for job to be done" (like with integrator action) ...

When we setup a security at dimension level, some users are set as N to prevent an access. In report spreadsheet, the element is displayed in a single cell (not using dynarange). But when non eligible user open the report, the particular element t...

When users have to switch between environments, it is often very difficult for them to "quickly" recognize which environment they are on. It can happen that the wrong data is used, e.g. plan data is accidentally entered in the test server instead ...