## Roadmap of planned features

- Security

- Token based verification of requests:

- This way a single JasperReportsIntegration can be secured and used simultaneously by different applications. Using this token approach we can prohibit application A from using the data source for application B.
- Process flow:

1. A token will be stored in the schema issueing a reporting request.
2. The token will be passed to the JasperReportsIntegration.
3. Before executing the request, the integration will validate the token using the requested data source with a verification function.

- Disabling testing / debugging for production systems

- New setting in application.properties to disable the report tester
- New setting in application.properties to disable the basic connectivity test (will tell you the installed user objects)

- Deployment

- Deploying new reports directly from your APEX application or a shell script

- New report definition files (report.rxml) can be deployed to the JasperReportsIntegration directly without the need to copy the files to the application server manually.

- Voting for new features using UserVoice (http://www.uservoice.com)
- Smaller code enhancements

- Include version number in packages
- Load jasperreports.properties from the directory conf in addition to the classpath

- APEX

- Create plugin to call the reporting engine.
- Create demo application covering the typical use cases

- How to pass additional parameters to the report

- Package the database objects as supporting objects together with the APEX application.

- Bugs

- HTML format not working properly, need to rewrite the urls for the images. Currently, no images or logos can be displayed in html format.