Suggest an Idea

[simonaubert]

Hello,

Well, everything in the title. This idea is about an integrated versioning system. Basically, my raw thoughts:

-in QMC, you would have several options :
       .Always keep previous version (with data) +a max quantity of version you save (empty meaning "all")

       .Always keep previous version (without data) +a max quantity of version you save (empty meaning "all")=> save a lot of place when you have huge applications

       .Ask the user if he want to version or not and with or without data +a max quantity of version you save (empty meaning "all")

when the user publish an app, the publish popup allows him to save a comment. However, he can consult all the versions from hub or qmc and according to his right downgrade to a previous version with the date of publication.


Sorry, it's a little messy.

Best regards,

Simon

[jp_golay]

ebiexperts WIP do DevOps/Agile Version control of Qlik Sense, QlikView and NPrinting. Also deployments to external servers, quality control (doc analyzer, check lists)  it's well adopted by a lot of Qlik Customers.

have a look at https://www.ebiexperts.com/qlik-integration/

[jpk]

Would be a nice feature and we will support this in ebiexperts-WIP which provides agile/devops/dataops source control, versioning, quality control, publication and audits. Integrations to Qlik Sense, NPrinting & QlikView & Jira.