Version Control for Qlik Sense

SenseOps is a no-code DevOps platform for developers to collaborate, deploy, and govern Qlik Sense applications at scale. SenseOps streamlines version control 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, and manage 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 control 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

SenseOps allows developer, manager, promoter, and admin roles to be set up 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 a 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 a repository (master) with projects
• Creates job definitions (movement across environments) and packages (group of related jobs) for deployment

Promoter

• Runs job 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.

SenseOps supports all Qlik Sense on-premise, SaaS versions (Enterprise editions), mashups, and extensions.

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

Repositories are a collection of app versions/files created within a project. While developers work with multiple versions, make commits from time to time within repositories, all these changes are auto-tracked for versioning and available on demand during deployment or update scenarios

Jobs are pre-defined actions to enable deployment: code progression between environments (Development, UAT, and Production). Packages are a collection of related Jobs configured and run as a batch and can be re-used by teams for frequently run programs.

In case of a single developer in an environment, the developer can clone a Qlik application (Master version) from their workstream, modify it, and commit changes to their branches. On completion of all changes, he/ she raised a merge request with the master branch. The request gets approved/ rejected by the manager, and a job is run to publish the app live. At any point in time, the manager can rollback to any older version with a single click.

In case of many developers in an environment, 2 or more developers working on a Qlik Sense app can clone from their work streams and work on them as separate branches. The developers can then modify and commit to their respective branches from their work streams. The manager/admin executes the merge requests from each developer and decides which request should be merged to accommodate changes and commit to the master branch, manager creates a job to publish in the live stream. Manager can also roll back to previous versions.

In case of multiple developers in a single Qlik environment, 2 or more developers working on a Qlik Sense app can clone from their work streams and work on them as separate branches. The developers can modify the apps and commit to their respective branches. The manager/admin reviews merge requests from developers and decides on the changes to be finally committed to the master branch. Manager creates a Job to publish to production and can publish/replace the same app in another Qlik environment. A Manager can also roll back to previous versions.