Databases Reference
In-Depth Information
3. The
Getting Started
wizard dialog may instantly appear, asking you to select
a data source. We will, for now, ignore it. Click on
Cancel
.
° Don't worry if this dialog window doesn't appear when
launching QlikView.
4. Go to the
File
menu again and click on
Save as…
. We will save the
document inside the
Airline Operations\Apps
folder and name it
Airline Operations.qvw
.
Now that we have our environment ready, let's move on to create our
analytical application.
QlikView documents are often referred to as 'applications' or
'apps' as they offer a much more interactive experience than the
term 'document' would imply. In this topic, we will be using
the terms 'document', 'application' and 'app' interchangeably.
Creating the app
We can think of a QlikView document as being composed of two major elements:
• The dataset that the user analyzes: This is the backend of our QlikView
document and includes all of the source tables needed to build a data model,
as well as the logic to update its source data.
• The user interface through which the user analyzes the data: This is the
frontend of our analytical app and includes the objects contained in the
document (like a listbox to make selections and filter data), or the charts
and tables used to visualize the information.
In hand with the elements described above, we will break the construction of our
QlikView document into two major phases:
• Constructing the data model
• Designing the user interface
However, before moving on to create our QlikView document, we should have a clear
understanding of the business-side requirements for our app, so the construction and
design phases are fully focused towards meeting those requirements.
The requirements
In our SiB scenario, HighCloud Airlines executives have determined that they would
benefit from a business discovery application that helps them answer questions
around the following topics:
