Legacy reporting has exposed limitations and now drives a gradual shift to modern analyticsSomething that I wish would be improved is that TIBCO Jaspersoft Studio looks like something that was designed in the 1980s. The UI is not user-friendly. Finding things in the solution can be quite tedious, and the exported code does not really follow good programming standards. For example, the use of exceptions were not very descriptive. You would have something called exception one, two, three, post-grass exception one, two, three, nothing very descriptive as to what was going on. The files were very long and you would end up with a bunch of code that was not really being used. Helping the tool create more intuitive naming conventions would be better. Maybe implementing some sort of AI logic to clean up the code after it has been generated would help. It would be nice if there was easier integration with other programming languages such as Python, which is where we were migrating to because of its versatility and big data capabilities. Something like Scala and Hadoop would have made it easier for us to remain in Java. I would say to improve TIBCO Jaspersoft, integrate it with other programming languages and other big data tools and include AI functionality. I cannot even see what I need to see in the display box, so I would fix the AI. Another thing to note is that TIBCO Jaspersoft does not offer much in terms of documentation. There were only some wiki pages for some common errors. Customer support required you to have a license. It is not available to the general public. As for performance, working with Java 8 and 11 instead of the latest Java versions is also something that impacted our performance because we had some packages that were dependent on Java version 21 and up.
