Task chaining is here! We are delighted to announce that one of the most requested features for Qlik NPrinting is now available with our February 2018 release.
If you thought that Qlik NPrinting 17 triggers were only time-based and prevented you from creating event-based dependencies on other Qlik tasks, (such as app and data reloads) then think again. This functionality is now available out-of-the-box using the Qlik NPrinting APIs and a Qlik load script!
You can now seamlessly run tasks that represent the typical workflow for a Qlik NPrinting report. Using the publicly available APIs, you can reload Qlik NPrinting connection metadata, update user information and run a publish task, all following a Qlik data and/or app reload.
You can also institute a poling mechanism to ensure that one task is complete before starting a subsequent one.
The technical details and examples can be found here: https://community.qlik.com/thread/292037 (even though the example uses Qlik Sense, this can be done just the same in a QlikView load script).
Please note that this functionality was made possible by the resolution of a bug related to the Qlik REST connector. You will need the REST connector v1.3 which is part of the February 2018 release of Qlik Sense, or it can be downloaded separately and copied over the old REST connector.
Our long-term vision for reporting involves exposing the Qlik NPrinting tasks in the QMC, however this is a first major step toward integrated scheduling
This is a great step forward for Qlik Nprinting 17.
However we as customers will wait on using Qlik Nprinting 17(we use SSRS) until 2 features are available.
1. Our long-term vision for reporting involves exposing the Qlik NPrinting tasks in the QMC, however this is a first major step toward integrated scheduling
I would guess that you guys are mening (in QMC):
To have a trigger e.g. "Trigger Report on Nprinting 17"
2. Easy LDAP integration
The same integration to LDAP (as in QMC) so that reports in Nprinting 17 can use AD groups and users directly.
The long-term vision for NPrinting is for it to be much more integrated in the product. That would mean NPrinting tasks in the QMC, as you described. Also having a single set of users to mange instead of a set for each product.
Until we get there, we will continue to deliver incremental value to the existing functionality of the product. We have set as one of our top priorities to have AD integration in the NPrinting web console. It will be part of our roadmap for this year, exact date TBD.
Pablo - we are addressing user management in our upcoming releases. Our top priority right now is for active directory integration in the NPrinting web console. We may consider additional data sources (like text files) in the future.
@Stephen_Jasionowski might as well comment on this, "The long-term vision for NPrinting is for it to be much more integrated in the product." any news here?
@SimonK , That is great that you guys are focusing and future development your SaaS platform however, do you guys take in any ideas from us customers that are still working in QlikView and/or Qlik Nprinting products?
If we take Nprinting for an example there are still a lot of features that are missing and that we (customers) have pointed out in the "Idea" section of the community but still no response, or rather "Look in the API" is the simplest answer we get..... very frustrating.
* Built-in trigger from QlikView (maybe Qlik sense) to Nprinting tasks
* Built-in dependency's in Nprinting when triggering tasks within Qlik Nprinting. E.g when a meta data connection is finished -> trigger a publish task
"Simple" Ideas like this is still not implemented 2 years after we asked for them... This should be out of the box, but is not.
