First the standard caveat. No promises that any of these will ship or that if they do, when. This is what we’re planning at present, but things can change. Especially the further out we go. In addition, while Q4 & Q1 are pretty locked down, we almost certainly will be doing more in Q2 & Q3.
And why do we list this out when none of it is guaranteed? Because knowing what’s likely can be of use in your planning. And we always appreciate feedback to what we are proposing. And with that, on to it…
Q4 – 2019
- A lot of engine settings are global to the engine. Every generated report uses those same settings. That worked great 5 years ago when most installations were to use the engine for a single project. But now that it’s a service those settings need to be unique for each report. We’re adding this functionality.
- We are adding a number of minor enhancements to the conditional wizard.
- We are adding a search to the metadata tree in the XML, JSON, & OData wizards (see the SQL Wizard for an example).
- We are adding some usability enhancement to the connection editor (including the one written by yours truly).
- We're upgrading to the latest BouncyCastle library (used for PDF encryption).
Q1 – 2020
- Upgrade most of the 3rd party libraries. For some (dom4j for example) the later versions are buggy. And for others the API changed significantly, to no great value (log4j). And so we will do this carefully.
- Upgrade the .NET engine to the .NET framework 4.8. This is part of our Q3 effort to port to .NET Core.
- Enhance the SalesForce query wizard to provide more advanced functionality – while keeping it simple.
- Add a new Input parameter type that supports multiple lines of text.
- Improve the error messages in Designer. This will likely improve the info in engine exceptions too.
- Improve the XPath Wizard, mainly around support for functions.
- Add more Hotkeys to the Designer.
Q2 – 2020
- Carry over all Excel (XLSX) formatting to XLSX output.
- Add support for QR codes. This will likely include native support for barcodes, although the present approach via barcode fonts will remain.
- Provide an API in the engine toreturn all the tags in a template, similar to what the Designer can already do.
Q3 – 2020
- The .NET & RESTful engines run on .NET Core.
And please remember, the above is our intention at present, but is not guaranteed. And if you have any thoughts on the above, or what you think is missing, please email or call me.
-David Thielen, CEO