Automating Dev → UAT App Deployment in Qlik Cloud Using Qlik Application Automation

[rohitk1609]

Overview

Most Qlik Cloud environments use at least two managed spaces:

• Dev – where developers build and test apps

• UAT – where business users validate and approve them

Traditionally, promoting an app from Dev to UAT requires several manual steps:

1. Back up the existing UAT version

2. Go to Dev

3. Move the updated app to UAT

4. Delete the backup after validation

To simplify this process, we built a Qlik Application Automation workflow that performs the entire Dev → UAT deployment automatically — safely, consistently, and without manual intervention.

This article explains the automation flow, block-by-block, so you can implement it in your own environment.

Automation Flow Summary

The automation performs the following steps:

1. Identify the UAT app to back up

2. Create a timestamped backup

3. Identify the Dev app to deploy

4. Move the Dev app to UAT

5. Update environment variables (vEnv)

6. Reload the app in UAT

7. Delete the backup after successful reload

8. Send a confirmation email

Below is the detailed explanation of each block.

Step-by-Step Block Explanation 1. List Spaces (Qlik Cloud Services)

Purpose: Retrieve all spaces in the tenant. Input: None Output: A list of all spaces (Dev, UAT, Shared, etc.)

We later filter this list to find the UAT space.

2. Filter List – Find UAT Space

Purpose: Select only the UAT managed space. Input: Output from List Spaces Filter Condition: name = "UAT" Output: The UAT space ID

This ID is required for backup creation and app movement.

3. List Apps (Qlik Cloud Services)

Purpose: Retrieve all apps inside the UAT space. Input: UAT space ID Output: List of apps in UAT

4. Filter List – Identify UAT App to Back Up

Purpose: Select the specific UAT app that needs to be backed up. Input: List of UAT apps Filter Condition: App name contains the user‑provided string Output: The UAT app ID

5. Create Variable – BackupAppName

Purpose: Generate a unique backup name. Input: User input + timestamp Output: A string like: SalesDashboard_Backup_20240424_1530

6. Copy App (Qlik Cloud Services)

Purpose: Create a backup copy of the UAT app. Input:

• App ID from Step 4

• Backup name from Step 5

• UAT space ID Output: Backup app ID

This ensures rollback is always possible.

7. List Spaces (again)

Purpose: Retrieve spaces again to locate the Dev space. Input: None Output: List of spaces

8. Filter List – Find Dev Space

Purpose: Select the Dev managed space. Input: List of spaces Filter Condition: name = "Dev" Output: Dev space ID

9. List Apps (Dev)

Purpose: Retrieve all apps in Dev. Input: Dev space ID Output: List of Dev apps

10. Filter List – Identify Dev App to Deploy

Purpose: Select the Dev app that needs to be moved to UAT. Input: List of Dev apps Filter Condition: App name contains the user‑provided string Output: Dev app ID

11. Move App to Space

Purpose: Move the Dev app into the UAT space. Input:

• Dev app ID

• UAT space ID Output: App now resides in UAT

This replaces the old UAT version.

12. Update Variable (vEnv = "UAT")

Purpose: Update script variable so the app uses UAT connections. Input:

• App ID

• Variable name: vEnv

• Value: "UAT" Output: Updated variable inside the app

This ensures the reload uses UAT data sources.

13. Do Reload

Purpose: Reload the newly deployed app in UAT. Input: App ID Output: Reload status (success/failure)

If reload fails, you can extend the automation to restore the backup.

14. Delete App (Backup)

Purpose: Remove the backup after successful reload. Input: Backup app ID Output: Backup removed

This keeps the UAT space clean.

15. Send Mail

Purpose: Notify the team that deployment is complete. Input:

• Subject

• Body

• Recipients Output: Email sent

Conclusion

With this automation, Dev → UAT deployment becomes:

• Consistent

• Fast

• Error‑free

• Rollback‑safe

• Fully auditable

This approach eliminates manual steps and ensures that every deployment follows the same controlled process.