This article provides an overview of how to manage space membership for groups using a Qlik Application Automation. This approach can be useful when migrating from QlikView, or Qlik Sense Client Managed, to Qlik Sense Cloud when security concerns prevent the usage of Qlik-CLI and Powershell scripting.

Environment

• Qlik Application Automation

Prerequisites 

• Access to Qlik Cloud tenant
• User assigned the role of Tenant Admin
• Office 365 account (for Microsoft Excel).

Sheet Configuration

In this example, we use Microsoft Excel to configure group Space memberships. A sheet name, for example, Groups, must be added and this must also be provided as input when running the automation. The sheet must also contain the following headers:

• SpaceName
• Group
• Roles
• Flag

Automation Configuration

1. Add an Input block that takes the name of the worksheet (from which data should be read) as input. You also need to specify the first and last cell to read data from, as well as if groups are to be added or deleted.
    
   • Worksheet Name: Name of the Excel Worksheet
   • Excel Start Cell: Enter the Start cell of your Excel Worksheet. Example: A1
   • Excel End Cell: Enter the End cell of your Excel Worksheet. Example: Z23
   • Mode: Add or Delete.
     
     
2. Add two variables of the type number. One to keep track of added groups and one to keep track of deleted groups. These variables will be used to update the run title when the automation has been completed. Observe that only one of them would be used when running the automation since only one of the run modes can be used (Add or Delete).
   Let's call the variables as vGroupsAddedCounter and vGroupsDeletedCounter.
   
   
3. Retrieve the information from the Excel sheets using the List Rows With Headers block.
   
   • Use the "do lookup" function to find the Drive ID and Item ID of the file you will be using as a source. 
   • Configure the other fields to get the values from the input fields.
     
      
     
     
4. Retrieve all the spaces from the tenant using the Search Spaces block inside the List Rows With Headers loop.
   
   
5. Add a Condition block and check if the space exists and if we're in Add mode.
   
   
   
   
6. If the condition is true, list all the members from the space using the List members from Space block by inputting the space ID. 
   
   
7. Retrieve the groups using the Filter Groups block by inputting the filter condition.
   
   
   
   
8. Add a Condition block that checks if the group exists and whether or not the group is a member of the space.
   
   
9. If the conditions are true, add the group using the Add Member To Space block.
   
   
10. After the Add Member To Spaceblock, add a variable block and increment vGroupsAddedCounter with 1.
    
    
11. If the first condition in the List Rows With Headers loop is false, then use a third Condition block to find out if we're in Delete mode and if the space exists.
    
    
    
    
12. If the condition is true, list all the members from the space using the List Members From Space block by inputting the space ID. 
    
    
13. Retrieve the groups using the Filter Groups block by inputting the filter condition.
    
    
14. Add a Condition block that checks if the group exists, and if the group is a member of the space and we delete it.
    
    
15. If the condition is true, delete the group using Delete Member From Space block.
    
    
16. After the Delete Member From Space block, add a variable block and increment vGroupsDeletedCounter with 1.
    
    
17. Lastly, add a Condition block that checks the run mode and updates the automation's run title to display how many groups have been added or deleted.
    
    

     

Considerations

• A multitenant scenario can be supported by utilizing the Qlik Platform Operations connector instead of the Qlik Cloud Services connector. 
• Google Sheets could be used instead of Microsoft Excel.

This article describes how to resolve the NPrinting connection verification error:

x Qlik NPrinting webrenderer can reach Qlik Sense hub error

Environment

• NPrinting: all versions
• Qlik Sense: all versions
  • multi-node QS proxy environment
  • NLB (Network Load Balancer or Alias URL) server address used in front of cluster of Qlik Sense proxy nodes (which are linked to a Virtual Proxy. Proxy nodes will not work with NPrinting unless they are linked to a QS virtual proxy)

Resolution

• Although it is possible to use an NLB address in front of your QS proxy nodes that are used by NPrinting, the error generated in the NP connection verification process will appear as described in the article title
• This error can safely be ignored as this does not affect generation of NPrinting connections
• To eliminate the 'error' message, you would need to update your NPrinting connection to use a virtual proxy node address/computer name behind the NLB address . It must be the computer name and not an alias url).
• The proxy node used must be linked to a virtual proxy with the following required attribute
  
  • Microsoft Windows NTML authentication on the Qlik Sense proxy. (SAML and JWT are not supported. If your virtual proxy uses SAML or JWT authentication, you need to add a new virtual proxy with NTLM enabled for Qlik NPrinting connections).
  • A link between the proxy node and virtual proxy.
  • For all NPrinting to Qlik Sense requirements visit https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#anchor-1

Related Content

• https://help.qlik.com/en-US/nprinting/Content/NPrinting/Troubleshooting/Verify-connection-to-Sense-errors.htm
• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#Requirem

Internal Investigation ID

• QB-2871

This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.

Authentication and Authorization

To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:

• Mail.Send
• User.Read
• Offline_access

Sending Email with the Microsoft Outlook 365 connector

The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.

The following parameters are available on the Send Email block:

• To: A comma separated list of recipients;
• CC: A comma separated list of recipients to which the email should be copied;
• BCC: A comma separated list of recipients to which the email should be blind copied;
• Subject: A title for your email;
• Type: Choose between plain text email or HTML;
• Body: The content of your email. You can use HTML for your email if chosen as the type.

Generating a report and sending an email with the report

As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.

Environment:

Qlik Application Automation 

During a Replicate Full Load, incoming changes occur while the Full load is in progress. What happens to those changes?

Qlik replicate starts the CDC thread before starting the Full load and all the changes show as cached events while the Full load is running. For example, 2 billion records are applied in the Full load state and Replicate again check at the end of the Full load for committed changes.  If 100k changes are also committed before finished then it will also be applied in the full load otherwise the 100k changes will go to CDC.

Another example, for a full load takes 12 hours, then updates during the 12 hours full load window are also applied. Note- these two examples assume you have CDC enabled in the task.

If CDC is turned off during a full load task, then Replicate will not capture the cached events.

Environment

• Qlik Replicate 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

This article will guide you on how to check audit logs to see users' activity on object/sheet/app.

First of all, we would need to enable Audit Logs on Qlik Sense side, to do so, you can follow this guide.

Once done all the steps from the above's guide, then we can check all user activity on object/sheet/level through the Operations Monitor app (from Qlik Sense 2019 release).

In the example below we will see a graphic example of how to check this information from Audit Logs.

User with ID "f9b8183a-bc07-4571-8ccb-94f7a1c5d9db" navigates into app with ID "1e4a22db-7395-46b3-bd43-78bc4cef811f" and then clicks on sheet with ID "1e4a22db-7395-46b3-bd43-78bc4cef811f" and finally selects a dimension:

User performing selections on an app

As we enabled Audit Logs, all traces coming from users selections will be logged on this path location: C:\ProgramData\Qlik\Sense\Log\Engine\Trace\ServerName_Audit_Engine.txt

Now we can check the audit logs directly from Operations Monitor app:

1. Go to Qlik Sense Hub
2. Under streams on the left hand side, click on "Monitoring apps"
3. Then click on "Operations Monitor" app
4. Then we can filter the Audit Logs we enabled before so we can check which actions have been performed on sheet/app level by any user
5. In the example we can see in the gif below, we are performing the following selections to filter:
   1. We first filter by app (where we performed the selections on the bar chart)
   2. Then the gif also shows more filter examples that you could use to filter your data from Audit Logs

Checking logs through the Operations Monitor app

Furthermore, you could also check from logs the object ID and action performed on it on the following columns from C:\ProgramData\Qlik\Sense\Log\Engine\Trace\ServerName_Audit_Engine.txt:

Checking object ID and action performed

Environment

Qlik Sense Enterprise on Windows 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content 

How to enable Audit Logging in Qlik Sense Enterprise on Windows

Issue:

When attempting to connect to a new Direct Access Data Gateway data source within the load script editor of a Qlik Application, the new data connection test fails.

When reviewing the Data Gateway logs at "C:\Program Files\Qlik\ConnectorAgent\data\logs" , the following error is discovered:

ERROR partner 'myremotedataserver.com:3350' not reached"

Environment

• Direct Access Data Gateway

Diagnosis:

• Open windows powershell
• Type: (without quotes and replace xxxx with the port in question)
  • "tnc qlikserver3.domain.local -port xxxx"

Expected Result:

Resolution:

• If the above port test fails following the message 'waiting for connection'  the identified 'blocked' communications port found in the Data Gateway logs must be opened on your network firewall.
• Once the port is opened, retest your Direct Access Data Gateway connection.
• You should now see 'test succeeded '

Cause

• All network ports closed by default in a highly secure network. This including explicitly blocked ports to external data sources (such as SAP SQL connector port 3350), when required for data gateway source data connectivity, must be re-opened on the network firewall
• Ports recently closed due to updated network firewall policy blocking undocumented ports

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

If you want to submit a new idea or improvement request for Qlik's products, our Ideas section in the Qlik Community is open to all registered customers. 

Content:

• Where to find Qlik Ideation
• How to submit an Idea on the Ideation

Ideas are qualified and prioritized based on their value to improving and enhancing the Qlik product. For a successful request, please consider including a strong business case on why you think the change would be beneficial, including:

• Functionality: How does the product work now? How would you like it to work in the future? 
• Motivation: Why is the change important for your business?
• Importance: What is the impact if the feature request is not approved?
• Benefits: What is the impact if the feature request is implemented?

Where to find Qlik Ideation

1. Go to the Qlik Community
2. Log in!
3. After logging in, navigate to Ideation
   1. You can navigate there manually from (a) Ideation
   2. And (b) Browse and Suggest
      
      
      
      
4. Scroll down to locate the Ideation Landing Page / App
   
   
   
   For more information on the Ideation Dashboard and its functionalities, see About Ideation.
   
   
   

How to submit an Idea on the Ideation

Before you get started, review Ideation Guidelines: How to Submit an Idea for submission guidelines and eligibility information.

1. Go to the Ideas Site
2. Click the Suggest Features card
    
   
   
   
3. Provide us with as much detail as possible, including a descriptive subject and description.
4. Choose the appropriate Product Area.
5. And click Submit request.
   
   

Ideas and Improvement requests are reviewed by our product teams. While we strive to provide answers, we cannot guarantee a specific response time.  

Related Content:

Ideation on Community  
Ideation Platform Updates
Ideation Guidelines: How to Submit an Idea

This article explains how to save network logs in web development tools and the console logs from the browser and how to capture and read client-side response trace with HAR file analyzer.

For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.

Environment:

• Internet Explorer / Edge browser
• Google Chrome browser
• Mozila FireFox browser
• iPad/iPhone and Safari

Google Chrome and Microsoft Edge (new Chromium version):

1. Open developer tools (Menu > More tools > Developer tools or Ctrl + Shift + I or F12)
2. Select the Network tab.
3. Make sure that "Preserve log" is checked so that all traffic is captured.
4. Access or refresh the page traffic needs to be captured for or a problem should be reproduced in
5. Perform the steps to cause the behavior/issue
6. Click on the down arrow "Export HAR..." button or Right-click within the Network capture pane then choose 'Save as HAR with content' and save the .har capture locally.
7. Click on the Console tab > right-click > Save As > Save on the .log file. (Important)

To read the files, use a tool such as the HAR Analyzer https://toolbox.googleapps.com/apps/har_analyzer/

Firefox (41+) :

1. Go to Menu > Web Developer > Network
2. Reload the page you want to get the log for
3. Perform the steps to cause the behavior/issue. 
   Note: For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.
4. Right-click > Save All as HAR
5. Click on Console tab, Right-click > Select All.
6. Right-Click > Export Visible Message To > File, and save on a .txt file. (Important)

Internet Explorer and Microsoft Edge (older versions):

1. Open Developer Tools (F12)
2. Go to the network tab and click on the green arrow to start the tool
3. Refresh the page to capture the logs
4. Perform the steps to cause the behavior/issue
5. Note: For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.
6. Click 'Export captured traffic' icon and choose XML or HAR format.
7. Click on Console tab > right-click > Copy All, and paste it / save on a .txt file. (Important)

To read the files, use a tool such as the HAR Analyzer https://toolbox.googleapps.com/apps/har_analyzer/

iPad or iPhone Safari:

1. On the iPad or iPhone, open the Settings app and go to Safari, Advanced. Enable the Web Inspector.
   
   
   
   
2. On the Macintosh, launch Safari --> Preferences --> Advanced --> Show Develop menu in tab bar
   
   
   
   

Further Troubleshooting

1. On the iPad/iPhone, access the QlikView / Qlik Sense site you are having issues with
2. On the Mac, launch Safari --> Develop menu --> pick the name of the iOS device and select the site to inspect.
   
   
   
   
3. The Web inspector will launch. Select Networking and then, on the iOS device, start reproducing the issue.
   
   
   
   The Web Inspector can be used not only with iOS devices, but also with the iOS Simulator for Mac.  Please, check the "How to simulate iOS Safari on a Mac" article.

In this Webinar, we covered how to approach a Qlik Sense Enterprise on Windows migration.

The session covers:

• How to Back-Up and Restore
• Managing Certificates
• Potential Pitfalls
• Automation Options
• If assistance is needed, Qlik Consulting would need to be engaged. Qlik Support cannot provide walk-through assistance with server migrations outside of a post-installation and migration completion break/fix scenario.

Resources and Related Content:

Qlik Sense Migration: Migrating your Entire Qlik Sense Environment (Blog post)
Help.Qlik.Com Documentation: Backup and Restore Qlik Sense Enterprise on Windows
Qlik Sense Upgrade Guide
Qlik Admin Playbook

Q&A:

Q: Is it possible to migrate from a standalone installation to a clustered one? 
A: Yes. Once the Central Node has been moved to a new host, additional Rim nodes can be added as usual through the QMC. 

Q: What about the personnal objects created by users (sheets, bookmarks, ...) ?  Are they included in the QSR backup ? 
A: All user objects as well as base sheets are included both in the Apps themselves as well as in the QSR. 

Q: Is this possible to migrate one repository to another server and merge the repository with another one? 
A: Not through the procedure outlined in this webinar. If your goal is to merge content from multiple sites, or seamlessly migrate content, I recommend reaching out to your Account Manager and discuss Qlik Mission Control platform. 

Q: Would the steps given here change if postgres is installed on a stand-alone server?
A: The only steps that would change would be the backup/restore for the DB itself, as this would have to be performed locally on the DB host. Additionally, if the DB location has changed, the QRS connection strings will have to be updated via QlikSenseUtil. 

Q: Is it necessary to have the same release on both servers before migrating ? Or is there compatibility between versions of QlikSense ? 
A: You can restore a database from a previous version on a newer Qlik Sense release and the system will update the internal objects automatically, however the reverse is not possible. It is recommended to perform the upgrade in place, before migrating the server. 

Q: Is it possible to restore without certificate ? 
A: Yes, Trust Root and Qlik Client certificates can be recreated from scratch, however as mentioned during the call, all internal metadata values that were previously encrypted, such as data source connection strings, would have be updated via the QMC by re-entering the connection password and saving. 

The Qlik Enterprise Manager has two licensed modules:

• Replication Management - Enables design, customization, monitoring, and control of Replicate tasks as well as Replicate Server management.

• Replication Analytics - Provides measurements of server and task metrics over a specific time-period.

To remove the Replication Analytics license:

A sqlite editor and knowledge on how to use it is required for this change, such as the DB Browser for SQLite: https://sqlitebrowser.org/

1. Take a backup of the Qlik Enterprise Manager repository. If the manual removal of the license fails, re-install Qlik Enterprise Manager and restore the backup without applying the Analytics license.
   
   To back up the repository, run the following command from a command line (as administrator)
   
   aemctl repository export -f C:\temp\qem_repo_202205.json -w
   

   The backup step is crucial. Always back up your setup before proceeding with database changes.

2. Stop the Qlik Enterprise Manager service
   
   
3. Using a DB Browser for SQLite, open cfgrepo.sqlite
   
   Default location: C:\Program Files\Attunity\Enterprise Manager\data\cfgrepo.sqlite
   
   
4. Go to Browse Data
   
   
5. Choose objects in the Table drop down
6. Locate the Replication Analytics record
   
   
7. Right-click the Replication Analytics records and click Delete Record
   
   
8. Click Write Changes in the main SQLite menu
   
   
9. Close SQLite 
   
   
   
   
10. Start the Qlik Enterprise Manager Service

To hide the Replication Analytics dashboard:

The main Analytics tab is shown by default, regardless of whether or not you have registered a Replication Analytics license. If you do not intend to use the Replication Analytics module, you can hide the tab by either clicking the Hide Analytics Dashboards link in the Analytics tab or by following the procedure described below.

This option is only available if no Replication Analytics license is registered.

To show/hide the main Analytics tab:

1. In the Qlik Enterprise Manager Console, Click Settings (cogwheel on the right)

2. Select the Licenses tab.

3. Select the Replication Analytics sub-tab.

4. Clear or select the Hide Analytics Dashboards check box as required.

   Information note

   

5. Click Save.

Related Content

Registering and managing licenses 

Upgrading Qlik Sense Enterprise on Windows does not automatically upgrade the bundled PostgreSQL version. New versions of PostgreSQL are only deployed during a new install. This means upgrading from, for example, Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.

For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:

• Move Qlik Sense database to standalone PostgresSQL database in which case you will have control of which PostgreSQL version is deployed as long as it is supported by the system requirements
• Continue to use the bundled PostgreSQL with version 12.5 (see the process below)

Content:

• Step 1: Upgrading your Qlik Sense site
• Step 2: Backing up your Qlik Sense site
• Step 3: Uninstall Qlik Sense on the central node
• Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node
• Step 5: Restoring your Qlik Sense site

The information in this article is provided as-is and to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.

It is highly recommended to test this process in a test environment to get familiar with it.

Step 1: Upgrading your Qlik Sense site

The first step is to upgrade your environment to Qlik Sense Enterprise on Windows May 2021 following the steps and recommendations provided on this link.

Once the upgrade is done make sure your Qlik Sense site is completely operational.

Step 2: Backing up your Qlik Sense site

At this point, you have an operational Qlik Sense site running on Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.

The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.

Step 3: Uninstall Qlik Sense on the central node

You will now need to uninstall Qlik Sense from the central node following these instructions.

During the uninstall:

• Have all rim nodes stopped.
• Don't check the box Remove Qlik Sense demo apps, certificates, and data folders.
• After uninstall and before reinstall rename C:\programdata\qlik to C:\programdata\qlik.old and rename C:\program files\qlik to C:\program files\qlik.old (if you changed it on another drive adjust accordingly)

Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node

Now that Qlik Sense Enterprise on Windows May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5. Instructions available here.

• select the same host name and database settings as before
• The file share can point at a temporary one since you will take the original one again after restoring the QSR database in step 5.

Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.

Step 5: Restoring your Qlik Sense site

You now have a clean Qlik Sense Enterprise on Windows May 2021 deployed on your central node with PostgreSQL 12.5. You now need to restore your environment to retrieve all your configurations and apps.

Please follow the Restoring a Qlik Sense site (including the certificates).

Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.

pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;

pg_restore: warning: errors ignored on restore: 1

Once the environment is restored, you should be able to start your central node and rim nodes successfully.

Environment

Qlik Sense Enterprise on Windows May 2021 and later

This article explains how the user can manage the queued reloads using automation by retrieving all the reloads in the tenant and viewing the reloads that are in queued state and can cancel the less important reloads.

Environment

• Qlik Application Automation

Automation Configuration

1. Retrieve all the Reloads using the Raw API request block of the Qlik cloud service connector by inputting reloads as a path.
2. Filter the reloads with the status Queued and Reloading by using a Filter block.
   
   
3. Retrieve the app details for the particular reloads using the Get App information block, retrieve the required information such as ReloadTaskID, AppName, AppID, and Status, Sec in Status, and store it in a Variable block.
   
   
   
   
4. Check if the space of the apps is empty or not and add the applicable space type to a variable.
   
   
5. Add the Reload task object to a variable.
   
   
   
   
6. Filter the reload apps in a Queued state in Private space using the Filter block with the condition SpaceType is equal to Private.
   
   
7. Check if the filter list is not empty, If yes, configure the Reloads IDs that are queued and use the Inputs block to make the IDs to be selected by the user to cancel them.
   
   
8. Use Raw API request to cancel the reloads and output them.
   
   

    

Example output

Amazon Bedrock is a fully managed service that makes base models from Amazon and third-party model providers accessible through an API.

This article explains how the Amazon Bedrock connector in Qlik Application Automation can be used within Qlik Cloud.

Content:

• Authentication
• AWS Setup
• Qlik Cloud
• Available blocks
• Examples for the Invoke Model Endpoint
• Example 1: Using amazon.titan-text-express-v1
• Example 2: Using amazon.titan-tg1-large
• Example 3: Using stability.stable-diffusion-xl (Text to Image)

Authentication

AWS Setup

By default, users and roles don't have permission to create or modify Bedrock resources. They cannot perform tasks using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles.

To learn how to create an IAM identity-based policy by using these sample JSON policy documents, see Creating IAM policies in the IAM User Guide.

1. Open the AWS console
2. Navigate to Identity and Access Management (IAM) 
3. Click Create User and enter the new username. 
   
   Optionally, you can also give separate console access to the user.
   

   
   

4. In the Create User editor, you can select one of the three options.
   
   For our example, let’s select the highlighted option Attach policies directly.
   
   
   
   
5. Scroll down. In the Permissions Policies text box, type and search for Bedrock Full Access. 
   
   
   
   
6. (Optional) Expand Set permissions boundary - optional and set Use permissions boundary to control the maximum permissions 
   
   Review the on-screen text for details.
   
   
    
7. Review and create user.
8. Navigate to the Security Credentials tab.
9. Click Create Access Key.
   
   
   
   
10. For Use Case, click Third-party service and follow the recommendations. A description tag is optional.
11. Click Create Access Key
12. Copy the Access Key and Secret Access Key values.
    
    Store them safely. The Secret Access Key will only be shown once. See Access key best practices onscreen. 
    
    
    

     

Qlik Cloud

1. Open Qlik Cloud
2. Navigate to My Automations
   
   
   
   
3. Switch to the Connections tab
   
   
   
   
4. Click Add new connection.
5. Search for Amazon Bedrock and click Add.
   
   
   
   
6. Provide the access key and secret access key and specify where your AWS region is located.
   
   

Available blocks

The Amazon Bedrock connector consists of the following blocks:

• Invoke Model
• List Foundation Models
• List Custom Models
  
  

Examples for the Invoke Model Endpoint

Example 1: Using amazon.titan-text-express-v1

1. Drag and drop the Invoke Model block from the left-hand side menu.
   
   
2. In Model ID, enter amazon.titan-text-express-v1 or choose it from the lookup dropdown. 
   
   
3. In Body, enter:
   
   Key: inputText
   Value: a prompt of your choice for testing. In our example, we use Hello, what is the date today?

3. Run the block and review its output in the History tab
   
   

Example 2: Using amazon.titan-tg1-large

1. Drag and drop the Invoke Model block from the left-hand side menu.
   
   
2. In Model ID, enter amazon.titan-tg1-large or choose Amazon Titan Text Large from the lookup dropdown. 
   
   
3. In Body, enter:
   
   Key: inputText
   Value: a prompt of your choice for testing. In our example, we use Hello, what is the date today?
   
   or
   
   Switch to Raw input and design a JSON based on the same:
   
   {
   "inputText":"Picture of a bird"
   }
   
   
   
   
4. Run the block and review its output in the History tab

Example 3: Using stability.stable-diffusion-xl (Text to Image)

1. Drag and drop the Invoke Model block from the left-hand side menu.
   
   
2. In Model ID, enter stability.stable-diffusion-xl or choose Stability AI Stable Diffusion XL from the lookup dropdown. 
   
   
3. In Body, switch to Raw Input and design the following JSON based on a prompt of your choice:
   
   {
   "text_prompts":[{"text":"A lighthouse on a cliff","weight":0.5}]
   }
   
   
   
   
4. Run the block and review its output in the History tab
   
   
   
   
5. To test this use case, copy the base64 output and paste it into a Base64 to Image converter
   
   

This article covers the usage of the Qlik Application Automation cloud storage blocks and gives design flow examples which apply them. You can also download an example JSON using Google Cloud Storage, and we have compiled a list of links for more in-depth platform connections and atypical usages.

Content

• The Available Blocks
• Verify if File Exists / Delete File Example
• Supported Platforms and Connectors

The Available Blocks

Selecting Cloud storage when creating your automation will present you with the following list:

• Open File
  
  The open file block is a read-only block that is used together with the "Move file", "Copy file" and "Read data from a file" blocks. It requires a valid connection to a cloud storage platform or a URL link.
  
  
• Create File
  
  As the name implies it creates a new file at the suggested location. If the file already exists the automation run will end up in failure.
  
  Warning: this block cannot be used if a file with the same filename exists at that same location. In order to do that you will need to use the overwrite flow rules at the end of this article.
  
  
• Copy File
  
  This block copies the output from an "Open file" block and sends the stream to a given source path on the target platform. As mentioned now and beforehand, this block needs to be preceded by an "Open file" in the automation flow.
  
  
• Read Data From File
  
  Reads data from a file opened with the "Open file" block but what is different from the previous one is that the data stream is mostly used only when you need to use the stream for other blocks apart from the native file blocks or to update other files. This block it has several modes of reading data:
  • Automatic: given the file type and contents we try to approximate the algorithm to use and try to apply it to the file
  • CSV: mostly used in conjecture with spreadsheet files and you can choose your own headers and separators to be used in the reading algorithm
  • JSON: allows you to fully utilize the Automations format in order to use the read data easier inside an automation
  • RAW: reads the file line by line (mostly used for text files)
    
    
• Write Line To File
  
  This block writes data to a newly created file with the "Create file" block. As mentioned previously, this block also has several modes in which to write the data stream:
  
  
  • Automatic: given the file type and contents we try to approximate the algorithm to use and try to apply it to writing to the file
  • CSV: mostly used in conjecture with spreadsheet files and you can choose your own headers and separators to be used in the writing algorithm
  • JSON: allows you to fully utilize the Automations format in order to use the write data easier inside an automation
  • RAW: reads the file line by line (mostly used for text files)
    
    
• Save And Close File
  
  The block is used to close opened files by the use of the "Create file" block. You will need to use this block in order to see the target result on the cloud platform.
  
  
• Delete File
  
  Will delete the file with the filename given found at the target path/location. Mostly used in the overwrite file flow implementation.
  
  
• Move File
  
  Has mostly the same functionality as the "Copy file" block but instead of leaving the source file at the initial platform, it deletes it.
  
  
• Check If File Exists
  
  Verifies the existence of the file with the given filename at the target path/location. Again this is mostly used in the overwrite file flow protocol.
  
  
• List Files
  
  Simply shows you all the files found at the given target path/location.

Verify if File Exists / Delete File Example

Here is an example of how to verify if a file exists prior to creating a new one. This is specifically important when you set up an automation meant to save your result in a target file that might or might not be at the location suggested. Since you cannot create a new file if a previous one exists, you will need to apply the following to your automation:

You can verify if the file exists initially, and, based on the response from that block, either simply create a new file or delete the old file and create a new one to write data to.

Supported Platforms and Connectors

And last but not least, this is a list of supported platforms for the native blocks as well as links to how to connect to them as well as more quirky details they have.

• Amazon S3
• Dropbox
• FTP/SFTP
• Google Cloud Storage (with or without a service account)
• Microsoft Onedrive
• Microsoft Sharepoint
• HTTP (just for the open file block)
• Microsoft Azure Blob Storage

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

• https://www.ldapadministrator.com/download.htm
• LDAP Admin - Windows LDAP manager 

1. Install LDAP Browser on same machine as QlikView Server, NPrinting or Qlik Sense Enterprise
2. Connect LDAP browser to directory service
3. Validate that connection can be established
4. Browse the person and group records to validate that they can be retrieved

When all steps above can be completed successful the connection is confirmed as valid. Apply the directory path, username, and password in the QlikView, NPrinting or Qlik Sense LDAP configuration. Assistance with modifying filters and ports for LDAP and Active Directory is not in the realm of the Qlik Support SLA.

Another recommendation is to use the ADUC Module from the server and test your LDAP filters there, outside of Sense. This can be added through Roles and Features.

It's also suggested to check if you have a non-default domain policy set in active directory that enforces all LDAP authentication to be secured with SSL. This policy on the domain controller is: "Domain controller: LDAP server signing requirements" and if set to "Require signing" the LDAP data-signing option must be negotiated. The customer's IT Dept will need to verify.


Note: Qlik Support assists in diagnosing user directory imports, however if a new LDAP filter is applied using the User Directory Connector feature of the QMC, and the users are not imported, then this is considered an environmental-related issue and Qlik Consulting Services will need to be elected by clients if they'd like further assistance. Qlik Support is for break/fix of embedded Qlik features and any external or third-party integrations or interactions requires consulting services to assist.

Related Content:

• Qlik Sense on Windows: Configuring and testing LDAP filters for User Directory Connector

• Sync Active Directory users from multiple domains with Advanced LDAP - Qlik Sense Enterprise on Windows

• How to connect to Active Directory using the Generic LDAP Connector

• QlikView: How to configure LDAPS with the Directory Service Connector

• Qlik Sense: User Directory Connector - LDAPS Support and Testing

• How to Filter Active Directory users when Synchronizing them with Qlik Sense Users

• How to get LDAP filters for Active Directory groups from users already in Qlik Sense

• User Directory Connector is configured and users are syncing, but authentication fails

This article explains how a reload task chain can be built that will run longer than the maximum automation run limit of 4 hours. 

This is an advanced article, if you’re new to automations or task chaining, I suggest you first read this basic article.

Content:

• General idea
• Preparation
• Automation 1: Task Chain Initiator
• Automation 2: Task Chain Manager
• Results
• Bonus: reducing total executions of automation

General idea

The maximum run time of an automation is 4 hours. This can be a problem when you want to build a task chain of multiple reloads of big apps that could take longer than that. To solve this, we'll build a system of two automations that run together:

Automation 1: Task Chain Initiator, this automation will run once and start the task chain. It will trigger the first app reloads.

Automation 2: Task Chain Manager, this automation will be scheduled to run every 5 minutes. It will verify if any reloads have finished, whether they were successful and if any new reloads should be triggered.

The Task Chain Manager automation will need to know which reloads were triggered by the Task Chain Initiator and will need a way to store which reloads it already processed in previous runs. In other words: these automations need some sort of state to track the progress of the reload task chain. We’ll use Google Sheets for this, but of course, feel free to use any other cloud storage tool.

Preparation

The state will be stored in one file and divided over 4 sheets. Go ahead and create a new file in Google Sheets.

Sheet 1: Apps for initial reload, this sheet contains the ids and names of the apps that should be reloaded in the first automation. They will be executed by the Reload Initializer automation and run in parallel. Add a new sheet to the file you created, give it the name “Apps for initial reload” and add each app's id and name as in the below example. The order of the apps in the sheet is ignored.

Sheet 2: Queued reloads, this sheet will keep track of which apps were already triggered for reloading.

Add the sheet to the file and name it “Queued reloads” but don’t fill in any fields, the content of the sheet is autogenerated by the automations.

Sheet 3: Finished reloads, this sheet keeps track of all reloads that have finished, it contains their id, name, the status of the reload, and the reload log. Add the sheet to the file and name it “Finished reloads” but don’t fill in any fields, the content of the sheet is autogenerated by the Task Chain Manager automation.

Sheet 4: Chained reloads, this sheet dictates which apps should be reloaded after certain apps finished reloading. Add a new sheet to the file and name it “Chained reloads” specify the order in which apps should be executed.

The order of the rows in the sheet is ignored, the sheet is processed as follows:

If a reload has finished for an app from column “First_id”, then trigger a new reload for the app that’s specified in the column “Next_id” on the same row.

Add this sheet to the file and specify the apps as in the example below:

Automation 1: Task Chain Initiator

This automation will only run once at the beginning of the full task chain process, it will execute the following steps:

1. First, it will clear the Queued reloads & Finished reloads sheets, this will remove all data from previous task chain executions.
2. Next, it will add headers to these sheets
   1. Examples of the generated headers in the Queued reloads sheet:
      
      
      
      
   2. Examples of the generated headers in the Finished reloads sheet:
      
      
      
      
   3. Your automation should now look like this:
      
      
      
      

       

3. After initializing these sheets, the automation will get all apps from the Apps for initial reloads sheet and trigger a reload for each of them in parallel (by setting the Run Mode in the Do Reload block to ‘Start reload and continue’).
   1. Each app’s id, name, and reload id are written to the Queued reloads sheet:
      
      

       

   2. This part of the automation looks like this:
      
      

Note: an export of this automation is attached to this article as a JSON file named "Task chain initiator.json".

Automation 2: Task Chain Manager

This automation will run on a schedule and will be the engine of our task chain process. Feel free to adjust the schedule according to your needs. On each run of the automation, the following steps will be executed:

1. Get all records from the Queued reloads sheet, the Finished reloads sheet and the Chained reloads sheet.
   
   
   
   
   1. Tip: we won't use the loops on these blocks, right-click these blocks and choose "hide loop" to make your automation smaller.
2. Compare queued & finished reload records to find all apps that are in the Queued reloads sheet but not in the Finished reloads sheet. This will return a list of all apps from the queue that haven’t yet finished. Make sure to configure the settings of the Compare Lists block as follows. (List 1 should contain that queued reloads and list 2 should contain the finished reloads)
   
   
   
   
   
3. For each record returned by the Compare Lists block (= unfinished reloads), execute a Get Reload Record block to get the reload status and use a Case block to verify if the reload has finished:
   
   
   
   
   1. The reload finished successfully (status == SUCCEEDED):
      1. Write the app & reload information to the Finished reloads sheet.
      2. Use a filter list block & filter the records from the Chained reloads sheet. Filter it to get all records where First_id == the id of the app of the reload that succeeded.
      3. For each record returned by the Filter List block, trigger a new reload with the Do Reload block and write the reload id to the Queued reloads sheet.
      4. This part of the automation should look like this:
         
         
         
         
   2. The reload failed (status == FAILED):
      1. Write the app & reload information to the Finished reloads sheet.
      2. Optionally, send an email or a Slack message with the reload log.
      3. Configure this part like this:
         
         
         
         

Note: an export of this automation is attached to this article as a JSON file named "Task chain manager.json".

Results

The reloads in the Finished reloads sheet will look like this:

Bonus: reducing total executions of automation

When scheduled every 5 minutes, the "Task Chain Manager" automation will generate 288 daily runs. This bonus paragraph explains how the number of total runs can be reduced. Instead of having an automation that has many executions that run short, we'll build an automation that has only a few executions that run for a longer time.

1. Take all blocks from the Task Chain Manager automation and place them inside a Loop block. Use the explode formula to create a loop in the Loop block's List input field. Specify a comma-separated list of 30 items. For example: 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30.
   
   
   
   
2. Then add a Condition block at the end of the automation right after the blocks from the original Task Chain Manager automation. Configure the block to validate the number of items returned by the Compare Lists block (use the Count formula for this). If this equals 0, the Task Chain has finished. Add an Exit Loop block to stop the automation.
3. Now add a sleep block after the condition to sleep for 60 seconds.
   
   
   

    

4. Finally, change the automation's schedule to run every minute. This will reschedule the next run of the automation 1 minute after the previous automation has finished. The automation will now run for 30 minutes (30 loop executions x 1 minute from the sleep block) + the total execution time of the other blocks in the loop.
   
   

Notes

• You can easily modify this automation to send messages to Microsoft Teams or emails.
• If multiple apps should be reloaded after a certain app’s reload is finished, just add multiple rows to the Chained reloads sheet with each time a different Next_id
• In the Task Chain Manager automation, if the output of the Compare Lists block is empty, the task chain has finished. Feel free to add a condition block to the end of this automation to verify this and alert your team.

The information in this article is provided as-is and to be used at your own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Related Content

How to task chaining with Qlik Application Automation
How to import and export automations

This article explains how you can Delete spaces in Qlik Cloud Services using Qlik Application Automation. Multiple spaces can be deleted during one run. As when deleting a space via the user interface, this will also delete any apps, data files or other content within the space(s) using the relevant blocks for those content types.

For information about spaces in Qlik Cloud, see Navigating Spaces.

This automation is not designed to be triggered using a webhook or on a schedule. It has been designed with manual user input in mind and requires multiple confirmations.

If you use your own automation to delete spaces, know that deleting a space via the space blocks will not delete the content in the space, and will instead result in that content being orphaned in the tenant. Leverage the examples in this automation to first delete content from spaces prior to deleting the space.

Once deleted, spaces, apps, or data files cannot be recovered.

Content:

• Prerequisites
• Overview
• Start
• Confirm selected spaces
• Delete apps
• Delete data files
• Delete spaces
• Finalize
• Running the Automation
• Related Content

Prerequisites

This automation assumes you have a TenantAdmin role.

Overview

The automation is divided into five sections: 

1. Start 
2. Confirm selected spaces
3. Delete apps
4. Delete data files
5. Delete spaces
6. Finalize

Start

The Start section retrieves all available spaces and prompts you to select what spaces you want to delete.

Overview:

Setting it up:

1. The List Spaces block retrieves all spaces on the tenant that you have access to.
2. The Filter List block filters spaces that you have the delete permission to.
   
   This is achieved using a condition configured such as this:
   
   Condition
   If meta.actions
   list contains
   delete
   
   
   
   
3. The Transform List block reformats the space list to improve readability in the input block (id, name and type are kept).
   
4. The Inputs block adds a prompt for selecting the spaces to delete.
   
   Multi-selection is allowed:
   
   
   
   
5. A Go To Label block moves to the next section of the automation.
    
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.

Confirm selected spaces

This section provides the possibility to review the selected spaces before deleting them.

Overview:

Setting it up:

1. The Label block is named Confirm Selected Spaces and this must also be configured in the Go To Label block from the previous section.
2. A Loop block loops over selected spaces.
3. Within the loop, a List Apps block retrieves apps in the space. The output of this block is stored in the variable appList which is used for reviewing what apps exist within the spaces that will be deleted.
4. To retrieve the connectionId for data files in this space, a Raw API Request block is used. The path in the block is configured to use data-files/connections and the HTTP method is set to GET. A query parameter is also added where the key is set to spaceId and the value is set to {$.loop.item}.
5. The connectionId retrieved in the previous step is used to retrieve data files in this space using the List Data Files block. The output of this block is stored in the variable dataFileList which is used to review the data files that exist within the spaces flagged for deletion.
6. After the loop, an Output block displays which spaces will be deleted.
7. We use an Inputs block to allow user confirmation before deleting apps, data files and other content within the selected spaces:
   
   
   
   
8. A Go To Label block moves to the next section of the automation.
   
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.
   

Delete apps

Once deleted, spaces, apps, or data files cannot be recovered.

This section deletes all existing apps inside the space(s). A space cannot be removed before all apps are deleted.

Overview:

Setting it up:

1. The numeric variable iter tracks how many apps are deleted. 
2. A Loop block loops over the items in the variable appList.
3. The variable iter is increased by 1 per loop iteration.
4. The block Get App Information retrieves the app name based on the app id. 
5. The app is deleted using the block Delete App.
6. A deleted app status will be presented using the string variable message. 
7. The delete apps status will be presented using an Output block:
   
   
   
   
8. The delete apps status will also be presented using the block Update Run Title:
   
   
   
   
9. A Go To Label moves on to the next section of the automation. 
   
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.

Delete data files

Once deleted, spaces, apps, or data files cannot be recovered.

This section deletes all data files within the selected space(s).

Overview:

Setting it up:

1. The numeric variable iter tracks of how many data files are deleted. 
2. A Loop block loops over the items in the variable dataFileList.
3. The variable iter is increased by 1 per loop iteration.
4. To retrieve the data file name for datafiles we use a Raw API Request block configured such as this:
   
   Path: data-files/{ $.loop3.item }
   
   HTTP Method: GET
   
   
   
   
5. The data file is deleted using the block Delete Data File.
6. A deleted data file status will be presented using the string variable message. 
7. The deleted data file status will be presented using an Output block:
   
   
   
   
8. The delete data file status will also be presented using the block Update Run Title:
   
   
   
   
9. Finally, a Go To Label block moves on to the next section of the automation. 
   
   Before the Go To Label block can be configured, the targeted Label must already exist. This is done in the next section.

Delete spaces

Once deleted, spaces, apps, or data files cannot be recovered.

This section deletes all selected spaces. 

Overview:

Setting it up:

1. The numeric variable iter tracks of how many spaces are deleted. 
2. A Loop block loops over the selected spaces.
3. The variable iter is increased by 1 per loop iteration.
4. To retrieve the name of the space we use a Lookup Item In List block.
5. The space is deleted using the block Delete Space.
6. A deleted space status will be presented using the string variable message.
7. The delete space status will be presented using an Output block
   
   
   
   
8. The delete space status will also be presented using the block Update Run Title.

Finalize

This section wraps up the automation and updates the final status of the automation run. 

Overview:

Setting it up:

1. A summary of how many apps, data files and apps have been deleted is presented using the string variable message.
2. The summary is presented using an Output block:
   
   
   
   
3. The summary is also returned using the block Update Run Title:
   
   

Running the Automation

1. On run, choose which space to delete. Be careful not to select spaces you want to keep:
   
   
   
2. Once you have selected the space or spaces, you are prompted to confirm the deletion of apps, data files and other content that exists within this space or spaces. If you don't want to proceed you can stop the automation. If you want to proceed you need to click on the green confirmation button:
   
   

Related Content

Navigating Spaces
Managing permissions in shared spaces 
Managing permissions in managed spaces 

Environment

Qlik Application Automation
Qlik Cloud

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.