Zurück zur Startseite

Qlik Application Automation: New features in September

Qlik Application Automation has added a new connector and a new template and updated the Qlik Cloud Services Connector.

Qlik Application Automation (QAA) has been helping to create dynamic analysis and integration workflows via a visual builder for some time, which automatically trigger the appropriate actions in the desired SaaS applications. To ensure that working with QAA remains as efficient and convenient as possible, the automation functions are continuously being expanded and optimized. Therefore, new features have been added and improvements have been made again in September.

New Databricks Connector

Qlik Application Automation now allows users to connect to the cloud-based collaborative data science, data engineering and data analytics platform Databricks via new connector blocks. Through the new blocks, Databricks pipelines can be run as part of the analytical data workflow. In addition, automations can be generated that perform or track Databricks ML model transitions and take appropriate actions. In this way, it becomes possible to launch tasks after previous tasks have completed and execute subsequent tasks after the Databricks job or pipeline has completed.

Enhanced template portfolio: Template for API key alerts

To minimize the effort required to create automations, Qlik Application Automation offers various pre-built templates, which are also constantly being extended. For example, a new template for API key alerts can now be used to send email messages to API key owners. The alerts contain a list of API keys that are about to expire or have been revoked. The template can also be used to notify all tenant administrators using a list of API keys without owners (due to user deletions).

Qlik Application Automation Features
Email alert of expiring or revoked API keys (Source: Qlik)

Updates for automation blocks

With the September updates, the Qlik Cloud Services Connector also gets new blocks that can be used to create and update automations and change their run schedules across multiple tenants. In addition, version control of automations via GitHub is supported with the use of optional parameters.

Leave a Reply

Your email address will not be published. Required fields are marked *