CAPANAS DEPLOYMENT FRAMEWORK
Capana Deployment Framework
For Capana, it is essential to create a Qlik platform that is easy to maintain, enhance, and scale. That is why we have developed our own Deployment Framework (DFW). Our DFW closely aligns with Qlik's own Deployment Framework, but we have customized it with our best practices.
A DFW structures the Qlik environment and facilitates the reuse of Qlik code and files, making it easier to manage and maintain.
Capana's Deployment Framework includes:
> Back-end development (script and architecture)
> Front-end development (design and best practices)
> QMC (Qlik Management Console)
The back-end constitutes the core structure of the Qlik solution. Capana's DFW covers three main areas:
> Folder structure
> Data modeling
The folder structure makes it easier to develop and maintain a solution. It supports the reuse of both files and Qlik code. The structure follows the same principles as Qlik's DFW, with layers such as Init (extract), Staging (transform), and Master (layout) to support ETL processes.
Variables are used in both the back-end and front-end to control QVW files. In the back-end, they are primarily used for consistent naming conventions, while in the front-end, they provide centralized control over expressions, enabling their use across solutions. In the end application, we employ field associations to achieve user-friendly naming that supports self-service.
Capana follows general best practices for data modeling. Based on our extensive experience in building BI solutions, we recommend utilizing a model that incorporates both a link table and a star schema to the greatest extent possible.