Hello and welcome to the October edition of
Techspert Talks. I'm Troy Raney and I'll be your host for today's session. Today is Visualization
Day and we have multiple Qlik experts ready to share with us. Patric why don't we start with you.
Would you tell us a little bit about yourself?
Thank you. It's great to be here again.
So, my name is Patric Nordström. I'm a Product Manager at Qlik. I oversee the
visualizations and the Geo Analytics. So, I also tend to keep track of other things inside
of the client, but mostly the visualizations.
Great. Thanks, and Bruno?
Yeah. Hi Troy. My name is Bruno Calver. I work in the UK pre-sales team. The thing
that I really focus on is where our technology meets the end user. So really, I love turning
what are otherwise boring and mundane data sets into visualizations that tell stories, provide
insights, and Inspire new ways of thinking.
And Patrik, could you tell
us a little about yourself?
Sure. My name is Patrik Lundblad, not
‘the other Patrik.’ I’m a Lead Product Designer here at Qlik. So, I work in R&D with
the dev teams. I work with the Architects, with the ux designers, and other people; mainly
representing the users and talking and showing how you users out there use our product and
how we can make a better experience for you.
Fantastic. Well, today we're going to take a
look at a lot of different things. We're going to start off with the product roadmap; take a look
at features that have been released and what might be coming around the corner. We're going to take
a look at a really cool new feature the Layout Container and see how that works; and we're
going to take a look at some cool things that you can do with bookmarks; some old and some new
and what's possible there. Now Patric Nordström, let's start with you. Could you highlight
for us some of the updates and features that have been released with Qlik Cloud recently?
Sure. All of this is part of a larger undertaking, trying to improve on the look and feel. Currently
working on new improved tables. You might have already seen the new Straight table maybe
the biggest change is the ability to pick and choose without going into edit mode which
dimensions and measures I want to look at. So, it's a bit of a catch wall to serve a variety
of different users. The next major update to the table will be a multi-page PDF export for all
the other charts and the prior tables; we only can export the current view but with the new table we
will be able to create multiple pages of PDFs.
Wow, that's really cool. Would you quickly
highlight some of the other recent improvements?
You might have seen, we added the
settings for the sheet background; settings to make the grid more fine-granular;
so you can move things around more precise. We added images and colors to the chart backgrounds;
we also improved on the access font styling. Lots of people have been asking for the ability to
change the font besides using a custom theme.
So, does that allow you to set a different font
on the access label of a chart versus the title?
Yes. If you go into a chart, on the presentation,
under styling, for each there's a general section that applies to basically all charts; like the
title, subtitle, and footnote. And then you have additional styling specific to that type of
short. So, you will be able to set the axis title, axis label, in this case for the bar chart, value
labels, Legend title, and Legend labels, also to set the color and the size and the font family.
That's really granular, that's great.
This has been possible to do with a custom theme.
We now provide both options. We can now switch off the sheet title and the toolbar. There's this
one called Show Toolbar and the other one is Show Sheet Header; but we will also be able to change
more of the look and feel of this standard top bar; that you can see, it gives you more screen
state to do whatever you want. In this case, I'm having this app that should work in both
Swedish and English. So, in order to change the names of things, I'm using the expression
based labels; but I don't have that type of control over the common selection bar because it's
a mirror of the data model. So, if I now just set it to English, I can control how this selection
bar should work. I've replaced the selection bar with my own. If I make selections here, and
then I have buttons to clear the selection, or go back in the selection. I also have
different buttons to move between the sheets.
That's great.
The filter panes that look pretty much the same for many years, but now we have lots
of more abilities to line them up in a grid mode; we have the histogram mode; we have the compact
View mode; you can turn them into checkboxes or into radio buttons.
Very cool.
You might have noticed the line object that
appeared not long ago. It's a way to style and add dividers and decorations to your dashboard.
That's great.
We added the font styling also to the KPI
object. So, that's also something new.
I love all of that; especially the Filter Pane
and new styling options. Are there any upcoming improvements that you can tell us about?
For all of these visualizations improvements, they end up in the Cloud first. And then we
round up all these changes for the on-premise releases which are 4 times a year. The next one
which I am really eager to push out is the new Text Object. It's a rich text object replacing
the text and image object; and it's more like a rich text object that you can find in Confluence
or Miro; where you can change the font family, size, and weigh,t in color, you can change the
paragraph control, you can also have order, list, and bullet lists that you could create
just for formatting purposes. You can add a table to your chart, and then you can
decide whether how many rows and columns, whether it should have borders. It's not like a
standard Sense table, where you make selections. It's more useful for doing formatting and
perhaps creating this ad-hoc metrics table.
Just sort of spacing things
out into columns and rows?
Yeah. So, the really big thing that will coming
this year which is the Layout Container. The way it works is that you lay out objects; in this case
I have a grid. I can overlay the object so they can be on top of each other; and I can decide
the order; and I can use the new settings for background color; whether I want to have the
same background or a transparent background. When I move things around, I get guidelines, and
you can select multiple things at the same time. So, it's a major big change. And of course,
with great power, comes great responsibility. You have a lot of options, but you also
have possibilities of things going wrong.
Well, that's why it's great that we have Bruno
here today to talk about some best practices for how to use this new Layout Container.
Bruno, what do you have to share with us?
Good stuff. Thank you, Troy. As Patrick mentioned,
with great power comes great responsibility. So, let's have a look into the Layout Container
and how we can really get the best out of this object. So, I've just put together 5 tips to try
and bear in mind. We use grids a lot to create symmetrical layouts, to create consistency in the
user experience and also to ensure that they're visually appealing. For example, BBC website. It's
really important to stick to a consistent approach so that objects are laid out in a beautiful
way that's easy to navigate. The next thing then is the best things are always odd. If you
imagine that being arranged on a plate in a two, it just wouldn't quite look right; and so, we have
to consider that in terms of how we're laying out objects. So, I've just done a simple example here
where I've just put two KPIs over a line chart. That looks okay; but actually 3 just somehow looks
more complete. So, here you can see this is a sales dashboard courtesy of Dennis Jaskowiak. It’s
a good example of both sticking to a grid; as well as doing things in 3s. He's laid this out with 3
kind of specific containers; and then within each of those containers are a variety of objects and
a sidebar as well. So, I know that might look like 4, but actually that's a consistent navigation
object that's been built on the side there. This is just a simple example of how we've stuck to a
grid, and we've used an odd number of containers, and I think this is quite pleasing to the eye.
Is this 1 Layout Container behind that? Or are we looking at 3 Layout Containers
with objects inside them?
Yes. There's 4 Layout Containers there.
We've got a Layout Container here; that then contains a number of different objects.
So, this has got all the the filters and so on; then this is handled as a separate container;
and again you can see the different elements in here. A 3rd and a 4th container; and you can
see within each of these containers; as I said, you've got all the different objects. We've
also here if you've got a line object here, which is creating nice dividing lines as well,
between each of the different elements.
And that fine grid.
Yeah. You can have gridless design within the Layout Container as well.
So, the choice is yours in that regard.
Okay. Well, that was a great design example of
keeping things in odd numbers. What's next?
The next point then was around the use of images.
You can see here we've used a background image. Alberto Vaghi here from the Italian pre-sales
team; it's design credit Alberto. So, the image here has been used to create kind of like a high
contrast theme. Alberto is very clear to point out: when you're using background images like
this; you have to make sure that you're using images that are fairly solid in color. If you've
got lighter objects in the background image, it will interfere with the legibility of the
dashboard. Alberto's uses these line objects to demarcate different sections. He's also
done some fun stuff here. So, you can layer objects on top of each other. Alberto's put
in a View Plants map. You can click on there, and that actually puts an overlay on there. Once
you start building these custom navigations, he greyed out this button, because it's now
just a Close Plants Map; it's light there to highlight that it can be activated; and then
he's always creating a root out. For example, here on this filter pane, if you click on the
filter pane here; you've always got a way to uncheck it. When you're building these custom user
experiences, you need to make sure that you've always got a way back to navigate, and so on.
Is it possible to open up the edit on that and show us how it was configured?
Yeah. Absolutely.
So, yeah, it looks like he's hidden the header.
Yeah. He's hidden the header. You have to be mindful of that, because that will hide this
Advanced Options box which is where you can edit some of this. And here's that button. So,
this is how he set; he's basically set the icon in here. So, if we go into the expression here;
he's used a variable. Yeah. And then according to the variable then; it's either going to
show Menu Icon or the Remove Icon there.
Very cool. That whole layering objects
on top of each other, I love that.
Yeah. Which is what a lot of people used to
do in QlikView. You can just use a container object at the moment, and within the container
you can then have a conditional show and hide; so that a different object will appear. But
that's only on a single object basis. So, you might want to layer more than one object
on top of each other; or as you can see in this example here, you're actually directly overlaying
an object on an already existing object; kind of bringing it to the foreground. So, the Layout
Container really opens up these possibilities.
Okay.
So, it's really important through the use of color; like in this
example where we've got a very dark background, and then just to delineate each of the objects,
we've used slightly lighter shades of black to then demarcate each of the objects onto
the background. So, yeah, think carefully about how you use Line Objects, background
images, and so on; and some of the icons, Etc. And try to use common icons that people can
easily work with; especially when for example, building sidebar navigation, that type of thing.
Sure. You want it to be intuitive for users.
Exactly. Okay, number 4. So, one of my favorite
quotes from Bruce Lee: ”Simplicity is the key to Brilliance.” Now you've got this ability to
overlay objects; there's a real temptation to cram in lots and lots of KPIs and different charts,
and so on. And we need to really be focusing on the key business questions; why are the users
trying to log into that screen? And not trying to do too many things in one place. What we'd
really like to do is: build a very nicely curated space that's been thoughtfully laid out and
designed. And generally I would say that 4 charts on a single screen; maybe 5 (sticking to
our odd number rule), but 4 or 5 charts is about the maximum we want to put on a screen.
Okay, that's a good rule of thumb.
Personal anecdote, but when I moved from working
with QlikView to Qlik Sense, I really loved the fact that I could very quickly just drag and drop
objects onto screen in Qlik Sense. I could just very quickly place objects on a screen; visualize
them and actually get some of the important data Insights very quickly. For a lot of users, where
you're just building dashboards for yourself or a very small audience; I probably wouldn't look to
use this Layout Container, because it's going to take up a lot of time. However, if you're building
a central dashboard; then in that example, then it probably is worth investing the time; using
a Layout Container; coming up with some really kind of high-impact bespoke designs, and so on.
Just because you now have the Layout Container, doesn't mean you should always use it.
Just keeping things simple, and quick, and easy also has its advantages. So, I think it's
really worth highlighting that as a final point.
Great, and tweaking costs time.
Tweaking costs time. Just to summarize those five key tips: firstly, stick to your grid when you're
laying things out; then using odd numbers always presents better. Thirdly, image is everything. So,
really think carefully about your color palette, but also when you're using background images,
make sure that those images aren't interfering with the reading of the dashboard. ”Simplicity is
the key to brilliance” said the great Bruce Lee; and then the final point: now you've got
this Layout Container doesn't mean you have to use it. You know, deploy it in the right
circumstance; it can really kind of wow the users; and that is going to take you a lot of
time. So, invest that time carefully.
Fantastic! Thank you. Okay, Patrick. So, from
something totally new to something that's been around for a long time; one of my favorite
features of Qlik Sense is bookmarks. Can you talk to us about what is possible with bookmarks?
Sure, Troy. I don't know about you, I normally use bookmarks a lot when I'm inside
an app and I maybe want to come back later and show things to other people.
Definitely. So, what are we looking at with this app here?
I have a cars data set. I have some cars from 1978 up to 1982.
Okay. So, it's a small data set. Can you show us how to pre-apply a
selection when users open the app?
Yeah. And I'm gonna go and select 1982. I'm gonna
go into bookmark; let's create a new bookmark; Latest Year, and once it's saved, right-click
here on it, Set as Default Bookmark. That means that whenever another user comes
into the app, once you've published it, the first time they open a session to the app,
that is the bookmark that will be selected.
That's really cool. And that
option, to Set Bookmark as Default; has that been around for a while?
I think it's been around for the latest 6 or 7 years or something like that.
That's amazing. I've never seen it.
Time goes on, there's a new year. Happy
New Year, Troy. There's a new car; maybe there's a Swedish Ikea car or something.
I'm just gonna do an inline load and add one more car. It's more of a prototype, I probably
could call it, because it has really bad stats.
Okay.
And if we clear the selection; sort it from top to bottom; we got this
new car in here. No acceleration, no horsepower. User comes into the app, maybe on the second of
January; Latest Year is selected, and they're wondering: why are we still in the past? Okay.
You can actually click on a bookmark; you have ”i” icon in here; if you expand it, you
can see down here: what is the selection that's being made. It's a selection against 1982,
actually not a selection against Latest Year.
Okay, it shows you exactly
what's being calculated there?
What's being calculated, what's being stored.
Okay, I like that.
In this case, I need to use a Search Expression
to search for what is the latest value within my data set. I have a cheat sheet in the bottom left.
I'm going to say: =Year, because that's the field I want to have; and I want to find what is the
Max Year within here. ”Total” looks through the data that I selected. Many people just click on
1983 and they click Ok. Search Expression needs to be executed by pressing Enter or Return.
I go up here, I'm going to create a bookmark. I'm going to call it Max Year instead. So, now
if I create it, Latest Year has 1982 selected; while Max Year instead has the Search Expression
in here. You can actually copy this if you remove the set expression around it.
Okay. And if you apply the Max Year bookmark now?
Max Year is selected. I mean it is a truly horrible car, let's remove
it. Go back in here at the table; uncomment. So, now no selection applied. And I click
Max Year. And 1982 is selected instead, because that is the max of the data.
That could be quite handy as a default bookmark, to have the Max Year as the default selection.
Now there is some issues with this. Let's say for example, that you as a user are in here;
you're clicking around, you're selecting a couple of years. So, I got 1978, 1979. I see
there's a bookmark here to get the Max Year. 1982 is not selected, because the
Search Expression as it is right now, uses the Total modifier and looked through
everything that was within the selection.
Right.
So, 1978-1979 of course, 1979 is the max one. But maybe you want to have
a bookmark that always selects the Latest Year, no matter what the selection a user has done.
Right. So, how do you do that?
In this case, use the second one down here. I'm
going to use an Only qualifier around it; and [1] in our selections for Year; that's because I just
want to have one year selected; = I'm going to do Max again the [1], I think you can use type ”All”
instead also if you want. So, it's Total Year; press enter. In this case, I'm going to use a
new feature that's available which is Replace Bookmark. I'm going to use the Update.
So, you took the old Max Year bookmark and replaced the Search Expression with
one that'll apply the actual Max Year; irrelevant of current selections?
Yeah. Because you don't want to go in here and create a new bookmark. You want
to use the same bookmark, but with a new expression in here. So, quite handy to tell
you have to be able to Update the bookmark.
That's great. What's the
difference there with those options between the Update and the Edit icon?
So, the Update just updates the selection; while the Edit one is if you for example want to
rename it; if you want to change the description, or if you want to delete it. So, now I have
1978-1979 selected. I go over to the bookmark. 1982 is selected, despite having selections within
the field already for some other values. That's a great way of having that bookmark; making
certain that it is always the Latest Year, not the maximum of what's in there.
That's great. So, that's really demonstrating the difference between
a Static bookmark and a Dynamic one.
Yep. Another thing you can do is to use the Layout
options within the bookmark as app developer. So, Patric talked about this new table down here. I'm
just going to go into edit mode; and show you how it's set up. This is the new Straight table, which
has the columns that are available and visible to the user. It also has some alternative columns.
I can go in here and I can add to this table and create the table that I want. This is called
changing the layout. Whenever I go in here and I create a new bookmark; I have the option here
of saving the layout or for example saving the variables as part of the bookmark. I can come in
here at another time; where I for example, have a different table. And I can click on a bookmark. I
can click my table exploration, and it will by the selections I had; it will also go to the sheet I
was on, and it will make certain that the layout, the dimensions and measures that were within the
chart are also selected for that, so I come back to exactly the same view and not just the
same sheet and same selections. So I can for example use the Button Object here with
two different bookmarks that I created with two different layouts; and I can say
that this is 1 type of standard report; and this could be another type of standard report.
I'm just using the bookmark here to be able to change the layout for the end user. It is the
button object. It is just an Apply a Bookmark; and the user can always go back in to Chart
Exploration, and create their own report.
That's a really cool concept: to provide a couple
of pre-built layout templates for the user, but still allow them to build their own
layout after they've seen some options. How can users share their own bookmarks?
Yep. In this case, I've used a report, and I saved a couple of countries in here, and I
can do my bookmark that I want to share. Save the layout, which means that the link I sent to you is
actually going to be exactly the same. To be able to share a bookmark, I actually have to make it
Public first. You can see that it needs to be made Public, because you need to be able to have access
to the bookmark. So, I can copy this bookmark, and send it to you. So, that's one way; but then
you're going to end up with a Public bookmark. Another way to do is by just right-clicking
the chart, clicking Share, clicking Copy Link; and then you will get the link
to that visualization with the selection states that was at that time.
Okay. So, that's not actually a bookmark, but it's applying the selections that are
current in the app at the time you copied it?
Because bookmark is a resource that
can be either private or public, but this is using another service to
store the ID of the app, ID of the sheet, ID of the association, and what has been done to
the visualization, in this case the selections.
Well, now it's time for Q&A. Please submit your
questions to the Q&A panel on the left-side of your On24 console. All right, first question:
can you help me understand why after applying a bookmark that my selections disappear?
Sure. So, this is something that quite often comes up as a bug to R&D they get assigned to me
and I look through it and I often noticed that for example using the wrong type of Search Expression
okay in this case it might be that I'm using the year as a field the max function because I want
to have the Latest Year but I want to have the latest here among everything So, I use the bracket
one then I do total year this is a possible Search Expression it does evaluate to 1982 by selection
same location and as long as I don't have a value selected this is gonna execute and work fine
but the case can be that for example due to triggers due to other things you might have
another year selected before already and now if you go in here and you apply the my selection
that's when the selection bar disappears because the Search Expression evaluates to an empty State
there is no 1982 available within there and that's why you need to use the only bracket one year
before to say within the year field also make sure that every selection is possible to do
Yeah. I can totally see how that could be frustrated for customers especially
when we say that's working as designed
Yeah. Once I go back in, I click it again.
I get customers complaining that I usually need to click on a button twice to get a
bookmark to apply or selection to apply, and that's because you already have a selection
and we cannot overwrite that selection.
Well, I appreciate you clarifying that
for people. All right. Well, let's move on to the next question: how can we deal with
multi-page straight and pivot table exports?
If you do a data export you will get multiple
pages the Excel file; and if you open up in Excel, it will have multiple pages. Perhaps the user
is referring to the PDF export which today is only printing the current view. One of the
new features of the new straight table that is coming up this Autumn is the ability to print all
pages, up to 50 pages in The PDF export. So, that is something coming in the new Straight table.
Fantastic, that's nice to know, great. Well, next question: is it possible to put containers inside
containers to get a bit of a tabular layout?
So, in most cases you can solve that without
putting the container inside of the container. It's a bit like the movie Inception, after a
while it becomes really strange behavior. So, first versions of the containers will not
allow for putting containers in containers. I would like though to be able to put the
Layout Container inside of Tab Container, but we are rewriting the Tab Container to look
more like the Layout Container. No containers in the containers in the first releases.
Okay, that sounds like a wise thing. It's a pretty big rabbit hole that
could turn into. Great, next question: how can we find out about new features that
are added and how often is Qlik Cloud updated?
Yeah. That's a great question. This is
what we struggle with. We are very quick on delivering new things, but there's also
the other part of telling people about it; and also to get users to use the new features.
We do have the Product Innovation Blog; there are also the What's New reference documentation
on Help.Qlik.com; and we do also have in-app announcements in the Cloud platform. For the
on-premise users, a month ahead of the release, there's a Technical Preview where you can download
documentation; and I also publish an app that you can try out; and you can actually try out the full
installation. If you don't have the strength to do that, you can at least download the PDF.
All right, great. Just move along to the next question: is there a way to easily
change the font in an entire app at once?
Yes. There is you you should set the font family
setting in a custom theme. Then when you apply the custom theme, all the fonts are changed
immediately. This is also a great question, because we now have the ability
to set the font in a custom theme, and per short (perhaps we should also expose it
in an app settings, but that will be later on).
Okay. And if in that situation, if you set the
styling in the theme, it applies to everything, and then w in and changed it in individual charts,
would that chart setting override the theme?
Yes. That's the beauty of the priority.
So, we have the theme settings which could be overwritten by perhaps coming app
settings which could be overwritten by chart settings which could be overwritten by measure
settings. So, this all, this order of things; and I would like to keep that that way.
Otherwise, it gets really confusing.
Okay, next question: could you show how
to make a filter pane collapsible?
Currently, the filter pane collapses when
there's not space enough for it to expand; there's no space for the scroll bar. So,
it collapses down to a drop down instead; but actually it's a really good question, because
this is one of the new styling options in the next set of features for the filter pane, that
we will have a setting that you could decide whether the filter pane should always collapse,
never collapse, or collapse by Auto. Of course, if you make the window so small you can't see it,
they will be moved into what we call the overflow section where you have this expand button,
and you have the list of all fields.
It's nice to know what's coming. That
sounds really exciting. Are there any style templates or demo apps available to review?
Yeah. There's a bunch of demo apps. You have the demos at Qlik.com; you have the visualization
showcase app; you also have the What's New app which is possible to download; and then you
have seven apps called Top 10 Tips apps for visualization development in Sense. Then we also
have the Visualization Vocabulary app; and we also try to bundle an app with every new release;
and you can find that in the Tech Preview.
Okay.
Especially with the new Layout Container. Wxpect us to have more examples. Also, check out the
Community. I highly anticipate that people will be building really cool dashboards that they want
to show off. Also take a look at LinkedIn. There will be a lot of people posting the most awesome
Qlik Sense dashboards that you can imagine.
When will the Rich Text Object be available?
Yes. So, as long as you don't take any decisions on buying futures, then I can reveal my best
estimates. The new text object will definitely come within this year. Whether it will make
the November cutoff for the November release for on-premise, it's still in the air. So,
but it definitely during November on SaaS.
Is it possible to import a chart
from Excel in Qlik Sense now or maybe even copy paste into a rich text object?
So, my understanding is there is no direct way to import the charts. What you would look to do is
bring in the underlying data from Excel, and then build a native Qlik chart; and the advantage of
that native Qlik chart is: then it's completely interactive, it's explorable. Excel charts
are (you know) quite fiddly and hard to build; then they give you a fixed view. Whereas building
out native Qlik charts is definitely a better option there. You could bring it in as a static
image file, but that kind of breaks the user experience of interacting with objects and data.
The next question is another follow-up and that: the values in an ad-hoc table in a
rich text object will still change on the selections or are they static?
So, the table function in the new text objects is more for formatting. It allows you
to place text in columns; to have equal spacing; to make them like a metrics table; is not
meant to be a replacement of anything; it's purely for formatting.
Okay. It is what it says it is: text.
Yeah.
Next question: a user who subscribes to a chart, will they
be notified if I create a public bookmark?
So, I can take that one. So, subscribing to a
chart or monitoring our chart anything that is a personal thing will not really know that, for
example a bookmark is applied or a bookmark has been created, because the bookmark is against
entire data model. Even if it feels like you're in a bar chart; you're doing selection against
the bar chart; you're clicking Save Bookmark; the chart doesn't know that that is
where the selections are done. So, it is in the data model that selections are done;
and that's very separate from the front-end UI.
Okay, that makes sense. Thank you for
clarifying that. And the next question: where can we find some documentation on those
Search Expressions Patrik that you were showing?
Sure. I saw that one coming up. There is this
post by Arturo, and he made this really cool Cheat Sheet that's available. So, just go Qlik
Sense Cheat Sheet version 2.0; and it's a PDF that you can download. It's available in multiple
languages, and you can see here for example: what are some of the different search options
can do; how to use a wild card search; how to use fuzzy search; modifiers… So, it shows
you kind of some of the options that are available instead of just clicking a value; or you're
searching for a value within the this box.
That's great someone's already put together
a cheat sheet for everyone to use. I love it, thank you. Next question: how can I send
specific users a public bookmark link?
So, within the app, within the system, there is
no possible way of saying ”share with a certain person.” So, this will be you create a public
bookmark; you get the link to the bookmark; they use an external tool (whatever
communication platform you have), and send that to your colleague or other user.
Okay, and just a couple more questions: are all of these features included
in a standard Qlik Cloud subscription or are some of these add-on features?
So, all of them are included. There's no add-on features that require a different license.
Fantastic. So, everything we've seen is what will be available for everybody,
great. And the last question today: how can I apply a bookmark to a monitored chart?
So, I can do that. A monitored chart is what we call a snapshot. It is a live chart, but
it has the data embedded within the chart; and whenever an app does a Reload, the data is
updated for that snapshot; and that's why it can reside in the Hub without actually having
a connection to the app, and having to spin up the entire app just because you want to see
a KPI in the hub. Which means that: whatever selections was done before you click the monitor
the chart is what's going to remain within that chart. If you want to have a live association,
you want to be able to do selection and so on; you need to go to the monitor chart; you need to
say Go to Source; and then you'll open up the app to charge your app; and then you can start doing
selections and applying bookmarks and so on.
Well, thank you very much gentlemen. This
first Techspert Talks Visualization Day has been really cool. I appreciate you guys sharing
all these exciting app design capabilities.
Yeah. I would like to thank you Troy for
giving us this opportunity to reach out to this channel. I know it's really popular; and
I'm really be happy to be able to tell people about all the new things that are coming
in the visualization space for Qlik Sense.
Yeah. And I'm happy about showing the old
school things; and if there's something new you know about bookmarks that I've missed or
something; send us a comment, because bookmarks is really powerful even if it's really old.
Yeah, pleasure. Thanks Troy! Cheers, bye.
Thank you everyone. We hope you enjoyed this
session. And thank you to our expert panel for presenting. Having Patric, Bruno, and Patrik
share with us has been really special. Here's our legal disclaimer. And thank you once
again. Have a great rest of your day.
