iVIEW Dataflow

Remove the complexity of code

with iVIEW Dataflow

For businesses wanting to save time and money on data application builds or are looking for a cost-effective way to enable internal teams to service their business’s data requirements more easily, iVIEW Dataflow is an easy to use, visual front-end interface that creates code for you, standardizing the use of code within your business and enabling your business to move towards a self-service environment.

Key Features

Benefits

Save Time With Standardised Code

iVIEW Dataflow is a low-code framework for Qlik that helps you save time and money. Everything is configured in a central repository so there is no need to make changes to the code, no need to make multiple updates when conditions change.

Governed ETL Processes

All workflows are structured according to Qlik’s best practices and compatible with an integrative corporate BI strategy. Give your Qlik projects a standardized structure and simplify your deployment process. Comprehensible, easy-to-read ETL logic, also for non-Qlik-developers.

Powerful Workflow Engine

Data integration and dimensional modelling with an intuitive and powerful stack of ETL operations for the BI developer. The generated Qlik code is readable and well documented.

Automated Workflow

Dataflow makes use of Qlik’s own APIs for a controlled, flawless deployment to Qlik Sense . Unify your deployment processes and allow for a continuous delivery in your BI projects.

State-of-the-art Technology

Stand-alone web application which is easily installed in a few clicks.

How it works

Discover the intuitive Features of iVIEW Dataflow

Main Features

What's coming

Dataflow – On Demand

The on-demand model uses the iVIEW Dataflow framework with the wizard to automatically generate user-based applications based on a pre-defined data model.

This can be a powerful tool for organizations that need to build and deploy customer applications quickly & without requiring extensive development resources.

Front-End App on the Go

The direct connection between the Dataflow model and the KPI in the iVIEW Library would allow users to view and analyze KPI data in real-time, without having to manually transfer data between the two systems.

The split screen between the iVIEW dataflow model and the KPI dashboard in the iVIEW Library would enable users to quickly compare and analyze data, making it easier to identify trends and patterns.

Workflow Landscape in Dataflow

A workflow landscape is a visual representation of the various workflows and data dependencies within a system or project.

It shows how different data sources, applications, and processes are connected and interact with each other which helps to identify bottlenecks, redundancies, or potential issues in the system.

It can also help with data lineage and tracking of data movement.

It provides a clear view of where data is coming from and how it is being used.

It will also help identify the different applications involved and how they relate to each other.

Use cases For iVIEW Dataflow

SUCCESS STORies iVIEW Dataflow

Technical

FAQ

CAN I GUARANTEE WITH THE iVIEW LIBRARY THAT ITEM DEFINITIONS MATCH MY DATA / DATA MODELS?

For items to be successfully distributed to Qlik Sense, there must be a direct dependency between the items managed via the iVIEW Library and the underlying data models and applications.

To address this, the iVIEW Library provides for direct mapping of Qlik Sense applications to centralised content.

A list of “compatible” Qlik Sense applications can be maintained via the metadata of each item, so that the affiliation to these applications can be checked before the content is distributed by the deploy action.

WHAT TECHNOLOGY DOES THE CENTRAL REPOSITORY USE, HOW BIG IS IT AND CAN IT BE ACCESSED?

For the data storage, you can choose between an embedded database (H2) and MS SQL Server database when installing the iVIEW Library. The latter serves as a repository and as a persistence layer.

The size of the database correlates directly with the size of the Qlik Sense infrastructure and how intensively the content is centralised. Basically, only metadata is held here. Experience shows that the size is in the small to medium MB range.

The database is openly accessible for read access, so that further analyses can be carried out.

WHAT SECURITY CONCEPT IS THE IVIEW LIBRARY BASED ON?

For the Qlik content, the library follows the security concept of Qlik itself 100%, i.e. the user only sees as much as in Qlik. This includes and considers the implemented security rules as well as the “Admin Roles” that are configured in the Qlik Management Console (QMC).

The iVIEW Library implements Keycloak as an authentication and authorisation module. An LDAP connection is provided by default. However, authentication can be extended to other methods and protocols, such as SAML, OAuth2, etc.

For authorisation, the iVIEW Library relies on two basic roles: Library User and Library Admin. The model can be extended to the individual functions of the iVIEW Library. For example, roles for Deployer, App Manager and Library Owner can be easily implemented.

Contact Us

Address

Informatec Ltd.liab.Co.
Freidorf 151
4132 Muttenz
Switzerland

Email: info@iview.io