How to: Getting started with Qlik Catalog connector in Qlik application automation.

[PradeepUrala]

This article gives an overview of the available blocks in the Qlik Catalog connector in Qlik Application Automation. The Qlik Catalog connector is built to enable Qlik SaaS users to utilize entity, fields, and lineage capabilities in the automation.

Authorization

Qlik Catalog connector uses the Cross-Site Request Forgery (CSRF) token as an authentication token and session ID to authenticate to your Catalog on-prem instance. Ensure the Base URL is correctly specified while connecting to the Qlik Catalog.

Working with Qlik Catalog blocks

All the blocks for Qlik Catalog use the REST APIs. The following objects have easy-to-use blocks:

• Entity
• Fields
• Lineage
• Metadata

The primary use case of this connector is to leverage the Entity, Fields, and Lineage blocks. Users can list out the newly updated Entities and Fields using the "List changed entities incrementally" and "List changed fields blocks respectively. This helps to retrieve the updated entities and fields on a regular basis. On the other hand, Lineage blocks are used to retrieve the Lineage graphs and nodes based on specified search criteria.

Furthermore, it is possible to work with other objects like Import, One-click-publish, Profile statistics, and so forth using the Raw API blocks.

Below is a basic example of how to use the Raw API blocks. This example demonstrates how to retrieve available field metrics using a Raw API list request. As per the API documentation, the action path of this API call is '/profile/v1/available'. Specify this in the input parameter of the block and run the automation for results.