Hi Chenna - this definitely breaks the out of box paradigm of Qlik Sense, although there may be customized approaches to do joint development with help of the APIs.
Basically an app on the server is either unpublished or published.
If its published than the load script and approved sheets,bookmarks and stories cannot be edited.
When its unpublished its still available on the hub but only in the 'my work' area of the owner of the application. There is only one owner. So there is a workflow to go through the owner to update/change the approved content.
Would you be looking to modify this to have 'group' work areas so that a team of developers can develop on a single app ? I can make some inquiries .. let me know if that is what you are after.
Its a good question. I think we need to start with how to do multideveloper / one application in the first place before gettig into best practices .
IN4BI and EBI Insights are some commercially available add-ons that support this capability for Qlik Sense. They both leverage the Sense APIs to do this.
Of course you can just use the APIs yourself. Two samples on branch of people doing this. I would suggest signing up for slack channel on branch to get some API assistance with the samples or your own code.
From a best practices standpoint I think the conversation becomes about how best to leverage the API and this is a little beyond me.
Just remember that apps have some or all of the following in them. You may not need to manage all of these in a source control solution
- load script
- data source connections
- App Objects
If you would like to allow accesses to multiple users on Hub > My works, you can realize it by security rules. Starting from p.84 in the following document, several examples of security rules are provided:
And, for instance, "Security rules example: Creating QMC organizational admin roles" on p.87 grants department admin user full access rights to apps created by users belonging to the department. I believe you can get an insight on what you are trying to do from these examples.
Masaki is right and I have solved this problem. I have put this into my blog:
Shortly, you define Custom properties and put and object and users related to the app into it. In the security rule you define, you provide the rights. This works even for unpublished apps, which is superior.
We tried different solutions but found nothing really professional. We still have the problem of working multiple on an application. Finally we tried different products on the market and found VM4QS extremely interesting. It makes collaboration very easy and reliable and deployments between servers are a mere formality. In addition we can manage all server resources, not only applications, but also excels, includes, content libraries and extensions very easily. What else...
Yes in deed. I also worked with VM4QS and found it very useful. Especially this can be very useful for depoyment scenarios to test and production environments and having versioning and comparing functionalities. Especially for Qlik Sense, this tool provides great benefits. However, this tool is not very cheap, so it suitable for medium to large environments.
In my personal opinion, this tool should be integrated into the QlikView and Qlik Sense environments.
Use Header Authentication process to bypass the user login.
You'd need an extension to be installed in Mozilla and a Virtual proxy to be added in QMC...
Extension to install in Mozilla 'Modify Headers'
Once you have Virtual Proxy and Extension Installed in Mozilla, you can give any user name available and login as that user to check his/her work.
Kind of version control. I have personally used this and it is simple to use.