This release is mainly a bug-fix release with only few new features. Over the last few months we concentrated on making this release a "god damn stable" beast. With 132 cases solved and numerous blocker-class fixes resolved, I think we reached that goal.
On the new-feature side, we still have some good things to report:
- Report data can and will be cached now. This way, the interactive parameter display and designing reports is more responsive now.
- The SingleValueQuery- and MultiValueQuery-Function can now be used to define dynamic default selections in parameter.
- You can redefine the list of output types that are available for a report
- Pentaho-Metadata datasources can now accept multi-selection parameter.
- Our Pentaho-Metadata datasource got a new Advanced mode to calculate the query string in a expression.
- There's a whole bunch of new barcode-types available.
- LibLoader is more aggressive on caching data from HTTP connections. So even if your service does everything wrong when it comes to cache-headers, we will handle that gracefully now. And best of all: In most cases you can "just use it(tm)". You don't need to configure a single bit.
- Thanks to KSK Solutions in Japan, we now have a Japanese translation for the Pentaho Report Designer
- There is a experimental CDA datasource now. It works, even though it is still a bit flaky in Edit-Mode in the Report Designer.
How can i enable the CDA datasource? I enabled "experimental" features, but there is no trace of CDA in the list.
ReplyDeleteCDA does not *ship* with a GA build. Drop the extensions-cda and datasource-editor-cda jars from either CI or from a local build into the PRD and it will pop up.
ReplyDeleteany plans on enabling parameter (or function) as a color choice in graphs?
ReplyDeleteNot until it becomes important enough for at least one person to actually file a JIRA case for it ;)
ReplyDeleteI think there is more people interested in this topic.. found quite a lot of questions regarding this issue and no answer.. ok.... Ill try.. :)
ReplyDeleteI said: Well, file a JIRA case. If there is no JIRA case, the feature is obviously not important enough. After all, filing the case costs 5 minutes, fixing it costs hours. So why should I invest hours iv no one even spends 5 minutes.
ReplyDeleteIf that sounds harsh: Well, you are competing with everyone who has cases filed in JIRA. They think their case is important too - and they already invested the 5 minutes to create a case for it.
Ahh, PRD-3336 is filed. Great, now we are talking.
ReplyDeleteNext, this will be triaged by Pentaho and scheduled for a release. At the moment, the next release we are planing is 4.0.
There may be a 3.9 release before that if there are enough bugfixes to warrant one, but my personal bets are on PRD-4.0.
waw.. thank you so much for a quick response.. guess I'll have to change the colors manually till 4.0
ReplyDeleteand BIG THANK YOU for 3.8 - saved my hair when solving the issue of subreport's element color defined be the field of the query.
and .. not willing to spend 5 minutes was not my case - as I have spend several days looking for the solution.. I just was not sure if I"m not missing something and did not want to pollute your JIRA with my "maybe misunderstood" issues. Moreover I was not sure I can do it properly – it was my first JIRA case :) - Just to explain. I can not even say how much I appreciate all your amazing hard work
ReplyDeletei still dont know, how to switch/change the language of this program! please help!
ReplyDelete