Curious to see how people are managing apps that they need to discontinue.
Without going into specific details I have a series of apps that need new versions. Essentially 2.0 to 3.0 versions. Not something I can do in the original development app itself because I will need to run concurrent versions for testing.
Current general process is this:
Extract Layer - Extracts data
Transformation1 - Takes that data and sorts it into general categories (customer info, finance etc)
Transformation2 - Takes the relevant data, combines it and makes it relevant to the front end apps.
Front End apps - Takes T2 data and presents it, amongst other things.
Essentially I am going to have to duplicate this process and its apps then fundamentally change how things are done due to internal requirements changing. Worth pointing out I have already done this once before.
My question is this. What is the best way to manage the old apps? I will be left with 3 versions of the named apps. The first of which I could probably delete now in many cases.
Is there a way to hide apps from view without deleting them or should I download the script's/apps, archive them locally and then delete them? Happy to leave them in the Qlik instance but my oddly specific OCD is struggling with seeing them appear multiple times on searches.
I do the same on one of my clients sites - What I normally do is have a Testing stream for the apps that needs to go through UAT. But once I have older versions of the apps I publish them to a stream called "Archive" - Only admins / managers have access to this stream. This way in 6 months time when the customer has questions they can always refer back to the "original" version.
Once the apps go into Archive I also remove the reloads to have a nice Point In Time application.
This is for a on Prem solution but I am sure you can do the same with spaces in Qlik Saas.
Regards Jandre
Mark the solution as accepted that solved your problem and if you found it useful, press the like button! Check out my YouTube Channel | Follow me on LinkedIn
I have done this two different ways. Running Windows not SaaS Qlik Sense. In a production environment, I created a new Stream and called it 'Archive' that only RootAdmin had access to. If an application was no longer needed, I just moved it to that stream or imported it to that stream. It all depends on whether you allow users to create and publish sheets. If you allow users to create an publish, you do not want to delete the application as re-publishing and replacing the existing application will keep the user generated sheets. The other option is to export the application and save the QVF in an archive location on disk. However, with this method, you only get the base sheets and not the user generated sheets. This was a simple solution that worked for me in my installation. Application without user created sheets was always an export. If the application had user generated sheets but the application was being retired, I moved it to the Archive stream just in the event that it was needed at a later date.
I'm not sure how things function in SaaS, but for the on-prem Qlik Sense you could for example move the old apps to a stream that only developers have access to, or you could make sure the old apps aren't published so that they only can be seen by the user who owns them. But archiving locally is of course also an alternative.
I think I used an old system I learned and added z. before the name so it always appeared at the bottom of the list but a separate space is a good idea.
I hadn't considered sheets to be honest but I think the sheets situation is fine because its only me and maybe 2 others that create sheets in all the apps up to front end anyway. The data in the v1.0 apps would be irrelevant anyway so wouldn't be comfortable letting them use them anyway.
