Jaspersoft Studio setup
I will get around to updating http://www.openvpms.org/documentation/csh/1.8/reference/reportsForms to refer to Jaspersoft Studio rather than iReports.
However, here is a quick note.
The necessary connector does not ship with Studio. Hence to set up a connection to the OpenVPMS database you need to:
1. Click the Add Database Adaptor icon
2. Set the Database Location tab as follows: (set user name and password to yours)
3. Set the Driver Classpath as follows: (adjust the path to mysql-connector-java-5.1.34-bin.jar to match you usage)
4. Press the Test button to check the settings.
Regards, Tim G
Re: Jaspersoft Studio setup
Default data source
Unlike iReports there is no concept of a 'default data source'. This has to be set for each report. Initially (for reports built with iReports), it will be set to the 'One Empty Record' source. However, once you change this (on the preview screen) the datasource is saved in the jrxml.
PDF font deprecated
When you open an old report it is lilely to display lots of errors as follows:
All of the errors are caused by the use of a PDF font to bold the field in PDF output. You need not correct the deprecation errors - things will work happily as is. If you want to clean this up, open the source and use Ctrl-F to replace the string ' pdfFontName="Helvetica-Bold"' with nothing.
Regards, Tim G
Re: Jaspersoft Studio setup
Persuant to this Tim I have been working on a better way to version these documents.
Currently ODF files and DOC files dont really version at all - as you can cant diff them to show the changes effectively each change is a new file. I am investigating using an open source tool called Pandoc that can convert DOC, DOCX and ODF into markdown and diff them there.
Jasperreports XML files can be diffed naturally but often are confusing because the editors randomly change large slices of the file without actually changing anything.
I would really love to be able to version these files in the source better - creating an internal marker that allows reports to tell us which version a user is using and hence quickly identify users using out of date reports.
Just some thoughts
Re: Jaspersoft Studio setup
Ben - what I would find useful would be:
a) a 'date content uploaded' in the document template
b) a 'date last used' and a 'usage count' in the document template. The usage count would be zeroed on content upload.
We have some 180 templates in the system, and I am certain that not all are used, but I have no way of finding out which are used and how often.
The overhead of a) is negligable; the overhead of b) is almost certainly negligable in comparison with the amount of database access being done by the report/document.
Regards, Tim G