Task Orchestration for Sense and Nprinting

ghaliabed — Sat, 16 Nov 2024 01:59:32 GMT

Hello

Researching enabling more DevOps practices for our Qlik Development cycle.

Typical components & pipeline:

Components:

ETL Job creating DW tables (ETL)
Qlik Application with main Dashboard (QMAIN)
Qlik Application using API to trigger Nprinting tasks (QNPRINT)

A typical Data Pipeline in our case goes like:

ETL Refreshes DW (Talend)
ETL Triggers Qlik Sense Task to Refresh QMAIN
QMAIN task then triggers QNPRINT

All this logic is being managed leveraging Qlik API and Qlik tasks and applications to do all the management, and it works fine in most cases.

However we are now facing additional complex situations where it's not a simple sequential steps of triggers,

Ex: We now need to trigger Nprinitng tasks only if its a certain Date and time and if a multiple dashboards are completed. This is just one example.

I am thinking ideally would be to move the orchestration and all logic to an external tool that can also manage Talend jobs also.

Where the triggering of various pipeline steps can be managed there, but even with this has drawbacks with complexity and lost tool specific customization.

Regards,

Abed

topic Task Orchestration for Sense and Nprinting in Management & Governance

Task Orchestration for Sense and Nprinting