1777 Sentry Parkway West Building 17, Suite 405 Blue Bell, PA 19422 +1 (888) 507-2270
Log in or Register to post comments in the forum
Any chance you could implement a browse path to allow the client to place the report(s) in a location other than the default reports folder?
Enhancements and Feature Requests
Sorry about the delay between replies, I had to step out for a bit. We'll make a note to look into adding this into a future release. In the meantime, you manually make this possible by editing the client's interface.xml file. If you are using version 1.0, this file will be located in the same directory as client.bat, and if you are using version 1.0.1, the file has moved to the lib/properties folder.
You can add a new entry to this file to specify a different report folder location. The new entry looks like this:
If you're using version 1.0, I believe you can specify the absolute path to the new report folder. If you're using version 1.0.1, you'll need to specify a path that's relative to the validator's lib folder. For instance, if the validator is located at C:\OpenCDISC\opencdisc-validator, and we wanted the reports in C:\OpenCDISC\reports, report-folder would be ../../reports/. This is fairly non-userfriendly, so if you have any trouble please let us know, and as mentioned before we'll make this functionality accessible from the UI in the future.
When I open the interface.xml file within the lib\properties folder it says do not edit...
Is this where I add the "<entry key="ReportFolder">report-folder</entry>" new entry?
Apologies for not getting back to you last week. Yep, you can go ahead and add that into the interface.xml file and it should work. Generally, you should leave that file as-is, but this particular property is only supported when you edit that file directly, so it should be fine. Let us know if you have any trouble with it.
Using the command line version, the report location can be explicitly set.
For example, on my Linux machine, here's a sample command to locate the output near the original data files.
java -d64 -Xms256m -Xmx2560m -jar lib/validator-cli-1.2.1.jar -config=$HOME/opencdisc-validator/config/config-sdtm-3.1.2.xml -report:overwrite=yes -config:define=$HOME/2011/DataSubmission/listings/define.xml -source=$HOME/2011/DataSubmission/listings/vs.xpt report=$HOME/2011/DataSubmission/reports/vs.xls
(New in this forum. Hope it is OK that I add to this thread?)
The ReportFolder entry in the interfaces.xml appeared to be exactly the solution to our needs.
Unfortunately it seems that it won't accept a full path, only ralative. And we would like to direct the Report to a completely different drive. 'W:\OpenCDISC\Report'
I added the following to the interface.xml file:
Java Stack trace. Error is the 'FileNotFoundException' exception:
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
Caused by: java.io.FileNotFoundException: D:\app\opencdisc-validator\lib\W:\OpenCDISC\Report\opencdisc-report-2011-10-18T15-22-39.xls (The filename, directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(Unknown Source)
... 7 more
Is this a known limitation?
And does a solution/work around for this exist?
LEO Pharma A/S
Hi Tim, development team,
Do you still plan to add this to the GUI in a future version? Yes, it is indeed possible to set the relative path in interface.xml, but we could not get it to point to another drive.
This is often what you will want in a controlled environment. We install the tool in a read-only location (let's say C:\program files) - so users cannot change the contents - and then do reporting in another location where users have write access. In our case that is another drive. In the mean time we are using the command line as workaround. Here you can set an absolute file path for the report output location.
This is often what you will want in a controlled environment. We install the tool in a read-only location (let's say C:\program files) - so users cannot change the contents - and then do reporting in another location where users have write access. In our case that is another drive.
As much as I know, this feature is not in the priority list.
We're eager to share and ready to listen.
* Required Field