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