FAQs

SenseOps is a No-code DevOps platform for developers to collaborate, deploy and govern Qlik Sense applications at scale. SenseOps streamlines source code management and deployment of Qlik Sense applications, Mash-ups and Extensions throughout the Business Intelligence Lifecycle. A unifying platform with built-in code review mechanisms and integrations, SenseOps makes it possible for developer teams to seamlessly build, commit, manager their on-going updates through automation.

When two or more developers work simultaneously on building and deploying an App, it can lead to misinformation on which is the latest version and eventually slow down deployment due to missing information on inter-app dependencies. The more the Apps, the bigger and riskier the challenge.

SenseOps offers end-to-end source code management for Qlik Sense. It stores all the App versions, tracks code changes from time-to-time and provides instant visibility on who worked on the updates to any version, enabling faster conflict resolutions, decisions on deploying or amending versions. A high level of automation powers code progression across environments, saving all the manual interventions in the deployment cycle.

To understand the need for SenseOps, let’s first look at how Qlik files operate and why conventional Git repositories may not suffice. Qlik applications are stored in a proprietary format within the Qlik environment, making it difficult to access or interpret the underlying details directly. Each dashboard created in Qlik is treated as an application, saved in a .qvf file format. This binary file contains everything from scripts, layouts, and visualizations to charts, formulas, and compressed analytical data. Because of the complexity and binary nature of .qvf files, these files cannot be directly versioned or managed using traditional Git repositories.

Standard Git tools are designed to track changes in text-based files, but they fall short when it comes to managing binary formats like Qlik’s.This is where SenseOps comes into play. SenseOps acts as an intermediary platform that extracts the essential metadata from Qlik applications, making it easier to track, version, and manage changes. With SenseOps, you can recreate Qlik files as needed, ensuring smooth version control and efficient deployment without compromising the integrity of the original Qlik environment.In summary, SenseOps bridges the gap between Qlik applications and version control, offering a specialized solution for managing, versioning, and deploying Qlik applications seamlessly.

SenseOps allows Developer, Manager, Promoter and Admin roles to be setup within an organization.

Developer

• Carries out multiple actions: Ex - Clone a Repository (Master) as Branches, run tasks within the Branches, modify Measures, create new Dashboards, send request to merge working version and so on.

Manager

• Creates Projects, assigns Developers and Promoters to them.
• Inspects Merge Conflicts, approves/ rejects merge requests for Branches.
• Creates Repository (Master) with Projects.
• Creates Job definitions (movement across environments) and Packages (Group of related Jobs) for Deployment.

Promoter

• Runs Jobs Packages, Rollback Jobs/ Packages.

Administrator

• Creates environments, defines roles, access controls and integrations.

Yes, however SenseOps has its own LDAP authentication mechanism for every user login.

Yes, code Management supports both versions.

Projects are spaces where developers can manage all updates to Qlik Sense Applications based on the type of Apps, ex: Grouping by Sales, Finance, Quality, etc

No, SenseOps uses the Qlik Sense Repository Service (QRS) and Qlik Sense Engine (QIX) APIs to carry out typical actions such as retrieval of repository information, code comparisons, branch updates, job movements, etc.,

Private sheets are included while taking back-up of the apps, but are not restored in the cloned version of the apps, thus maintaining the inherent security controls.

Cadence for SenseOps releases: SenseOps adopts a monthly release cycle to rollout new features, fixes or enhancements to the product.

Cadence for Qlik Cloud releases: Following any release update from Qlik, SenseOps conducts a study and thorough testing process to address them. Updates in SenseOps are rolled out for General Availability within one (1) working week of a Qlik Cloud release. SenseOps uses stable, Qlik-tested capability APIs to perform most actions, ensuring compliance at all times.

Cadence for Qlik Sense Enterprise releases: Following any release update from Qlik, SenseOps conducts a study and thorough testing process to address them. Updates in SenseOps are rolled out for General Availability within 3 (three) working weeks of a Qlik Sense Enterprise release.

SenseOps enforces a strong authentication mechanism (with username and password) by default. It also enables an SSO-based login with Qlik Sense as the Identity Provider and ensures seamless synchronization of user permissions.

No, MFA is not mandatory for all user roles.

SenseOps offers four pre-defined roles (Developer, Manager, Promoter and Super Admin), designed to meet most of the needs in the devOps cycle. In addition, it supports dynamic roles, which align with Qlik user permissions for further granular access controls.

Yes, SenseOps provides a default session timeout after 30 minutes. However, this duration can be configured.

• Local repositories are hosted on client-managed servers (on-premises) with user-level access controls.
• Cloud backups are optional and rely on security mechanisms offered by external cloud repositories (eg., GitHub, Bitbucket…)

Yes. An audit application (.qvf) helps track user activities and application logs are stored securely on the server where SenseOps is installed.

SSO integration between SenseOps and Qlik Sense ensures that users access only permitted data and resources.

Yes, API access is controlled through JSON Web Tokens (JWT) with both access and refresh token mechanisms.

• At the application level, the middleware offers protection.
• All incoming HTTP requests and any malicious traffic need to be managed based on rules and threat intelligence via WAF.