patientClinicalEvent a4
Hi All
I try to add the "PatientClinicalEvent a4" to my template but it keeps showing a message with "please make sure it is saved to be compatible with Jasperreports 3.7.6
On TIBCO Jasper soft stodio I've tried to add 3.7.4 version as there was no 3.7.6 but still keep getting error message on Jasper stodio too and when I push the Preview button it says Document is empty.
Appreciate your help
Regards
Ben Ajilian
Re: patientClinicalEvent a4
The "patientClinicalEvent a4.jrxml" is a template included in OpenVPMS 1.7.1 and earlier. Whilst it can be developed in Jaspersoft Studio It can only be run within OpenVPMS.
You should be able to save the report in Studio and have it run in OpenVPMS 1.7.1 by setting compatiblity to JasperReports 3.7.5 or 3.7.4.
Re: patientClinicalEvent a4
Ben - I just tried to duplicate this, but I cannot. I have two systems: A - running OpenVPMS 1.8 using JasperSoft Studio 6.1.0final and B - running OpenVPMS 1.7 (where I normally use iReports 3.7.6 for developing jrxml based stuff).
On the A system I pulled a copy of patientClinicalEvent A4.jrxml from my 1.7 archive and edited it in Studio - just to put 'xxxx' in front of the report title - and then saved it after setting the version to 3.7.4 as shown below
Checking the saved jrxml, I can see:
I then went to my B machine and using Administration|Templates built a new template called 'xxx Patient Clinical Event' using the above content and setting the Type to 'Patient Visit'.
I then used Administration|Organisation|Practice Location to set the above as a template for my test Practice Location zz-test. I then logged out and in again to get the Practice Location changes to take effect, called up patient ZZ-Dog and his medical records, and then pressed the Print button. Out came the xxxx Patient Medical Records report.
So if you use Studio to edit a report and then save it in 3.7.4 format, you can use the resulting jrxml in OpenVPMS 1.7
I apologise for the detail above, but hopefully you should be able to see where you have done things differently to me.
On the 'Preview' question, you cannot use the preview facility (in either Studio or iReports) if the report you wish to preview is not an SQL based report - ie has Type other than Report. [This is because OpenVPMS provides the data to the report depending on its Type - and Studio/iReports cannot mimic this.]
Hence when developing non-Report things, testing is a pain - you edit the template to import the content file, run the report (eg Patients|Medical Records|Print), then if there are problems, back to iReports/Studio, change things, save, then back to Administration|Templates to edit to update the content file and repeat until you are happy.
However, preview works wonderfully for SQL based reports and you only need to do a final test in OpenVPMS. iReports has problems previewing reports that have subreports (you need to tweak things) but Studio does it wonderfully.
My personal feeling is that if you are using OpenVPMS 1.7 then it is better to stick to iReports 3.7.6 - rather than using a later version of iReports or Studio and telling them to save in 3.7.4 format. However, when you go to 1.8, switch to Studio.
Regards, Tim G