A number of customers have asked recently how to update NPrinting URL's within a Sense OnDemand component as you promote a Sense app from one environment to another. With the OnDemand component available in Qlik Sense February 2020 there is configuration option that enables an environment promotion strategy. I have provided an overview in this video found on the Qlik Help site. Hope you find it helpful!
SR's also containing the component:
In case you missed it last week, Qlik NPrinting April 2020 was released last Tuesday. The Qlik NPrinting team is excited about this release in that it offers the frequently requested Dynamic Email capability. Qlik NPrinting April 2020 now allows for the ability to distribute email reports to recipients based on user specific email addresses, or Qlik Variables containing email addresses derived from QlikView or Qlik Sense connections. Qlik NPrinting Developers will notice that user profiles now have definable alternate email addresses and the Publish Task Email configuration allows for more flexibility in distribution configuration. One of our customers referred to this new Dynamic Email capability as being a dramatically improved implementation of the old QlikView NPrinting 16 CC/BCC functionality. We hope you enjoy!
As an aside - for those of you who were passionate about the NP16 Test Task capability, this Dynamic Email capability actually deliveries a compelling addition to my previous post on using Folders in the Verifying Publish Tasks in Qlik NPrinting 19+. The flexibility of the Dynamic Email configuration now allows a developer to distribute emails to an email address for verification purposes. This would be an explicitly configured email, sending an instance of each (publish task) user report email to the verifying Individual (see the screen cap below). Or course, the developer would have to set the final Publish Task email configuration distribution attributes after verification. Another trick to add to your Qlik NPrinting 20 toolbox!
Screen capture explained:
The attached Migration Playbook is intended to be a consolidation of references for those who are on a QlikView NPrinting 16 to Qlik NPrinting 19 migration journey. It includes migration content from Qlik Community Posts, Qlik YouTube Channels, Qlik Support articles, Qlik Help site references, and guidance from the Qlik NPrinting product team. Read it from front to back or just selectively review the sections that relate to you - I hope you find this useful!
Reminder - this is relevant to QlikView NPrinting 16 customers only. If you are on Qlik NPrinting 17+ this guide is not for you.
Updated April 28, 2020: change log in V2 document attached.
We are pleased to announce the release of a migration tool in the November 2019 version of Qlik NPrinting that facilitates the migration of QlikView NPrinting 16 projects into a Qlik NPrinting 19 environment.
Attached to this post is an FAQ to help address the most critical questions that may arise before, during, and after using the migration tool.
There are other resources that will assist you though this process. Namely, a new section in the help site that includes step-by-step instructions and troubleshooting as well as a YouTube video that demonstrates how the tool works.
When posting to the Qlik NPrinting forum with questions about the migration tool, it is important that you use the newly created label Qlik NPrinting Migration Tool to help us differentiate these posts from other NPrinting discussions.
Please also use QlikView as the product label, as the scope of the migration tool is limited to migrating QlikView NPrinting 16 projects to Qlik NPrinting November 2019 (or newer) with QlikView as the data source for reports. There is no mechanism to convert connections from QlikView to Qlik Sense in this feature.
We are extremely excited about this feature since it will help our QlikView NPrinting 16 customers make the move to and experience the many benefits of Qlik NPrinting 19, including multi-threaded scalability, enhanced security, and a robust set of APIs to tackle even the most complex reporting scenarios.