Hey Guys - with all the excitement around our new Qlik Sense Enterprise deployment options:
Qlik Sense Enterprise on Windows
Qlik Sense Enterprise on Kubernetes
Qlik Sense Enterprise on Qlik Cloud Services
...I wanted to share a brief video to show you how easy it is to setup a tenant along with an integrated identity provider (IdP) to provide authentication, using Qlik Sense Enterprise on Qlik Cloud Services. (Please note in this video I use OKTA as my integrated IdP but Auth0 is also supported. This video does not go into setting up the actual IdP subscripition so please have that available prior. ) In order to get access to Qlik Sense Enterprise on Qlik Cloud Services please contact your Qlik representative. If you are want to experience Qlik Sense right away you can always sign up for a 30 Day Trial of Qlik Sense Business. To learn more about Qlik Sense Business check out this blog.
First just to recap – Qlik Sense Enterprise on Qlik Cloud Services is a deployment option on Qlik’s multi-tenanted SaaS-based analytics platform. Offering all the great features of Qlik Sense Enterprise on a secure scalable SaaS environment managed by Qlik.
When setting up your tenant and IdP there are few things you should know.
#1 – Once your information has been entered into the Qlik customer system, you should receive an invitation via email to register your Qlik Sense Enterprise tenant. You will login using the email used when registering for a Qlik Account on our web site. The tenant registration process will guide you to select a region for the tenant to operate in as well as create a tenant name for the URL structure that is to be used to access your Qlik Sense tenant.
#2 – you need to have an identity provider (IDP) setup to provide authentication to your Qlik Sense tenant. This can be done currently using Okta and Auth0. This video will focus on Okta, but the steps outlined will be similar. Setting up an IdP is beyond the scope of this video and it is assumed you have the appropriate access and rights to manage it as we will need some information from the IDP environment to setup the tenant.
3# - you will configure your Qlik Sense Enterprise tenant to use the identity provider and will need your IdP client key, client secret from the IDP system. You will also need the OpenID Connect metadata URI from your Qlik Sense tenant used within your IDP configuration as well as a callback URL to be added to your OKTA configuration.
Let's get started.
Please post your questions here and we will address appropriately.
Regards,
Mike TaralloQlik
...View More
We have created many charts with the Engine API and Picasso.js in the past.
Here is a list of all of them so far
https://qdt-apps.qlik.com/qdt-components/react/#/
What was missing, was the navigation bar with a minimap of the entire chart.
Engine API has a cool method, GetHyperCubeReducedData. This returns a reduced set of points based on the zoom factor. If you pass '-1' in the options, the engine will decide for you the depth of the returned data. So if you have one million points of data, the method will still return to you 10000 cells like the hypercube but this time it will be every 100th element.
const qDataPages = await qObject.getHyperCubeReducedData('/qHyperCubeDef', [{ ...qPage }], -1, 'D1');
Then with these reduced dataset, you can use the same picasso method to render the minimap
picasso({ renderer: { prio: ['canvas'] } }).chart({
element: this.element,
data: [{
type: 'q',
key: 'qHyperCube',
data: data.qHyperCube,
}],
settings: this.settings,
});
Here is the documentationhttps://help.qlik.com/en-US/sense-developer/June2019/APIs/EngineAPI/services-GenericObject-GetHyperCubeReducedData.html
Even though it is work in progress and is missing some functionality like resize and smooth scrolling, here is a live demo
https://qdt-apps.qlik.com/qdt-components/react/#/picasso-vertical-barchart
Happy Coding!!!!
Yianni
...View More
Hi guys -
I'm pleased to present to you a new video series that shows you how Qlik Sense and Salesforce work together.
With so many companies running multiple business systems, Qlik offers an alternative to data consolidation confusion by relating information within Salesforce and other enterprise systems for seamless visual analysis, dashboards and reports. Qlik can easily be accessed within Salesforce as a custom tab or as embedded Qlik graphs, tables, and charts within other Salesforce tabs. Alternatively, Salesforce data can be immediately integrated into a Qlik application via a native data connector to provide an unparalleled view into your business’ entire data.
Please take a few minutes to watch and learn. Enjoy!
Regards,
Mike TaralloQlik
Follow mehttps://twitter.com/mtarallo- for instant Qlik updates and insights!
Part 1: Introduction
Part 2: Embedded Analytics Use Case DemoPart 3: Qlik Sense Client & Other Features
Resources:
Salesforce Connector
Configuring SAML
Embedding Qlik Sense in Web Apps
...View More
The latest Qlik Sense June 19 version ships with a nice new feature that should let anyone to embed or share a chart in style.
How to
It’s simple, find the chart you want to embed and right-click on it, you should access to the context menu where you could for example see the data table for the chart you are looking at. In this case what we want to click on in that menu is the option called “Embed Chart”. Note if your screen mode is set to touch, you will find this option by touching in the vertical ellipsis (aka Kebab Menu) icon.
That will pop a window up with a nice preview of the chart and some options that are very handy.
Setting appearance and interaction
You can customize how you can interact with the embedded object.
Allow interaction
You can select if you want the user to be able to interact with the embedded object.
Enable context menu
You can select if you want the context menu to be available when the embedded object is right-clicked.
Language
You can select which language to use in menus for the embedded object.
Theme
You can select which theme to use for the embedded object.
Selections in the embedded object
You can choose if the user can make selections in the embedded object, and which selection state to show in the embedded object.
Use current selections
You can select to use the current selections in the app.
Show selections bar
You can select to show the selections bar above the sheet.
Allow selections
You can select if you want the user to be able to make selections in the embedded object. You also need to enableAllow interaction.
Clear selections on reload
You can select to clear all selections made in the app when the object is rendered.
Apply bookmark
You can select to apply a bookmark and use the selections defined in the bookmark.Bookmarking selections
When the page containing the embedded object is rendered, the initial selection state is defined by the order of execution and your settings.
Clear selections on reload
Apply bookmark
Use current selections
When you make selections in the embedded object, they will be replicated in the app. If you selectClear selections on reload, for example, and use the embedded object, selections are cleared in the app.
Enjoy it,
Arturo (@arturoqv)
...View More
With Qlik Sense June 2019 comes the addition of a container object to the list of native objects. The new container object allows you to add Qlik Sense visualizations in a limited space by using tabs to switch between the visualizations. Developers can use the Visualization API to create container objects and add visualizations to it on the fly.
You can check out the documentation for the creating a container object with the Visualization API at https://help.qlik.com/en-US/sense-developer/June2019/Subsystems/APIs/Content/Sense_ClientAPIs/CapabilityAPIs/VisualizationAPI/container-properties.htm. Let’s walk through the example of creating a container object and adding some visualizations to it from the docs.
The first step is to create a few visualizations. There's no need to show them yet, but the promises need to be resolved so the visualization objects can be used.
// create some visualizations
var bar = app.visualization.create('barchart', ["Dim1","=num([Expression1])"],{ title:"Great on-the-fly barchart" });
var line = app.visualization.create('linechart', ["Dim1","=Sum([Expression1])"],{ title:"Great on-the-fly linechart" });
var pie = app.visualization.create('piechart', ["Dim2", "=Sum([Expression2])"], { title: "Great on-the-fly piechart" });
// wait for the promises to resolve so the visualization objects can be used
Promise.all([pie, bar, line]).then(function(data) {
// the rest of the code will go here
});
The next step is to create the container. Let's take a look at that.
// create the container object using the Visualization API
app.visualization.create('container', null, {
// only a couple of options are set here, but you can refer to the docs for other available options
title: 'My container',
showTitles: true
}).then(function(container) {
// the rest of the code will go here
});
Now that the container has been created, it's time to add visualizations to it, and then to show the container. That will look like this.
// loop through the visualization objects
for (var i = 0; i < data.length; i++) {
// use the getProperties method on each visualization object model to get its qProp
data[i].model.getProperties().then(function(child) {
// use the createChild method on the container object model to add each child to the container
container.model.createChild(child);
});
}
// show the container on element with id="QV02"
container.show("QV02");
Now the container is created and displayed. There are two methods used above from the Engine API on the model of visualization objects, which are really just generic objects, which you may not be familiar with if you are not familiar with the Engine API. I've linked to those below.
https://help.qlik.com/en-US/sense-developer/June2019/APIs/EngineAPI/services-GenericObject-GetProperties.html
https://help.qlik.com/en-US/sense-developer/June2019/APIs/EngineAPI/services-GenericObject-CreateChild.html
You can also save a reference to the child when using the createChild method, so you can later remove it from the container object if that's something that you anticipate. You would just use the id of the reference to the child in the destroyChild method you can find herehttps://help.qlik.com/en-US/sense-developer/June2019/APIs/EngineAPI/services-GenericObject-DestroyChild.html.
It looks like this when all put together.
var bar = app.visualization.create('barchart', ["Dim1","=num([Expression1])"],{ title:"Great on-the-fly barchart" });
var line = app.visualization.create('linechart', ["Dim1","=Sum([Expression1])"],{ title:"Great on-the-fly linechart" });
var pie = app.visualization.create('piechart', ["Dim2", "=Sum([Expression2])"], { title: "Great on-the-fly piechart" });
Promise.all([pie, bar, line]).then(function(data) {
app.visualization.create('container', null, {
title: 'My container',
showTitles: true
}).then(function(container) {
for (var i = 0; i < data.length; i++) {
data[i].model.getProperties().then(function(child) {
container.model.createChild(child);
});
}
container.show("QV02");
});
});
That's how to create the new container object and add visualizations to it using the Visualization API.
...View More
Today's guest blogger needs no introduction. I am pleased to have Elif Tutuk,Qlik Director of Research, join me on today's edition of the Qlik Design Blog. Today Elif and I have teamed up to bring you an exciting video that highlights the strength and unique capabilities only made possible by the Qlik Associative and Cognitive engines coupled with the power with AI.
In the digital age, business users need analytics tools that surface anomalies, the unexpected connections in the data. Unfortunately, these unexpected connections would not be seen if the analytics tool uses a relational data layer, where the data is connected by a human based on pre-canned business questions.
As the name applies, relational analytics tools work based on the relationships between data tables, which means the users can only “traverse” in the data based on the pre-defined relationships, which would prohibit them from seeing the unexpected connections defined by the data.
On the other hand, with Qlik’s Associative technology, the connections between data points are defined by the natural associations found in the data, not by the data table relationships defined by a human.
This difference becomes even more important as the analytics technologies start to leverage AI. At Qlik, we are building our AI and Natural Language capabilities with the data layer that “livewires” itself. Let me explain you what I mean by “livewire” by using an analogy from human brain.
Read more here:https://blog.qlik.com/livewired-vs.-hardwired-data
...View More
The contents of this document are for informational purposes only and relates to installation and configuration of an initial test environment only. This document is expressly not part of Qlik Documentation, and Qlik makes no warranties or representations, or any obligations to update, with respect to the information contained herein. Partners are solely responsible to determine their own deployment processes with respect to production use of Qlik Sense Enterprise on Kubernetes.
HAVE A QUESTION?Please useSource Linkfor Discussion - to provide your own thoughts, comments and questions soJesús can respond to you directly.
AboutJesús Centeno:
Jesús Centeno is a Global Alliances Manager at Qlik with over 20 years of blended experience in Strategic Alliances, Business Development and Analytics/Data Management implementations. During the last few years at Qlik, Jesús has supported the launch of a new partner program focused towards Managed Services Providers.
His professional background in end-to-end management of strategic partnerships with Tech companies and Global System Integrator partners expands across various industries. Prior to joining Qlik, Jesús worked for international organizations such as MicroStrategy, the International Monetary Fund (IMF) and Freddie Mac.Jesús has a BS degree in Mechanical Engineering from Tec de Monterrey University and an MBA in Finance and Logistics from University of Maryland.
...View More
With the June 2019 release of Qlik Sense, the trellis chart is now a visualization we can add to our apps right out-of-the-box. With this release, the Trellis container extension is part of the Qlik Visualization bundle allowing us to show a master visualization across various dimension values all at once. Here is an example of what a Trellis chart looks like:
In the Trellis chart above, Lost Time Value by Line for each Plant is being displayed. The master visualization is a bar chart with the dimension Line and the measure for Lost Time Value. When I add this master visualization to the Trellis container along with the Plant dimension, I can see the bar chart for all 5 plants. This allow me to compare the time lost value for each plant side by side. The Trellis chart is created by adding the Trellis container from the Qlik Visualization bundle to a sheet and adding a dimension and master visualization. One adjustment I had to make since I was using an expression for my measure was to add a label for the measure in the master visualization. This prevented the whole expression from being displayed as the label.
There are several Trellis options in the properties section that are quite helpful in customizing how you want the Trellis chart to look. In the chart above, I set number of columns property to 5 so that all charts could be displayed side by side. I also set the dimensions titles property to left side only. This shows the dimension label (Line 1, Line 2 and Line 3) on the left most chart only providing more space and removing redundant labels that are not necessary in this layout since the charts are side by side. Other title options included right side only, top only or bottom only. There is also the option to adjust the measure labels by setting the measures titles property but I opted to keep this set to chart default and show the label on each chart.
Here is another example of how the Trellis charts could be displayed:
In this example, I set the number of columns property to 3 and I kept the dimensions titles and measure titles properties set to the default, chart default, so that the x and y axis labels appear on all the charts. With this layout, if I set the dimensions titles to left side only, the top left chart would be the only chart with a dimension label and I did not think it would be clear to the user that it applied to all the charts.
There are many other properties that can be set for the Trellis container such as slide mode. On mobile devices, slide mode is on and shows one Trellis chart at a time. The user can swipe to get to the next chart. Here is what the Trellis container with slide mode on looks like. Notice the arrow on the right that can be used to go to the next chart and the dots at the bottom to show that I am on the first of five charts.
Check out Qlik Help and the Trellis Container video to see all the ways the Trellis container can be customized. To learn more about the other new features in the Qlik Sense June 2019 release, check out the What’s New – Qlik Sense June 2019 app on Qlik’s Demo Site and the What’s Newvideo. These resources also highlight the best practices you should consider when creating master visualizations that will be used in a Trellis container.
Thanks,Jennell
...View More
Hey guys, happy to be back and sharing some awesome tips and tricks with you today! When demonstrating Qlik Sense the other day to some business users, we touched on the topics of Set Analysis, Set Expressions and the use of Bookmarks in Qlik Sense. Thoughdocumented in the Qlik Online help, many methods and approaches to using these powerful capabilities can often be missed. In this video I'll show how you can use the expression editor and a defined Bookmark (from your selection state) as a Set Expression.
Ohh...one thing not covered in the video, that I will mention here is that when you create a Bookmark, if you select the information icon (i) nesx to the Bookmark date on the right in the Bookmark list pop-up, you can preview the Set Expression that is defined from the selection before you insert it with the expression editor.
Bookmarks and Set Expressions
If you have any comments or questions, I'd love to hear from you, so please speak up and don't be shy.
Regards,
Mike TaralloQlik
...View More
Qdt-components is a library that we've build in the Demo Team to help us with our mashups.
We had many requests for custom picasso charts, other than the pre existing ones we already include in the bundle.
So far we have'comboLineBarchart','horizontalBarchart','lineChart','multiLineChart','pie','piechart','scatterplot','verticalBarchart','verticalGroupBarchart','stackedBarchart','verticalGauge','verticalRangeGauge' and'rangeArea'.
Today I have also added a Gantt chart (https://qdt-apps.qlik.com/qdt-components/react/#/picasso-gantt)
So the question is what if I want to create another chart that is not one of the above?
There are two ways of achieving this. Either by getting a preexisting one and adding more components, like a bar chart and add a line to make it a combo or, by including all of the components yourself.
In order to make this possible, wehave exported all of these preexisting charts, as well the individual components like axis, boxes, lines, dots, labels, legend, pie, point, range and tooltip.
Here is an example that describes both ideas.
https://qdt-apps.qlik.com/qdt-components/react/#/picasso-custom-combo-chart
In the first example "custom1", I used an already predefined setting, verticalComboChart and appended 2 lines and 3 points.
In the second example "custom2", I created the entire settings file.
https://github.com/qlik-demo-team/qdt-react-website/blob/master/src/pages/PicassoCustomChart.jsx
https://github.com/qlik-demo-team/qdt-react-website/blob/master/src/components/QdtComponent.jsx
Render in your Template
<QdtComponent type={viz2.type} props={viz2.props} />
Define the props in your code
// In this page:
const viz2 = {
type: 'QdtPicasso',
props: {
type: 'custom1',
cols: [
"Case Owner Group",
"=Num(Avg([Case Duration Time]), '##.0')",
"=Count( {$<Priority={'Low'}, Status -={'Closed'} >} Distinct %CaseId )",
"=Count( {$<Priority={'Medium'}, Status -={'Closed'} >} Distinct %CaseId )",
"=Count( {$<Priority={'High'}, Status -={'Closed'} >} Distinct %CaseId )",
],
outerHeight: 300,
},
};
const viz3 = {
type: 'QdtPicasso',
props: {
type: 'custom2',
cols: [
'Case Owner Group',
"=Num(Avg([Case Duration Time]), '##.0')",
"=Count( {$<Priority={'Low'}, Status -={'Closed'} >} Distinct %CaseId )",
"=Count( {$<Priority={'Medium'}, Status -={'Closed'} >} Distinct %CaseId )",
"=Count( {$<Priority={'High'}, Status -={'Closed'} >} Distinct %CaseId )",
],
outerHeight: 300,
},
};
// in the QdtComponents class:
componentWillMount() {
const { props } = this.props;
const { settings, components, interactions } = QdtComponents.picasso;
if (props.type === 'custom1') {
props.type = null;
props.settings = settings.verticalBarchart;
props.settings.scales.y = { data: { fields: ['qMeasureInfo/0', 'qMeasureInfo/1', 'qMeasureInfo/2'] }, invert: true, expand: 0.04 };
props.settings.components.push(components.line({
displayOrder: 3, y: { field: 'qMeasureInfo/1' }, stroke: '#960000',
}));
props.settings.components.push(components.point({ displayOrder: 4, y: { field: 'qMeasureInfo/1' }, fill: '#960000' }));
props.settings.components.push(components.line({
displayOrder: 5, y: { field: 'qMeasureInfo/2' }, stroke: '#99cc66',
}));
props.settings.components.push(components.point({ displayOrder: 6, y: { field: 'qMeasureInfo/2' }, fill: '#99cc66' }));
props.settings.components.push(components.point({ displayOrder: 7, y: { field: 'qMeasureInfo/3' }, fill: '#275378' }));
} else if (props.type === 'custom2') {
props.type = null;
props.settings = {
scales: {
x: { data: { extract: { field: 'qDimensionInfo/0' } }, padding: 0.3 },
y: { data: { fields: ['qMeasureInfo/0', 'qMeasureInfo/1'] }, invert: true, expand: 0.2 },
c: { data: { field: 'qMeasureInfo/0' }, type: 'color' },
},
components: [
{ type: 'grid-line', y: 'y' },
components.axis(),
components.axis({ scale: 'y' }),
components.tooltip,
components.box({ fill: '#3399CC', stroke: '#275378' }),
components.labels(),
components.line({
key: 'line2', displayOrder: 3, y: { field: 'qMeasureInfo/1' }, stroke: '#CC6666',
}),
components.point({
key: 'point2', displayOrder: 4, y: { field: 'qMeasureInfo/1' }, fill: '#CC6666', stroke: '#B35A01',
}),
components.range(),
],
interactions: [
interactions.itooltip,
interactions.pan(),
],
};
}
}
Yianni
...View More
