When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

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.

The default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:

1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)

   [globals]
   LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
   (...)
   MaxHttpHeaderSize=16384

2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.

Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows 

From Qlik Sense February 2023 onwards, apps listed in the Qlik Sense Management Console (Apps view) are now represented with clickable links. Clicking them will open the app directly on the hub.

This means the app names are no longer plain grey text but are now formatted as links (blue, underline). See Apps for details.

Example: 

To disable clickable links in the Management Console:

1. On your Qlik Sense Enterprise Server, go to C:\Program Files\Qlik\Sense\CapabilityService
2. Open capabilities.json (using for example Notepad++)
3. Search for flag QmcOpenAppInHub 
   Example:
   {
   "contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874",
   "originalClassName":"FeatureToggle",
   "flag":"QmcOpenAppInHub",
   "enabled":true
   },
4. Change "enabled":true to "enabled":false
5. Save and close the capabilities.json file
6. Restart the Qlik Sense Service Dispatcher service from the Windows services console
7. The links are now disabled

Known Limitation

Using only a custom virtual proxy prefix is currently not compatible. The default virtual proxy prefix must be accessible as the link generated will always refer to it.

Qlik is actively working on improving this feature: SHEND-1197.

Environment

Qlik Sense Enterprise on Windows February 2023 and above

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 Automate 

Talend Data Stewardship Installer for on-prem and Hybrid version could not redirect the gateway.url to correct host from IAM server or Cloud Server and got error page. 

Somehow, it points to localhost instead of the IP Server or HostName specified in the TMC->Configuration->TDS setting. 

Resolution

Temporary Workaround

1. Edit data-stewardship.properties file which is available in <install_folder>\tds\config folder and change gateway.url to correct IP/Host (The real IP of the server on which TDS is installed )
2. iam/data/client/tds-client.json file also needs to be updated by adding URL item with the correct IP/Host

Final Solution

Wait for new installer versions released after R2025-05 

Cause

It is a known bug from Installer level that IP/Host did not be propagated to the config of the Installed version of Talend Data Stewardship.

Internal Investigation ID(s) 

Internal Jira case ID: SUPPORT-3964

Environment

• Talend Data Stewardship 
• Talend Cloud 

Dates are processed to the target as 01.01.0101.

This occurs when running a Full Load from a SAP Hana Source Endpoint while the Log-based CDC Mode is set on the SAP Hana task and the DATE columns are empty.

Resolution

This behavior has been identified as a defect (RECOB-9893) in Qlik Replicate 2024.11 SP02 and previous versions. 

Fix Version

Install the latest Service Pack 2024.11 SP03 or any later releases.

If the latest Service Release is not available containing the Patch, contact Qlik Support. 

Internal Investigation ID(s):

RECOB-9893

Environment

• Qlik Replicate 2024.11 SP02

Old versions of RabbitMQ include multiple vulnerabilities. This article covers:

• CVE-2020-5419
• CVE-2022-31008
• CVE-2017-4967
• CVE-2019-11291
• CVE-2017-4965

They do not impact Qlik NPrinting.

Qlik NPrinting 2023 versions and later use RabbitMQ 3.12, which is not affected by these vulnerabilities.

How can I verify the RabbitMQ version my Qlik NPrinting install uses?

1. Open the folder C:\Program Files\NPrintingServer
   
   
2. Find the folder named Rabbitmq_server-** 
   
   This will show the deployed version.
   
   Example: C:\Program Files\NPrintingServer\rabbitmq_server-3.12.10

Environment

• Qlik NPrinting

A binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with:

General Script Error

or

Binary load fails with error Cannot open file

Before Qlik Sense Enterprise on Windows November 2024 Patch 8, the Qlik Engine permitted an unsupported and insecure method of binary loading from applications managed by Qlik Sense Enterprise on Windows.

Due to security hardening, this unsupported and insecure action is now denied.

Binary loads of Qlik Sense applications require a QVF file extension. In practice, this will require exporting the Qlik Sense app from the Qlik Sense Enterprise on Windows site to a folder location from which a binary load can be performed. See  Binary Load and Limitations for details.

Example of a valid binary load:

Binary [lib://My_Extract_Apps/Sales_Model.qvf];

Example of an invalid binary load:

"Binary [lib://Apps/777a0a66-555x-8888-xx7e-64442fa4xxx44];"

Environment

• Qlik Sense Enterprise on Windows November 2024 Patch 8 and any later releases

A Qlik NPrinting task contains a report with filters applied, either on the report itself, the recipients, or the task itself. 

Not all recipients receive the report, or the Qlik NPrinting task stalls. 

The log files display the following error:

Filters for request xxx produce an invalid selection.

Other related errors that may appear in the Engine logs when running reports with invalid selections include:

ERROR: Error processing request of type Qlik.Reporting.Engine.Messages.Requests.FilterMaterializationRequest for sense app <app id>. ERROR: Cannot apply filter Filters:...
Bookmark: , Void: False to current document data. Requested fields with evaluates are: F\<field name>
...
Error processing request of type Qlik.Reporting.Engine.Messages.Requests.FormulaNodeRequest for sense app <app id>. ERROR: System.TimeoutException: Method "EvaluateEx" timed out

Resolution

The reports are not being generated due to filter incompatibility.

To resolve this:

1. Review the filters referenced in the logs and cross-check them in the source QlikView or Qlik Sense documents.
2. Apply the Qlik NPrinting filters manually to confirm which selections are causing the issue.
3. Fix the filters and rerun the report task.

Cause

Qlik NPrinting will not generate reports when the applied filters are incompatible. It automatically checks for incompatible filters at the beginning of task execution and stops report generation if any are detected. This is a standard feature in all Qlik NPrinting releases.

Without this safeguard, QlikView or Qlik Sense would remove the incompatible selections and proceed, potentially generating a report containing all (or no) data, which may expose confidential information.

What are incompatible filters?

Common incompatible filters are:

Duplicate Filter Application

Applying the same filter to multiple locations (such as to both a user and a task) can result in a conflict. Depending on how the filters interact, double selections can lead to all (or no) data being shown. 

Removed or Non-Existent Filter Values

If a filter references a value that no longer exists in the source document, it becomes incompatible. For instance, if a filter was set to Country = "Germany" and the latest reload of the source data removed "Germany" from the Country field, the filter will no longer work.

Contextually Conflicting Filters (No Data in Common)

A filter might work independently, but it becomes incompatible when combined with other filters. For example, a filter for Country = "Germany" may function properly on its own. However, the selection is invalidated if you also apply Month = "April" if April has no data for Germany.

Environment

• Qlik NPrinting

This article provides an overview of how to send straight table data to email as an HTML table using Qlik Automate.

The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send straight table data to email as table' in the search bar, and clicking the Use template option.

You will find a version of this automation attached to this article: "Send-straight-table-data-to-email -as-HTML-table.json".

Content:

• Full Automation
• Automation structure
• Related Content

Full Automation

Automation structure

The following steps describe how to build the demo automation: 

1. Add a variable called 'EmailBody' to build the email body, and append the body opening tag and opening text of the email as value to this variable.
   
   
2. Add another variable called 'EmailStraightTable' and append the table opening tag together with the table header opening tag as a value to this variable.
   
   
3. Use the 'Get Straight Table Data' block from the Qlik Cloud Services connector to get data from the straight table for a specific app to be sent as an email. Specify app ID, Sheet ID, and Object ID input parameters. You can use the do-lookup functionality to find value for all these parameters. There is a limit of 100,000 records that can be retrieved through the 'Get Straight Table Data' block. This block will not work with other table types.
   
   
4. Add a 'Loop' block to loop over the keys from the 'Get Straight Table Data' block response which act as the headers of the HTML table. Use the '{getkeys: {$.GetStraightTableData}}' formula in the 'Loop' block.
   
   
5. Add the key/column name as the header of the HTML table in the 'EmailStraightTable' variable block. Outside the loop, add the 'EmailStraightTable' variable block, and append the table header closing tag, and table body opening tag as values to this variable.
   
   
6. Add a 'Loop' block to loop over all the values from the 'Get Straight Table Data' block response. Within the 'Loop' block add the following blocks:
   
   
   1. Use the 'EmailStraightTable' variable block and append the table row opening tag as a value to this variable.
   2. Use another 'Loop' block to loop over all values from the straight table for the current key/ column of the straight table.
   3. Next, use the 'EmailStraightTable' variable block and append the table data opening tag along with the column value for the corresponding key from the straight table which ultimately gives a single row with values for all the keys in each iteration and the table data closing tag as value to this variable.
   4. Use the 'EmailStraightTable' variable block and append the table row closing tag as a value to this variable.
      
      
7. Add the 'EmailStraightTable' variable block and append the table body closing tag with table footer tags as a value to this variable.
   
   
8. Add the 'EmailBody' variable block and append the 'EmailStraightTable' variable, which contains the final HTML table with straight table data, together with the email footer, and body closing tag as a value to this variable.
   
   
9. Add a 'Send Mail' block from the Mail connector to send an email with the above constructed HTML table that contains straight table data. Specify values for all the mandatory input parameters. Please connect to the SMTP server by adding a connection to the Mail connector.

An example output of the email sent:

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

Related Content

How to export more than 100k cells using Get Straight Table Data Block 

Environment

• Qlik Cloud Analytics
• Qlik Automate

This Techspert Talks session covers:

- What to plan for
- Migration Pathways
- Cloud Best Practices

Chapters:

• 01:20 - Cloud Tenant Locations
• 01:47 - Qlik Cloud Architecture
• 03:08 - Planning the migration
• 03:50 - Migration Journey
• 05:13 - Licensing Guardrails
• 06:39 - Migrating users, groups, and permissions
• 11:11 - Migrating apps
• 14:44 - Migrating the data connections
• 21:07 - Completed Migration
• 21:35 - 5 Key Take Aways
• 22:48 - Q&A: How to license sync with hybrid?
• 23:59 - Q&A: Best practices for 1 app migration?
• 24:47 - Q&A: What's included with license cost?
• 26:03 - Q&A: How to customize the UI?
• 26:45 - Q&A: How safe is the data in Cloud?
• 27:37 - Q&A: What are common stumbling blocks?
• 28:41 - Q&A: How are reload monitored?
• 29:28 - Q&A: What is the data size cap?
• 30:15 - Q&A: What cannot be migrated?

Resources:

• Qlik Cloud Best Practices
• Troubleshooting Qlik Data Gateway Direct Access
• Qlik Cloud Migration Center
• Qlik Professional Services
• Space-aware data source syntax examples
• Trust and Security at Qlik
• The Reload Analyzer for Qlik Cloud Customers
• Qlik Licensing Service Reference Guide
• Migrating NPrinting to Qlik Cloud Reporting

The user that runs the Qlik Sense Enterprise on Windows services is commonly referred to as the Qlik Sense Enterprise service account. The user is defined as the "Log On As" user in Windows service settings. 

In a multi-node deployment it is recommended to use the same domain user for all Qlik Sense services on all nodes the same deployment. 
NOTE: Qlik Sense Repository Database service is an exception, and is expected to always run as Local System.

Confirm the current Qlik Sense Enterprise service account;

1. Login to Windows Server on Qlik Sense node
2. Open Services manager in Windows
3. Sort by Name column
4. Scroll down to show all Qlik Sense related processes in the window
5. Confirm that all services except Qlik Sense Repository Database runs with the same "Log On As" user
6. Repeat above steps on all nodes in the same Qlik Sense site to confirm that the same user is applied 

Erlang/Open Telecom Platform (OTP) has disclosed a critical security vulnerability: CVE-2025-32433.

Is Qlik NPrinting affected by CVE-2025-32433?

Resolution

Qlik NPrinting installs Erlang OTP as part of the RabbitMQ installation, which is essential to the correct functioning of the Qlik NPrinting services.

RabbitMQ does not use SSH, meaning the workaround documented in Unauthenticated Remote Code Execution in Erlang/OTP SSH is already applied. Consequently, Qlik NPrinting remains unaffected by CVE-2025-32433.

All future Qlik NPrinting versions from the 20th of May 2025 and onwards will include patched versions of OTP and fully address this vulnerability.

Environment

• Qlik NPrinting

When upgrading Talend Studio to a newer patch level that is at or higher than R2024-12, those Snowflake jobs that have logging enabled may suddenly switch writing to the home directory (or users directory on Windows) instead of "/tmp" directory that the default file output.

If the home/users directory folder size has been restricted or there are other restrictions on the environment, those Snowflake jobs may fill up the home/users directory and error out outofmemory or get a Permission Denied Issue. 

Resolution

In order to continue collecting logs from the Snowflake JDBC driver, you should create a JSON file to configure your logging on the Jobserver/Remote Engine instance. This JSON file will tell the Snowflake Driver what logging level it should be using, where to write the log, and any additional configurations that may be required for the use case. Once created and stored in a location the Jobserver/Remote Engine can access, create an environmental variable called "SF_CLIENT_CONFIG_FILE" that points to the specific folder where the JSON file was written.

An example of a logging JSON file for Snowflake has been shared below:

###########################################################
#   Default Logging Configuration File
#
# You can use a different file by specifying a filename
# with the java.util.logging.config.file system property.
# For example java -Djava.util.logging.config.file=myfile
############################################################
############################################################
#   Global properties
############################################################
# "handlers" specifies a comma-separated list of log Handler
# classes.  These handlers will be installed during VM startup.
# Note that these classes must be on the system classpath.
# ConsoleHandler and FileHandler are configured here such that
# the logs are dumped into both a standard error and a file.
handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler
# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers.  For any given facility this global level
# can be overriden by a facility specific level.
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level = INFO
############################################################
# Handler specific properties.
# Describes specific configuration information for Handlers.
############################################################
# default file output is in the tmp dir
java.util.logging.FileHandler.pattern = /tmp/snowflake_jdbc%u.log
java.util.logging.FileHandler.limit = 5000000000000000
java.util.logging.FileHandler.count = 10
java.util.logging.FileHandler.level = INFO
java.util.logging.FileHandler.formatter = net.snowflake.client.log.SFFormatter
# Limit the messages that are printed on the console to INFO and above.
java.util.logging.ConsoleHandler.level = INFO
java.util.logging.ConsoleHandler.formatter = net.snowflake.client.log.SFFormatter
# Example to customize the SimpleFormatter output format
# to print one-line log message like this:
#     <level>: <log message> [<date/time>]
#
# java.util.logging.SimpleFormatter.format=%4$s: %5$s [%1$tc]%n
############################################################
# Facility specific properties.
# Provides extra control for each logger.
############################################################
# Snowflake JDBC logging level.
net.snowflake.level = INFO
net.snowflake.handler = java.util.logging.FileHandler

Cause

The change was done by Snowflake itself on the JDBC side, which can explain the driver changes, regardless of the Studio version being used. These changes are required for all Snowflake jobs that use a JDBC driver version higher than 3.14.4, which does get upgraded in Studio (and those affiliated Snowflake Components) from 3.13.30 to 3.18.0.

This can also apply for Studio instances older than R2024-12, where users have upgraded to a newer driver (such as 3.30.0) manually. 

Related Content 

• https://docs.snowflake.com/en/developer-guide/jdbc/jdbc-configure#logging-configuration-file
• https://community.snowflake.com/s/article/How-to-generate-log-file-on-Snowflake-connectors
• https://help.qlik.com/talend/en-US/patch-notes/8.0/r2024-12

Environment

• Talend Studio 
• Talend Data Integration 

You are experiencing a sudden failure of connections to data sources such as MySQL, Qlik Cloud, and Microsoft SQL Server in Talend Data Catalog. These connections were previously working correctly. When you test the connection, you receive the following error message:

"An error occurred in the remote service [-1,1] - MIMB execution thread ( ) was not found"

This issue can occur even if you can locally access the data sources with other tools, such as DBeaver.

Cause

The error message indicates that the Talend Data Catalog application is unable to connect to the bridge server. This is because the Remote Harvest Agent required to access your local data sources is either missing, has been deleted, or is not properly configured. The default server running in the cloud does not have access to data sources behind your firewall.

Resolution

To resolve this issue, you need to install and configure a new Remote Harvest Agent. This agent can be installed on the same server as your data source (e.g., MySQL) or on another machine that has access to it.

Here are the steps to follow:

Install the Remote Harvest Agent:

• Download the installation files for the Remote Harvest Agent.
• If you are installing on a Windows operating system, run the Setup.bat file.
• If you are installing on a Linux or Unix-like operating system, run the Setup.sh file.
• Follow the on-screen instructions to complete the installation.

Configure the New Agent in Talend Data Catalog:

• Once the agent is installed, open your Talend Data Catalog.
• Navigate to Manage Servers.
• Add the newly installed Remote Harvest Agent.

Use the New Agent for Harvesting:

• When configuring your data source connections, select the new agent you just added to harvest the data model.

These instructions are the same for both the cloud and on-premise versions of Talend Data Catalog. 

Additional Information

For more detailed instructions, you can refer to the following documentation:

• Configuring a remote harvesting server using the setup utilityConfiguring a remote harvesting server using the setup utility
• Configuring remote harvesting serversConfiguring remote harvesting servers

Note: Although these links pertain to version 8.0, the process remains identical for version 8.1.

Environment

• Talend Data Catalog (Cloud or On-premise)
• Connections to data sources like MySQL, Qlik Cloud, Microsoft SQL Server, Oracle DB

When using a Microsoft Azure ADLS as a target in a Qlik Replicate task, the Full Load data are written to CSV, TEXT, or JSON files (depending on the endpoint settings). The Full Load Files are named using incremental counters e.g. LOAD00000001.csv, LOAD00000002.csv. This is the default behavior. 

In some scenarios, you may want to use the table name as the file name rather than LOAD########.

This article describes how to rename the output files from LOAD######## to <schemaName>_<tableName>__######## format while Qlik Replicate running on a Windows platform.

In this article, we will focus on cloud types of target endpoint (ADLS, S3, etc...) The example uses Microsoft Azure ADLS  which locates remote cloud storage.

This customization is provided as is. Qlik Support cannot provide continued support for the solution. For assistance, reach out to Professional Services.

Resolution

1. Open and modify repctl.cfg 
   
   Default file location: C:\Program Files\Attunity\Replicate\bin
   
   Set enable_execute_user_defined_commands from false to true 
   
   Example: "enable_execute_user_defined_commands": true,
   
   
2. Download and install the latest release of the Azure CLI (v2.50.0 is used in this sample)
   
   
3. Add the az cli installation folder to Windows PATH enviornment. The default installation folder is "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin"
   
   
4. Restart the Qlik Replicate Server service. 
   
   
5. Create a text/batch file named myrename3_adls.bat and save it in the Qlik Replicate Server folder: C:\Program Files\Attunity\Replicate\bin
   
   Content of the file:
   

   @Echo on
   for  %%a in (%1) do set "fn=%%~na"
   echo %fn%
   set  sn=%fn:~4,8%
   echo %sn%
   az storage fs file move -p %1 -f johwg --new-path johwg/demo/%2.%3/%2_%3__%sn%.csv --account-name mydemoadlsgen2johwg --account-key Wbq5bFUohzfg2sPe7YW6azySm24xp4UdrTnuDSbacMi44fkn4UqawlwZCcn2vdlm/2u70al/vsWF+ASttoClUg==

   where  johwg is the Container Name. account-name and account-key are used to connect to ADLS storage. The values are obfuscated in the above sample.

6. Set the Microsoft Azure ADLS Target endpoint and configure it with the following settings: 
   
   

   General
       Storage Type       : Azure Data Lake Storage (ADLS) Gen2
       Container             : johwg
       Target folder       : /demo
   
   

   
   

   
   Advanced
       Post Upload Processing, choose "Run command after upload"
       Command name  : myrename3_adls.bat
       Working directory: leave blank
       Parameters             : ${FILENAME} ${TABLE_OWNER} ${TABLE_NAME}
   
   

7. Startup or Reload the Full Load ONLY task and verify the file output.
   
   In Azure Storage Explorer, it will typically looks like:
   
   
   
   Where SCOTT is the source table schema name, KIT is source table name, 0000000<n> is the unique incremental number.
   
   You can tailor the myrename3_adls.bat file for any particular needs.

Environment

Qlik Replicate  
Microsoft Azure ADLS target

Related Content:

Qlik Replicate and File target: How to rename output files LOAD######## to table name format on Windows
Qlik Replicate and File target: How to rename output files LOAD######## to table name format on Linux

The reload task fails with a message like this in the document log:

or

           2017-11-10 10:16:48 0454       WHERE isnum(Sequence#)
            2017-11-10 10:16:48      Error: Field 'Sequence#' not found
            2017-11-10 10:16:48      Execution Failed
            2017-11-10 10:16:48      Execution finished.

or
 

Sequence# field not found in 'lib://SHARE/Repository/Trace/SERVERNAME_Synchronization_Repository.txt' 

The steps below apply where it cannot find any field. The field that cannot be found includes but is not limited to CounterName, ProxySessionID.

Environment:

• Qlik Sense Enterprise on Windows and Qlik Sense Monitoring apps

Cause:

QLIK-35804: Occasionally when Qlik Sense services stop, they do not fully write to the logs in the expected format. 

Resolution:

Services need a restart

Restart the Qlik Sense services 

Last stop of services did not write logs in the expected format

Modify the License and Operations Monitor apps such that it will continue parsing logs even if it fails to fully parse a particular log.

1. When logged in to the server, import a new copy of the problematic app from C:\ProgramData\Qlik\Sense\Repository\DefaultApps (You will need to give it a new name, i.e. License Monitor (New))
2. Go to the Hub to the My Work section and open the application
3. Click on Open to go to the Data Load Editor
4. Go to the Run Logic section
5. It will initially look like below. For reference, the screenshots are from the Operations Monitor but the principle applies to the License Monitor as well even though the load script will look slightly different.
   
6. Wrap the section labelled working: with the following code:

   //begin ignoring errors parsing logs
   set errormode = 0;

   and 

   //end ignoring errors parsing logs
   set errormode = 1;

   This will look something like this:
   
   
7. Save the file
8. Reload from the Hub or QMC
   1. From the Hub: Click on the Load Data icon in the upper right hand corner
   2. From the QMC: Apps > Select the new License or Operations Monitor App > More Actions > Reload Now
9. Ensure that it has reloaded successfully
10. Delete the original License or Operations Monitor app
11. Rename the new copy, i.e. License Monitor (New) will be renamed to License Monitor
12. Publish the new app to the Monitoring Apps stream
13. Create a reload task to reload the new app. The default reload schedule for the default apps is to reload every hour, but you can set to this to be as frequent as your needs require.

Watch this space for when the feature has been successfully rolled out in your region.

This capability is being rolled out across regions over time:

1. May 5th: India, Japan, Middle East, Sweden (completed)
2. June 4th: Asia Pacific, Germany, United Kingdom, Singapore (completed)
3. June 9th: United States (completed)
4. June 12th: Europe (completed)
5. TBD: Qlik Cloud Government

With the introduction of shared automations, it will be possible to create, run, and manage automations in shared spaces. 

Content

• Allow other users to run an automation
• Collaborate on existing automations
• Collaborate through duplication
• Extended context menus
• Context menu for owners:
• Context menu for non-owners:
• Monitoring
• Administration Center
• Activity Center
• Run history details
• Metrics

Allow other users to run an automation

Limit the execution of an automation to specific users.

Every automation has an owner. When an automation runs, it will always run using the automation connections configured by the owner. Any Qlik connectors that are used will use the owner's Qlik account. This guarantees that the execution happens as the owner intended it to happen.

The user who created the run, along with the automation's owner at run time, are both logged in the automation run history.

These are five options on how to run an automation:

1. Run an automation from the Hub and Catalog
   
   
   
   
2. Run an automation from the Automations activity center
   
   

    

3. Run an automation through a button in an app
   
   You can now allow other users to run an automation through the Button object in an app without needing the automation to be configured in Triggered run mode. This allows you to limit the users who can execute the automation to members of the automation's space.
   
   More information about using the Button object in an app to trigger automation can be found in How to run an automation with custom parameters through the Qlik Sense button.
   
   
4. Programmatic executions of an automation
   
   
   1. Automations API: Members of a shared space will be able to run the automations over the /runs endpoint if they have sufficient permissions.
   2. Run Automation and Call Automation blocks
      
      
5. Note for triggered automations: the user who creates the run is not logged as no user specific information is used to start the run. The authentication to run a triggered automation depends on the Execution Token only.

Collaborate on existing automations

Collaborate on an automation through duplication.

Automations are used to orchestrate various tasks; from Qlik use cases like reload task chaining, app versioning, or tenant management, to action-oriented use cases like updating opportunities in your CRM, managing supply chain operations, or managing warehouse inventories.

Collaborate through duplication

To prevent users from editing these live automations, we're putting forward a collaborate through duplication approach. This makes it impossible for non-owners to change an automation that can negatively impact operations.

When a user duplicates an existing automation, they will become the owner of the duplicate. This means the new owner's Qlik account will be used for any Qlik connectors, so they must have sufficient permissions to access the resources used by the automation. They will also need permissions to use the automation connections required in any third-party blocks. 

Automations can be duplicated through the context menu:

As it is not possible to display a preview of the automation blocks before duplication, please use the automation's description to provide a clear summary of the purpose of the automation:

Extended context menus

• Start a run from the context menu in the hub
• Duplicate automation
• Move automation to shared space
• Edit details (owners only)
• Open in new tab (owners only)

Context menu for owners:

 

Context menu for non-owners:

 

 

Monitoring

The Automations Activity Centers have been expanded with information about the space in which an automation lives. The Run page now also tracks which user created a run.

Note: Triggered automation runs will be displayed as if the owner created them.

Administration Center

The Automations view in Administration Center now includes the Space field and filter.

The Runs view in Administration Center now includes the Executed by and Space at runtime fields and filters.

Activity Center

The Automations view in Automations Activity Center now includes Space field and filter.

Note: Users can configure which columns are displayed here.

The Runs view in the Automations Activity Center now includes the Space at runtime, Executed by, and Owner fields and filters.

In this view, you can see all runs from automations you own as well as runs executed by other users. You can also see runs of other users's automations where you are the executor.

Run history details

To see the full details of an automation run, go to Run History through the automation's context menu. This is also accessible to non-owners with sufficient permissions in the space.

The run history view will show the automation's runs across users, and the user who created the run is indicated by the Executed by field.

Metrics

The metrics tab in the automations activity center has been deprecated in favor of the automations usage app which gives a more detailed view of automation consumption.

Question

When using Heruko PostgreSQL as a source integration, how to enter the Client Key which is required for the Mutual TLS (mTLS) authentication? Since the database requires mTLS to connect, is there any settings available for it in Stitch?

This feature is not supported right now and therefore there are no settings for it in Qlik Stitch. It is considered a New Feature Request.

Please find it here:

IdeaID:#492366_Stitch mTLS and Heroku integration

On the right side, click the thumbs up button icon under “Request Actions” to ensure that you let our product folks know you are interested in seeing this feature placed on the product roadmap for consideration. 

Environment

• Talend Cloud 
• #Qlik Stitch