<addressname> =
 (DESCRIPTION =
   (ENABLE=BROKEN) 
   (ADDRESS_LIST =
     (ADDRESS = (PROTOCOL = TCP)(Host = <hostname>)(Port = <port>))
   )
 (CONNECT_DATA =
   (SERVICE_NAME = <service_name>)
 )
)

(DESCRIPTION=(ENABLE=BROKEN)(ADDRESS=(PROTOCOL=TCP)(HOST=<hostname>)(PORT=<port>))(CONNECT_DATA=(SERVICE_NAME=<service_name>)))

The text in a KPI object is not always at the same size. It changes according to the lenght of the text and to the size of the KPI.

Environment

• Qlik Sense Enterprise on Windows 
• Qlik Cloud 
• Qlik Sense Business 

Font size in KPIs is set to change automatically according to the space available in the object. If the text is too long, the font size is reduced. If it is short, it becomes larger in order to use all the space.

KPI object's font size can be adjusted to Small, Medium and  Large but like all other visualizations it will be responsive and automatically resize content when chart is resized.

When the chart is resized, the font size is automatically adjusted to fit the chart. It is not possible to set an absolute value for the KPI font as of February 2019 release. A feature request has been registered in order to allow the font size in KPI objects to be set to absolute.

See Presentation section under KPI Properties

Font size: Set the relative font size of the measure value. When the chart is resized, the font size is adjusted to fit the chart.

How to enable "Integrated Windows Authentication" (IWA authentication) in Qlik Sense and QlikView. Windows Integrated Authentication allows a user’s Active Directory credentials to pass through their browser to a web server.

If you would like to do the reverse and always prompt for username and password, then the opposite settings will need to be taken. 

Environment:

QlikView 
Qlik Sense Enterprise on Windows 
Qlik NPrinting 

Internet Explorer:

Step 1, enable IWA: 

1. Go to the Windows Control Panel and select Network and Internet
2. Open Internet Options
   
   
   
   
3. Select the Network Zone you want to configure (Trusted sites or Local intranet) 
4. Open custom level...
   
   
   
   
5. Scroll to the bottom and click Automatic Logon with current username and password
   
   
   
   

If you are looking to configure your Trusted sites and add your Qlik server:

1. Click Trusted Sites
2. Click Sites
   
   
   
   
3. Add your desired domain name.
   
   

Google Chrome:

Google Chrome in Windows will use Internet Explorer settings

Firefox:

1. Navigate to the URL about:config in Firefox. 
2. Proceed by clicking Accept the Risk and Continue
   
   
   
   
3. In the search bar, search for: network.automatic-ntlm-auth.trusted-uris
   
   Add your domain.
   
   
   
   

The following messages will appear in the engine trace system logs:

QVGeneral: when AAALR(63.312046) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency.
QVGeneral: - aggregating on 'RecruiterStats'(%DepartmentID) with Cardinal(87), for Object:  in Doc: ffe8a825-b52e-4ceb-aea2-30de0f2c3306

There has also been reports of end users seeing the message "Internal Engine error" when opening apps when the error above is present.

Also for QlikView see article SE_LOG: when AAALR(1072.471418) is greater than 1.000000, we suggest using new row applicator to improve time and mem efficiency.

Environment:

• Qlik Sense Enterprise on Windows, all versions

"AAALR" is a very low level concept deep in the engine. Generally speaking it means the average length of aggregation array. The longer this array is, the more memory and CPU power are to be used by the Engine to get aggregation results for every hypercube node.
 
When AAALR is greater than 1.0, normally the customer has a large data set and suffers slow responses and high memory usage in their app. In this case, Qlik Sense has a setting called DisableNewRowApplicator (default value is 1).
 
By setting this parameter to “0”, Qlik Sense will use a new algorithm which is optimized for large data set to do the aggregation, and will use much less memory and CPU power.

Changing this setting when they have AAALR warnings, making this change has resulted in drastic performance increases.

Possible setting values for DisableNewRowApplicator:

Resolution:

• Stop all Qlik Sense services from the windows control panel / services
• Locate the “C:\ProgramData\Qlik\Sense\Engine\Settings.ini”
• Add this portion to the Engine Settings.ini file (press <enter> at the end of DisableNewRowApplicator=0 so the cursor rests on a blank line below it)

[Settings 7]
DisableNewRowApplicator=0
         <---- the cursor should be here when saving the file

• Restart all Qlik Sense services
• (If multinode) Complete the above steps on every node.

Related Content:

• How to start investigating a suspected Qlik Sense Performance issue  

This article provides an overview of how to notify your team on Microsoft Teams using data from multiple apps with Qlik Application Automation.

The template is available via the template picker. You can find it by navigating to Add new -> New automation -> Search templates searching for 'Notify your team on Microsoft Teams with data from multiple apps' in the search bar, and clicking the Use template option.

You will find a version of this automation attached to this article: "Notify-your-team-on-Microsoft-Teams-with-data-from-multiple-apps.json".

Content:

• Full Automation
• Automation structure
• Related Content

Full Automation

Automation structure

The following steps describe how to build the demo automation: 

1. Add two 'Get Measure Value' blocks from the Qlik Cloud Services connector to get a measure value from the first and second apps.
   
   
2. Add the 'Select Field Value' block from the Qlik Cloud Services connector to apply a selection to the third app before getting the measure value.
   
   
3. Now add 'Get Measure Value' block from the Qlik Cloud Services connector to get a measure value from the third app.
   
   
4. Add a 'Send Message' block from the Microsoft Teams connector to send a message to the Teams channel with the information from the above three apps. Specify the Team ID and the Channel ID input parameters. You can use the do-lookup functionality to find value for all these parameters. 

Related Content

• How to get started with Microsoft Teams

Environment

• Qlik Cloud  
• Qlik Application Automation 

This article provides an overview of how to send straight table data to Microsoft Teams as a table using Qlik Application Automation.

The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates, searching for 'Send straight table data to Microsoft Teams as a 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-Microsoft-Teams-as-a-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 the 'Get Straight Table Data' block from the Qlik Cloud Services connector to get data from the straight table for a specific app to send to the Microsoft Teams channel as a table. Specify the app ID, Sheet ID, and Object ID in the 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.
   
   
2. Add a 'Loop' block to loop over the keys from the 'Get Straight Table Data' block response which acts as the table header. Use the '{getkeys: {$.GetStraightTableData}}' formula in the 'Loop' block. Within the 'Loop' block add the following blocks:
   
   
   1. Add an object variable called 'teamsTextBlockObject' to build the header and pass this variable to another list variable called 'cardTableColumn'.
      
      
   2. Add another 'Loop' block to loop over all the values for the current key of the straight table. Within the 'Loop' block add the following blocks:
      
      
      1. Add a 'Condition' block to check whether the column value is empty or not.
         
         
         • If the condition block outcome evaluates to true:
           
           
           • Add the 'teamsTextBlockObject' object variable, set the text value as 'NA' since the column value is null/empty, and pass this variable to the 'cardTableColumn' list variable.
             
             
         • If the condition block outcome evaluates to false:
           
           
           • Add the 'teamsTextBlockObject' object variable, set the text value as the column value of the straight table, and pass this variable to the 'cardTableColumn' list variable.
             
             
   3. Add another object variable called 'columnObject' and pass this variable to the 'columns' list variable. These variables are used to build the straight table data into a specific format which is required to build the structure of the team's message as a card attachment.
      
      
3. Add a string variable called 'title' which is used to provide the title to the message.
   
   
4. Add the 'Create Attachment Adaptive Card' block from the Microsoft Teams connector to build the structure for card attachment. Make sure to transform the 'columns' list to JSON text using the JSON formula.
   
   
   
   
5. Add 'Send Message' block from the Microsoft Teams connector to send straight table data as a table to the Teams channel with the card attachment which was created in the previous block.
   Specify the Team ID and the Channel ID in the input parameters. You can use the do-lookup functionality to find the value of all these parameters. 
   
   
   

An example output of the table sent to the Teams channel:

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.

Related Content

• How to get started with Microsoft Teams
• Send straight table data to Microsoft Teams as a message 
• Send straight table data to email as HTML table

Environment

• Qlik Cloud  
• Qlik Application Automation 

This article provides an overview of how to send straight table data as a message to Microsoft Teams using Qlik Application Automation.

The template is available on the template picker. You can find it by navigating to Add new -> New automation -> Search templates, searching for 'Send straight table data to Microsoft Teams as a message' 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-Microsoft-Teams-as-a-message.json".

Content:

• Full Automation
• Automation structure
• Related Content

Full Automation

Automation structure

The following steps describe how to build the demo automation: 

1. Add the 'Select Field Value' block from the Qlik Cloud Services connector to apply a selection to the straight table.
   
   
2. Add the 'Get Straight Table Data' block from the Qlik Cloud Services connector to get data from the straight table for a specific app to send to the Microsoft Teams channel as a table. Specify app ID, Sheet ID, and Object ID input parameters. You can use the do-lookup functionality to find value for all these parameters. The 'Get Straight Table Data' block is limited to retrieving  100,000 records. This block will not work with other table types.
   
   
3. Add a string variable called 'message' within 'Get Straight Table Data' block to append a list item element (<li>) to the message variable. Specify key-value pairs for the dimensions from your straight table to be included in the message.
   
   
4. Add a 'Send Message' block from the Microsoft Teams connector to send straight table data as a message to the Teams channel. Map the 'message' variable to the Content input parameter and enclose it in an unordered list element <ul>. Ensure you don't send too many records; Microsoft Teams has a limit of 28 KB per message. Specify the Team ID and the Channel ID input parameters. You can use the do-lookup functionality to find value for all these parameters. 
   
   

An example output of the message sent to the Teams channel:

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.

Related Content

• Video - Send straight table data to a Microsoft Teams channel as a message 
• How to get started with Microsoft Teams
• Send straight table data to Microsoft Teams as a table 

Environment

• Qlik Cloud  
• Qlik Application Automation 

Content:

• Step-by-Step:
• Limitations
• Related Content

Step-by-Step:

To create a Mail connection in Application Automation, do the following:

1. In Qlik Sense SaaS Hub select Add New > New automation
2. On the create dialog, select Connections in the menu
   
   
   
   
3. In Explore, search for Mail and select the Mail connector. Press Add
4. Fill out the details for your SMTP server. Press Save and Ok

The Mail connection will now be listed in My connections.

Verify the Mail connection by creating a simple automation.

1. In Qlik Sense SaaS Hub, select Add New > New automation
2. Give the automation a name and press Save
3. In the automation editor, click on the Mail connection in the left pane
   
   
   
   
4. Drag the Send Mail block on to the canvas, connecting it to the Start block
   
5. In the right pane, fill out the required fields to send a test email
   
   
   
   
6. Press Save and Run to execute the automation
7. Verify the test email being sent successfully and received in the mailbox
   
   If you receive any error when running the test automation, verify the details of your SMTP server being correct (Host, Password still accurate, Port etc):
   
   
   
   
8.  In the menu select Connections to go back to the connections page
9. In My connections, select the Mail connection and press Edit connection
10. Confirm all settings being correct and press Save
11. Run the test automation again to confirm the email being sent

Limitations

• The Mail Connector does not at present support SSO. See Qlik Application Automation: "Send Mail" block doesn't work with Gmail's with Okta integration
  
  
• The configuration for an Email server that already exists on a tenant cannot be used within an automation. A new connection must be created in Qlik Application Automation.
  
  
  
  
• The connection will not be verified during creation. As a best practice it is always recommended to verify the Mail connection with a simple automation, before using the Send Mail block in more advanced automations.

Related Content 

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.

With the new inclusion of the Get Chart Image block in the Qlik Reporting connector in Qlik Application Automation, you now have more options to notify a group of users with more in-depth data and charts using Slack, Microsoft Teams, and email.

This article will guide you in sending your first chart image to Slack with Qlik Application Automation.

It explains a basic example of a template configured in Qlik Application Automation for this scenario.

You can make use of the template which is available in the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send a Chart Image to Slack' or 'Embed a chart image in an email' in the search bar, and clicking the Use template option.

For guidance on sending charts via Microsoft Teams and mail, go to the "Next Steps" section at the end of this article.

You can download examples of the automations from this article: Send-chart-image-to-slack.json, Send-chart-image-to-outlook.json, Send-chart-image-to-mail.json, Send-chart-image-to-microsoft-teams.json

Full Automation

Configure the Automation

1. Open the automation editor and search for the Qlik Cloud Services connector on the left-hand menu.
   
   
2. Drag the blocks “Select Field Value” and “Create Bookmark” to the canvas and fill in the required inputs. You can add multiple Select Field Value blocks to apply selections to various fields. The Create Bookmark block is then used to create a temporary bookmark that can pass the selections to the Get Chart Image block.
   
   
   
   
   
   
   

   Warning: Whenever the “Get Chart Image” block is to be used, we advise you to only use it with temporary bookmarks or pre-existing persistent bookmarks.

2. Search for the Qlik Reporting connector on the left-side menu, then drag the "Get Chart Image" block to the editor and attach it below the previous block.
   
   Choose the same app you chose when creating the temporary bookmark and use the ID value received from the “Create Bookmark” block. 
   
   
   
   The height and width inputs are not required and default to 1000 if the fields are empty.
   
   Manually insert the Object ID input; it can not yet be retrieved through an API call.
   
   To find the chart ID from the app, open the app, then click Edit Sheet, right-click the chart, and open the Share/Embed menu from the menu dropdown that appears. You will see the object ID of the chart under the chart preview section as shown below:
   
   
   

    

3. Add the 'Condition' block to check whether the "Get Chart Image" block has returned a successful response.
   
   
   
   
   1. If the condition block outcome evaluates to true:
      
      
      • Search for Slack connector from the left-side menu, add the "Upload File To Channel" block, and fill in all the required inputs.
        
        
        
        
      • The chart image gets posted on the Slack channel as shown below:
        
        
         

   2.  If the condition block outcome evaluates to false:

      • Add the "Update Run Title" block to specify that the "Get Chart Image" block failed due to an error.
        
        
        
        
      • Add an "Error" block to throw an error message from the "Get Chart Image" block and set the current automation run to be in a failed state.
        
        
        

Configure and send the Output

Embed the chart in the email

Gmail does not support embedding base64 encoded images due to security constraints. To work around this, we advise sending the chart image as an attachment through the Send Mail block in the Mail connector if you use a Gmail account.

See Gmail blocking small embedded inline images in email template for details on the restriction. 

1. To embed the image in an email, you'll need to replace the Slack block with Send Mail block from the Microsoft Outlook 365 connector or the Send Mail block from the Mail connector and configure the block's Type parameter to HTML.
2. In the body of the HTML, start adding a <img> tag and set the src parameter of the img tag to "data&colon;image/png;base64,".
   

   
   

3. Add the Get Chart Image block output at the end of the src parameter.
   

   
   

4. Click the Get Chart Image label in the input parameter, and pick the Add formula option; then search for the "base64 encode" formula to apply it to the output from the Get Chart Image block.
   
   
   
   
   

   
   

5. Finalize the img tag with an optional width and height to style the image.
   
   

Send the chart to a channel in Microsoft Teams

1. To send the image to Microsoft Teams, replace the Slack block with the Send Html Message With Base 64 Image block from the Microsoft Teams connector.
2. Configure the "Base 64" parameter of the block by mapping it to the output of the Get Chart Image block.
   

   
   

3. Click the field mapping for the Get Chart Image again and open the formula picker. Search for the base64 encode formula and apply it.
   
   
   
   
    
4. Set the Image Content Type parameter to image/png and (optionally) provide additional HTML content that will be inserted before or after the image.
   

   
   

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.

Environment

• Qlik Cloud 
• Qlik Application Automation 

Related Content

• Distributing Chart Images through Automation

When attempting to log in to Qlik Sense Desktop, after authentication, the following warning may be displayed on the Qlik Sense Desktop screen:

Your Version of Qlik Sense Desktop has expired.
Please Visit qlik.com/QlikSenseDesktopUpgrade to download a newer version.

Visiting the page mentioned in the error will result in downloading the same version that you are currently using.

Resolution

Manually visit the Qlik Product Downloads page to upgrade or install the supported or latest version of Qlik Sense Desktop. No further configuration is necessary.

To review the product lifecycle, please refer to the Qlik Sense Product Life Cycle page.

Additionally, you can find information about the end of support for Qlik products on the Qlik Product Downloads page.

The caution sign (⚠️) marks releases that reach end-of-support within 90 days or less. The end of Support date is highlighted in orange when less than 90 days are left or red when support has expired.

For example, as of today (February 2024), the Qlik Sense Desktop version May 2022 will expire within 90 days, and the version February 2022 has already expired.

Environment

Qlik Sense Desktop 

Question

What is the difference between Qlik SSO login page and Qlik Talend SSO login page?

Qlik SSO login page is the login page to access your Qlik Cloud Tenant.
Qlik Talend SSO login page is the login page to access your TMC (Talend Management Console).

Related Content

For further information on how to login to Qlik Talend Management Console using Talend SSO, check Logging in to Talend Management Console with SSO.

Environment

Talend Cloud 

Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch. 

All Qlik Replicate versions older than the 2024.5 SP03 release are affected.

Environment

• Qlik Replicate 2024.5 SP02 and below
• Oracle Source Endpoint with Oracle 2024 July patch (version 19.24)

Resolution

Upgrade to Qlik Replicate 2024.5 SP03 or later once available. 

Download the early builds for 2023.11 and 2024.5 here:

Link: https://files.qlik.com/url/ptbgkdzrixz2arpr
Password: ey9wfcf8

If you have Qlik Enterprise Manager deployed, upgrade this as well. See Qlik Enterprise Manager fails adding a table to a task with SYS-E-HTTPFAIL, no rest handler for url for download links.

Cause

The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly. 

Internal Investigation ID(s)

RECOB-8698

Reference:

Oracle Database 19c Release Update July 2024 Known Issues

As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.

Question I

How long does it take for Talend Management Console Logs to clear?

It takes 31 days. Any data older than 31 days will be cleared automatically as per our log retention policy. 

Question II

Can you manually change the time it takes for Talend Management Console Logs to be cleared?

The taken time for clearing TMC logs can not be manually changed. As mentioned in the answer for Question I, the 31 days is based on Talend log retention policy and cannot be manually changed.

Related Content

Talend-Cloud-Management-Console-Log-rotention-policy

Environment

Talend Cloud 

You can select a sheet to the landing page of the app by setting a default bookmark.

When you open the app, the expected landing page may not be displayed.

As well, when you open a sheet with a sheet action, the action might not get triggered.

Environment

• Qlik Sense Enterprise SaaS
• Qlik Sense Business

Resolution

The session needs to be terminated.

1. Close the browser or all opened tabs.
2. Wait for 30 minutes.
3. Log in to the tenant and open the app.

Cause 

The default bookmark with selection and landing sheet as well as sheet actions are applied once per session.

Qlik Sense SaaS keeps the session up to 30 minutes after closing the tab or tabs.

Related Content 

Setting a default bookmark to create an app landing page

The hybrid local deployment of Talend Data Stewardship (TDS) R2023-03 shows the newly created/updated Semantic Type (Regex pattern) for customized TIN_RULE as below, which is not functioning per Campaign task data filtering

^(\b\d{7}\b|\b\d{9}\b|\b\d{12}\b)$
^(\d{7}|\d{9}|\d{12})$

Resolution

Update private key and certificates from both Talend Dictionary Service Server and Talend Data Stewardship
 

Cause

After tried to update the Semantic Type by changing the Regex pattern and Naming/Label, and even creating a Semantic Type to publish, the newly created/updated Semantic Type is still not list from the Talend Data Stewardship Data Models side and it is not propagated to Model/Campaigns/Tasks for re-usage. Talend Data Stewardship could not fetch the Semantic Type successfully.

In Talend Data Stewardship catalina.out log, there are lots of network SSL disconnection error messages sent to dictionary service, and it could be the root cause.

Log Analysis 

Searched "UPDATE_CATEGORY" or "TsdEventListener" as a keyword in catalina.out log, you can find that:

The last time of dictionary service received dictionary service API feedback is at 2024-09-16 23:32:49,902. After that, TsdEventListener does not show the rules is propagated and updated successfully until you fix certificate_unknown issue at 2024-10-28 09:38:15,807

SCHM 2024-09-16 23:32:49,902 INFO [container-0-C-1] o.t.schema.datatypes.TsdEventListener : UPDATE_CATEGORY on [TIN_rule,

Till the certificate is fixed,  TIN_RULE shows ST updated

SCHM 2024-10-28 09:38:15,807 INFO [container-0-C-1] o.t.schema.datatypes.TsdEventListener : UPDATE_CATEGORY on [FirstName_Regex, tin_rule_v3,....

It indicates between 2024-10-01 and 2024-10-28 09:38 , the dictionary service could not be accessible due to certificate_unknown issue

starting date of Received fatal alert: certificate_unknown2024-10-01 06:05:32.743 UTC|TransportContext.java:361|Fatal (CERTIFICATE_UNKNOWN): Received fatal alert: certificate_unknown (
"throwable" : {
javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown

Environment

Talend Data Stewardship

Talend Cloud 

Accessing the QlikView Server in the Management Console, or making changes in its settings, throws a "Failed to load because item with ID does not exist. Make sure that the QVS is available with the correct credentials." error.

Environment:

• QlikView 

QVPR is corrupted or includes a faulty Distribution Service / Reload Engine references.

Resolution:

This error message indicates that QlikView QVPR is corrupted.

I. If you have only started experiencing this recently, reverting to a backup of a previous QVPR version is advisable. 

Follow those steps to fix the issue, or see How To: Restore QVPR From Backup for details. 

1. Stop all the services
2. Open folder C:\ProgramData\QlikTech\ManagementService\QVPR\
3. Make a manual backup of all XML files, then delete them
4. Open sub-folder Backups
5. Select the zip file from the day before you faced the issue and unzip it in the QVPR folder.
6. Restart the services.

II. If this issue has been existent for a long while, it may be necessary to look into removing faulty Distribution Service / ReloadEngine references.

For QlikView 11.20 SR15 and up, as well as QlikView 12.x see ReloadEngine@SERVERNAME is down displayed in the QlikView Management Console after an upgrade

III. If the issue presents itself during a new installation, the best approach may be to rename the ProgramData\QlikTech\ManagementService folder, restart the Qlik Management Service which should recreate the directory and all the default settings and QVPR data. Note: all the save settings are restored to default and tasks are flushed)
 

This article gives an overview of the available blocks in the Github connector in Qlik Application Automation. It will also go over some basic examples of retrieving file/blob contents from your repos as well as other functionalities within a GitHub account.

As with most connectors provided for automations the authentication for this connector is based on the oAuth2 Protocol, so when connecting to it you provide the user name and password of the account directly to the Github platform to request access so it is done in the most secure manner there is.

Let's now go over a few basic examples of how to use the Github connector:

How to list owned repositories and check their contents from your Github account:

1. Create an automation;
2. From the left menu, select the Github connector;
3. drag and drop the "List my repositories" block
4. drag and drop the "List repositories contents" block inside the loop created by the first block:

Now the "list my repositories" block offers a couple of filtering options depending what result you want (all repos or just the private or public ones and if you want the result to come in sorted by some rule) but they are mostly optional. Not filling them in will return by default all repositories.

As for the "List repository contents" block you will need to fill in the username you use for your github account as well as the repository name which can be filled in with the results gotten from the first block. You can leave the path parameter empty to get the contents from the root folder or you can specify a path and the contents of that path will be returned.

As stated, if you expect to retrieve only one record, the use of "get repository content" block is more better suited. Also, you might want to switch this "List repository contents" block On Error status to either warning or ignore since Github API platform returns a 404 error if one of the queried repositories is empty.

Now if you are planning to use the "Get repository content" block another warning should be mentioned and that this block only works for files or blobs up to a maximum of 1 MB in size, as per Githubs platform limitations. The response of this block should look like:

As you can see we have a couple of information stubs of that file, but most importantly from here is the SHA property, which is needed if you are planning to later on use the "Create or update file contents" block, required input parameter for the update of a file/blob.

Now if you're planning on updating files that are bigger than 1MB and you require the SHA of that file, we suggest using the list repository contents block and search for the required file and SHA in that result.

As for other functionalities of the Github connector we support also getting and listing commits or issues present in a repository, listing of users and many other requests but, if you are in need of a request that isn't present, we also offer the functionality to create your own requests to the Github API by making use of the RAW API blocks. These API blocks and their uses are explained in a separate article.

You can find attached to this article a simple JSON example which you can upload to your workspace, if you want to see a quick example of how to use version control to back up your QCS apps I suggest visiting the related article.

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: Qlik Application Automation for backing up and versioning Qlik Cloud apps on Github

QlikView and Qlik Sense files are like ZIP file, as in they are highly compressed. So obtaining an estimate of how much RAM is needed for loading Apps into memory (footprint) is difficult to provide across the board. The expected memory usage associated with the app can also depend on how many users access the app and how much they are used.

Environment: 

• QlikView, all versions
• Qlik Sense Enterprise on Windows,  all versions
• Qlik Cloud

An estimate of the RAM needed per app can be built on the below, but for accuracy always test by loading the app into memory and using the Qlik Scalability Tools to obtain a baseline of memory usage for each app as it is accessed by the foreseeable number of users. 

Telemetry logging which allows for using the Telemetry Dashboard, is also an available suitable tool.

Since the release of the February 2019 version, Sense System Performance Analyzer monitoring App can be used to determine app footprint as well. Since the release of the June 2018 version, App Metadata Analyzer monitoring App can also be used. However, these last three may not provide the same data as the Scalability Tools.

An alternative is to use a test environment and simply observe RAM usage increases as apps are first opened (footprint), and as number of users accessing the app increase, then as number of operations are performed within the app. The test environment results for observed memory and CPU usage can be recorded as a baseline for the particular app in production, which assists in determining future sizing/scaling needs.

Need direct assistance in evaluating your Qlik Sense and QlikView apps? Qlik's Professional Services are available to assist you.

RAMInitial = SizeOnDisk × FileSizeMultiplier ; this is the initial RAM footprint for any application 

FileSizeMultiplier: range between 2-10 (this is a compression* ratio depending on the data contained in the app) 

*Compression is based upon the data, and how much we can compress depends upon the homogeneity of the data. The more homogeneous, the more compression Qlik can achieve. 
More information on one way of optimizing a document can be found on the Qlik Design Blog: Symbol Tables and Bit-Stuffed Pointers

RAMperUser = RAMinitial ×  userRAMratio ; this is the RAM per each incremental user 

userRAMratio: range between 1% -10%
 

Total RAM used per app :

TotalRAM = (RAMperUser × Number of users) + RAMinitial 

Example:

SizeOnDisk = 1 GB

File Size Multiplier 6 (range is from 2 to 10) This is an example value. A value can be obtained by reviewing telemetry (how far does the app expand?) or opening the app in a QlikView or Qlik Sense desktop and measuring the expansion based on how large it grows in memory.

RAMinitial = 1 * 6 = 6 GB

If we take a RAM Ratio per User of 6% then it is 0.06 (range is from 1 to 10)

RAMperUser = 6 x 0.06 = 0.36GB

Then RAM Required for 30 Users

TotalRAM = (RAMperUser × No. users) + RAMinitial 
TotalRAM =  (0.36 * 30) + 6
TotalRAM = 16.8 GB

Related Content:

• App Metadata Analyzer
• Sense System Performance Analyzer 
• Qlik Sense Scalability Tools - Community
• How to enable Qlik Sense QIX performance logging and use the Telemetry Dashboard
• Single/Multi-threading in QlikView
• Qlik Sense Performance Benchmark
• Qlik Sense Scalability Tools

After a successful installation of Qlik Alerting following Qlik Alerting installation steps, Installing the Qlik Sense Extension, and then adding the extension object to an Qlik Sense app with the proper Qlik Alerting server information, the extension shows up blank in Internet Explorer (IE) or with the message "Could not retrieve user info. Check your extension settings or contact your administrator" when using Google Chrome:



Chrome will output the following or similar in the Developer tools Console logs: (also under Network tab the extension failure is registered)

POST https://<Qlik Alerting server>:4552/api/users/extension net::ERR_CERT_AUTHORITY_INVALID
error

IE in the other hand will output the following or similar in the Developer tools Console logs and not much under the Network tab (halts after loading the Qlik Alerting js file):

SCRIPT1002: Syntax error
File: qlik-alerting.js, Line:9, Column: 42
SCRIPT5007: Unable to get property '__esModule'of Underfined or null reference

Environment:

• Qlik Alerting 
• Qlik Sense Enterprise on Windows 

In order to use a HTTPS connection with the Qlik Alerting extension a proper certificate needs to be installed on the Qlik Sense clients' computers. Otherwise HTTP needs to be used as indicated in the Workaround(s) section.

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.

Replace the Qlik Alerting self-signed certificate with the certificate issued for the deployment in order to allow HTTPS connections. Otherwise, a certificate error is observed when connecting to the Qlik Alerting web console and API connections from the extension fails as described above. See Workaround section below for an alternative.

There are at least the two methods for resolving the error above:

I. Using the server.pem and server_key.pem files that were originally exported from Qlik Sense:

The easiest way to resolve the error above is to use the server certificate and private key that was originally exported from Qlik Sense.

Note: This may not be suitable for all production environments. It will not allow the extension to function from outside the Qlik Sense / Qlik Alerting local network. E.g: When an external FQDN / Alias / CNAME is used to access the Qlik Sense app that uses the Qlik Alerting extension.

1. Follow the steps documented under Using trusted SSL certificates with Qlik Alerting and replace the mentioned server certificate files (server.pem and server_key.pem) with the server certificates (not the client certs) that were originally exported from Qlik Sense when going through the steps to configure the connection between Qlik Alerting and Qlik Sense.

2. When configuring the extension, make sure to use the machine name that was used when exporting the certificate via the Qlik Management Console (QMC). This will be the "Issued To" field found in the certificates.

3. Make sure the Qlik Sense self-signed root CA certificate (root.pem / root.cer) is installed on client computers (including the Qlik Alerting server) that require access to the web console and use of the Qlik Alerting extension in Qlik Sense apps. The certificate should be installed in the Trusted Root Certification Authorities store.

II. Another method is to replace the Qlik Alerting self-signed certificate with a certificate issued by a private or public CA for the deployment in order to allow HTTPS connections.

Note: The following is an example of issuing an SSL certificate using TinyCert. Please note that certificates issued by TinyCert.org are not considered to be "production ready" and should only be used for evaluation or testing. More information in TinyCert FAQ

1. Sign up for a free TinyCert account.

2. Create a Certificate Authority (CA) certificate. Using the defaults works fine.

3. Create a server certificate. Make sure to include all the host names used when accessing the Qlik Alerting server over https.

For example: The server machine name (hostname) may be sufficient in environments where clients are always on the same local network (LAN). However, an external FQDN (Alias, or CNAME records) for Qlik Alerting may be needed in the certificate's Subject Alternative Names in order to allow the extension to work when Qlik Sense app are accessed from outside the LAN. Keep in mind the client using the Qlik Alerting extension in the Qlik Sense app makes the connection request directly to the Qlik Alerting server.



4. Download the CA Certificate (cacert.pem). This certificate will need to be installed on client computers that use the Qlik Alerting extension as well as accessing the web console (to eliminate the cert error).

5. Download the server Certificate (cert.pem), and the Private key (clear) (key.dec.pem).
Note: Qlik Alerting does not support the option Private key (encrypted) as it does not support passphrases.

6. Move the three files to the Qlik Alerting server and follow the steps documented under Using trusted SSL certificates with Qlik Alerting.
Note:

• The cert.pem file above is the one that gets renamed to server.pem
• The key.dec.pem above is the one that gets renamed to server_key.pem

7. Import the CA Certificate (cacert.pem) on the Qlik Alerting server and on any needed client computer using the Certificates snap-in.

Workaround(s):

In use-cases where encryption of the traffic between the Qlik Sense client and Qlik Alerting is not a priority, communication via plain HTTP (unsecured) can also be used by unchecking the HTTPS option in the Extension configuration:


However, please note that in order for the above workaround to work the Qlik Sense app also needs to be accessed via plain HTTP (unsecured). Otherwise, the error reported above "Could not retrieve user info. Check your extension settings or contact your administrator" will be displayed along with the other errors for the two browsers. In Google Chrome the following will be registered in Developer tools Console logs:

Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint '<URL>'. This request has been blocked; the content must be served over HTTPS.

 

Related Content:

• General: what does the certificate error(red cross) in browser mean and how to fix it