On April 16th,2024,Qlik is launching a highly anticipated capability: custom security roles.
What do custom security roles do?
Custom security roles introduce fine control of data exportand access permissions within Qlik apps. This allows you to tailor permissions to your specific needs, enhancing data securityand compliance.
The first delivery on April 16th includes the capability to control who can export content. Additional capabilities will be added soon after, such as who can create data connections, reports, and similar.
What does this mean for me?
As part of this update, the existing "has restricted view" space role will gain the ability to export data to Excel. This adjustment is in line with Qlik's capacity-based pricing model, ensuring basic users have essential tools.
If you do not wish for users with the "has restricted view" space role to be able to export data, you will need to edit the User Default roleto deny download for all users, and thencreate a custom rolethat allows if for specific users and groups.
Stay tuned for more information and resources leading up to the April 16th launch. We are excited about these enhancements and the value they will bring to your data management and security efforts within Qlik.
Thank you for choosing Qlik,Qlik Support
...View More
Qlik Cloud Reporting packaging changes are here!
We’ll be replacing the multiple tiers with simple ‘Small and Large Add-On Packs’, alongside standardized limits for easier management.
Our new Standard, Premium and Enterprise customers using our Capacity Model, will have reporting entitlements included in their package. Customers on our User Based Model will have 1000 reports included and available to them.
All customers can purchase our add-on packages when needed.
See structure below:
Key: QSE = Qlik Sense Enterprise / QCA = Qlik Cloud Analytics
Items to Note:
Depending on your product package, you will be automatically placed in the standardized limits above. Those who already have paid tiers will continue-on their current tier until their contract ends.
If you’re expecting to exceed your standard limit, be sure to contact sales to purchase our add-on packages to prevent future overages.
Additional Resources:
Product Descriptions for Qlik Cloud Subscriptions| Qlik ResourcesReporting Services| Product Innovation BlogReporting from Qlik Cloud Analytics | Qlik Help Page Tabular Reporting Corporate Blog
...View More
Hello Qlik Users,
Beginning onApril 22nd 2024, Qlik Cloud will change how the font sizes fortitles,subtitles, andfootnotesare displayed. The change will carry over to Qlik Sense Enterprise on Windows with its May 2024 release.
What is being changed?
Font sizes for titles, subtitles, and footnotes are controlled by either:
the theme, in which a customer can define a set pixel size (such as 16px),
or in the property-styling panel, where the same option is available.
The conversion factor Qlik uses at present is incorrect, caused by a defect introduced by a previous change in a base font type.
What does this mean?
Currently, we convert using 13 as a base when we should be using 14. This results in the font size being slightly larger than the one set by the user.
The current scaling ratio is 1/13 * 14 =~ 1.077.
As an example:
The default themeHorizon, currently set to a 16-pixel default size, is in reality using 17.23 pixels.
Why are font sizes being changed?
Since we use other technologies to embed charts, we don’t want to replicate this error across all interfaces just to get matching title sizes. This means that we’ll now fix this defect, and start using the correct font size.
When will font sizes be changed?
The fix is planned for Qlik Cloud on April 22nd 2024.
Qlik Sense Enterprise on Windows will receive the fix in its May 2024 release.
How exactly will this affect me?
After the fix is deployed,the text in titles, subtitles and footnotes will appear smaller (about 93% of the current size), reverting to the intended size set by the user or the theme developer.
Since this will free up a small amount of space inside each object area,charts and graphics will become slightly bigger.
In rare scenarios, the resulting expansion might result in a different look for charts, where certain features (like labels or legends) appear, move or disappear due to the reaching of specific visual breakpoints.
What do I need to do to benefit from this change?
No action is required for Qlik Cloud users. This change will automatically be applied to all the dashboards at the time of deployment. Qlik Sense Enterprise on Windows users will need to see their platform being upgraded to May 2024.
Can I preview the changes?
A preview is not possible before the deployment on April 22nd.
We're available for questions if needed! As always, thank you for choosing Qlik,Qlik Support
...View More
To our Talend 8 Customers,
To enhance both your security and Talend experience, Java 17 will be the only supported Java version for future updates to Talend Studio and the following supported applications.
Talend Studio
Talend Administration Center
Talend Data Preparation - (client managed installation)
Talend Data Stewardship - (client managed installation)
Talend SAP RFC Server
Talend Semantic Dictionary
Talend Identity and Access Management
Note: this upgrade does not impact execution of your artifacts that continue to support Java 8 or 11.
Previous versions of Java will no longer be supported by the above application when electing to upgrade to R2024-05. We are giving you this advanced notice to ensure you can plan this upgrade and take time to review your current Java environment. Java 17 support was first introduced with the R2023-10 release.
By giving this advanced notification, we are delighted to be able to reach a point of maturity where we can fully support best practices with dependencies and third-party libraries and be proactive in addressing CVEs to deliver constant improvement to the Talend Studio platform.
Compatibility Documentation:
For Cloud
For On Premises
Artifact for Cloud and Remote Engines
For further questions please contact Qlik Talend Support and subscribe to the Support Blog for future updates.
Thank you for choosing Qlik,
Qlik Talend Customer Success
...View More
Update 21st of March 16:00 CET: published CVE numberUpdate 27th of March 10:45 CET: added FAQ
Hello Qlik Users,
A security issue in QlikView has been identified and patches have been made available. Details can be found in the Security Bulletin High Severity Security fix for QlikView (CVE-2024-29863).
Today, 20th of March 2024, we have released two service releases across the latest versions of QlikView to patch the reported issue. All versions of QlikView prior to and including the releases below are impacted:
QlikView May 2023 SR1 (12.80.20100)
QlikView May 2022 SR2 (12.70.20200)
Call to Action
As no workarounds can be provided, Customers should upgrade QlikView to one of the following versions that contain the fix:
QlikView May 2023 SR2 (12.80.20200)
QlikView May 2022 SR3 (12.70.20300)
This issue only impacts QlikView. Other Qlik data analytics products including Qlik Cloud and Qlik Sense Enterprise on Windows are not impacted.
Additional Details
All Qlik software can be downloaded from our official Qlik Download page (customer login required). Follow best practices when upgrading QlikView.
Qlik provides patches for major releases until the next Initial or Service Release is generally available. See Release Management Policy for Qlik Software.
Notwithstanding, additional patches for earlier releases may be made available at Qlik’s discretion.
The information in this post and Security BulletinHigh Severity Security fix for QlikView (CVE-2024-29863) is disclosed in accordance with our published Security and Vulnerability Policy.
The Security Notice label is used to notify customers about security patches and upgrades that require a customer’s action. Please subscribe to the ‘Security Notice’ label to be notified of future updates.
Frequently Asked Questions
Q: Is the vulnerability present in the QlikView Plugin or other QlikView products?A: The vulnerability is related to the MSI files on disk.
Q: Will deleting the MSI files mitigate the issue?A: Qlik does not consider removing the MSI files a complete workaround. A server user can restore them.
...View More
Beginning with the May 2024 release, Qlik Sense Enterprise Client-Managed will release two major releases a year (May and November).
This adjustment aligns our release cycle with the preferred cadence of our customers, enhancing communication around our major releases. Qlik continues to add new functionality to Qlik Sense Client-Managed versions following their initial release to the cloud. As always, we will continue to deliver patches as needed under our Release Management Policy.
We look forward to helping you optimize your release experience. Be sure to follow the release notes area in Qlik Community and review our updated policy.
...View More
Don't miss our previous Q&A with Qlik!Hear from our panel of experts to help you get the most out of your Qlik experience.
SEE THE RECORDING HERE!
Our experts held a Qlik Replicate Best Practices live webinar, answering all your questions about tips and recommendations for running Qlik Replicate implementations.
...View More
Hello everyone,
Google finally set Q3 2024 as the date for 100% blockingall content relying on third-party cookies rendered on web pages in Chrome.At Qlik, the date is not a surprise to us, and to all our customers who embed Qlik Sense, we appreciate your collaboration and patience.
What does this mean for my embedded analytics?
Qlik has been working hard for two years to prepare our products to handle this change and the impact it has on your end users. We've documented additional information for you, which we believe will help you understand how to best configure Qlik Cloud and Qlik Sense Enterprise Client-Managed and keep embedded analytics working smoothly with your web applications and mashups.
Read all about it in Need to Know: Embedding Qlik Analytics and the End of Third-Party Cookies.
Thank you for choosing Qlik, Qlik Support
...View More
Edited 29th of January, 15:00 CET, added information on how to migrate to use a JSON key file, as well as updated the release date for on-premise from February to May 2024.Edited 23rd of February, 15:10 CET, updated release date for Qlik Cloud release, which has been confirmed for the 6th of March 2024.
Hello everyone,
An upcoming update of the Qlik Sense Google BigQuery Connector will no longer support the use of a p12 file as the Key File. This is currently supported while Service Authentication is used as the OAuth mechanism. If you are using a p12 key file in the definition with this connection scenario, you will have to migrate to a JSON key file instead.
Why is this change being made?
The latest version of OpenSSL, 3.0, has deprecated p12 as a legacy function. Therefore, while the new connector version will have a new driver supporting OpenSSL 3.0, it cannot support p12 key files anymore.
How do I migrate to use a JSON key file?
The easiest way to migrate is to create a new JSON key file in the Google Console. Then, the new key file can be used in the connection definition replacing a currently used p12 file. See Google Cloud documentation for more details on how to create and delete service account keys.
When will this change take effect?
The updated Connector will be rolled out in Qlik Sense Cloudon the 6th of March, and in the May 2024 release of Qlik Sense Enterprise on Windows.
Thank you for choosing Qlik,Qlik Support
...View More
