2017 was a very busy year for Qlik NPrinting, from the standpoint of improving stability and performance, filling gaps from NPrinting 16, and extending the product with a platform-based approach in mind.

 

Let’s start in April with Qlik NPrinting 17.3.1. This service release contained a significant amount of bug fixes, and on top of the improvements made in version 17.3 in February, represented the first truly stable version of NPrinting. We received positive feedback from the field and at Qonnections shortly after this version was released. During an open discussion at a customer presentation at Qonnections, several customers who were unsuccessful with previous versions voiced that they had just upgraded to this version and were able to get their environments running without issue.

 

While we continue to focus on product stability and quality, crossing this proverbial tipping point allowed us to turn our attention to highly requested gap features and functionality, and building out enterprise reporting APIs.

 

The June 2017 release included a task execution monitoring page where from within the Qlik NPrinting web console, task status, percentage completion, and a snippet of the log file can be viewed. There are plans to increase the amount of data available in the monitoring view in future releases.

 

We also introduced APIs aimed at three types of reporting activities: task chaining, user management, and On-Demand reporting for Qlik Sense (including user selections as report filters). In 2018, we will continue to enhance our APIs to be more robust.

 

Additional highlights included support for Qlik Sense third party extensions, a connection verification button and making metadata reload a schedulable task.

 

In September, we filled the long-requested gap of report cycling, which allows for an easy way to loop through dimension(s) values and produce unique report files for them.

 

Another highly requested capability that was part of this release is the ability to migrate reports between Qlik NPrinting environments. The import/export process includes a check on the connection(s) used for the report template, as well as any filters that are applied to the report. It is on our roadmap to support migration of more Qlik NPrinting entities. Note that you can effectively “clone” a report by exporting it and then re-importing it into the same environment.

 

And in our final release of the year (November 2017), another key gap was filled with embedded reports. HTML reports or reports rendered in image formats can be embedded directly in the body of an email message.

 

Last but not least, we added new image quality settings for reports. There are now three options to choose from when adding a report to a publish task: normal (96 dpi), high (192 dpi), and very high (384 dpi). While these settings impact both QlikView and Qlik Sense images, the overall quality improvement is much more evident with Sense.

 

At this time, we also have a technical preview of our February 2018 release available on Qlik Community. This release includes support for JWT authentication, as well as DMS authorization for QlikView. Please see the technical preview help site for more information.

 

We are looking forward to 2018 being a great year for Qlik NPrinting and its users!