Talk to your data.
Get trusted answers.

• Developer will clone the application (Say App_A.qvf) from the live stream. The cloned app should present in the Developers work area. This will be handled in the new branch in SenseOps.
• Developer will do the modification (Adding new chart in the existing sheet) in the work area app App_A and commit it to his branch
• Developer will create a merge request to the Master branch
• Manager/Admin will execute the merge request
• Manager will create a Job to publish the App_A.qvf in Live stream (Replacing in the same stream)
• Manager have the privilege to rollback to any versions

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.

Please refer to our documentation for the full list of prerequisites, including Qlik Sense version compatibility, necessary access rights, and server configurations needed to set up SenseOps successfully.