Last updated December 7, 2012.
QlikView 11 takes Business Discovery to a whole new level by enabling users to more easily collaborate with coworkers, supporting larger enterprise deployments through enhanced manageability, and delivering an enhanced mobile experience.
QlikView 11 makes it easier than ever before for business users to leverage three important sources of insight: data, people, and place.
Table of Contents
QlikView 11 brings new levels of capability and manageability to the QlikView Business Discovery platform. In this release, we focused our investments on five value propositions:
For more info, see this video, "Introduction to QlikView 11":
Customers can get the latest release of QlikView, as well as the release notes, from our download site at http://www.qlik.com/download.
What platforms does QlikView 11 support?
You can find full detail about supported platforms in the QlikView 11 and QlikView Expressor System Requirements data sheet (download here). Also see the
data sheet, "QlikView Governance Dashboard System Requirements."
We will post info about upcoming service releases as it becomes available.
The differences are:
Small Business Edition (SBE) only supports Windows-based authorization (Active Directory and Windows local users) and utilizes the web server to do the authentication against Windows. So if users are managed in Windows, SBE could be deployed in a DMZ. The SBE license, however, does not allow for external users. Customers that require access by external users should consider QlikView Extranet Server. QlikView Extranet Server allows access by external users and can be used with any user management system.
Yes, you can find a "What's New in QlikView 11" demo app on the demo site here. You may need to click on the QlikView 11 banner to get to the QlikView 11-specific demos.
As of QlikView 11 SR1, QlikView Server includes a real-time (dynamic update) component for accessing real-time data.
QlikView 11 does not include new chart types. Instead, we focused this release on making it easier for web developers to create QlikView extension objects, which enables customers to bring any visualization they want into QlikView and have it be fully interactive just like a native QlikView object.
Just as with QlikView 10, if the servers are properly licensed and configured to cluster, then CALs are shared across the cluster nodes.
QlikView Desktop does not provide direct support for the Mac platform. However, it works very well on Mac with a virtual machine.
QlikView is an in-place upgrade from QlikView 9 and QlikView 10. But for upgrading from earlier versions, more work is required. You can find additional information here:
Please see these additional resources:
Decision making is inherently a collaborative activity. Social Business Discovery helps organizations leverage peoples’ shared insights in the decision-making process. With QlikView 11, business users can ask and answer streams of questions in formal or informal groups, in real time as well as asynchronously. Together, QlikView users collaborate to explore data and forge new paths to discovery and insight.
The new social Business Discovery capabilities in QlikView 11 build on existing collaboration functionality in QlikView, including collaboration objects, shared bookmarks, and Microsoft Office® integration.
Check out this video: "Social Business Discovery:"
In QlikTech’s vision of the future of Business Discovery, a social and collaborative experience is front and center. Using concepts from the consumer world, social Business Discovery enables business users to collaborate on discoveries and generate multiplicative insights. Users collaborate on creation of analytic apps and can define and answer their own questions in teams and groups. They communicate with each other in real time and asynchronously to collaboratively explore data, forge paths to discovery and insight, and arrive at decisions. They explore Business Discovery apps through a social lens to find the data and insights that are most relevant to them. With social Business Discovery, people can make unexpected discoveries that lead to better decisions and organizations can streamline the decision making process.
Social Business Discovery is for decision makers at all levels of an organization. QlikView’s social Business Discovery approach means workgroups and teams can collaborate on innovative decisions faster than ever by collectively exploring data, anywhere, anytime, on any device. And they can capture the conversation so there’s accountability and a decision history trail. QlikView also empowers IT managers and analysts. Unified management capabilities and the ability to more rapidly deliver relevant, segmented, live data and self-service analysis means they can serve the business like never before.
QlikView 11 does not provide direct support for analyzing social media data. However, partners have built connectors and applications that do just this, using prior versions of QlikView. For example, Industrial CodeBox built QVSource, which is a set of QlikView API connectors to a variety of web services including Facebook, LinkedIn, and Twitter. And TIQ Solutions has built a sentiment analysis app called Sentival (check out the Sentival demo app).
QlikView apps and objects can display alongside other related decision-making inputs such as documentation, traditional BI applications, or CRM or supply chain applications. We have customers using QlikView web parts for use with Microsoft SharePoint (download data sheet here), which enables business users to embed individual QlikView objects such as charts, list boxes, and graphs into SharePoint portals and collaboration sites. This integration helps organizations increase the return on their investment in SharePoint by improving collaborative decision making and helping to preserve a record of how decisions were made.
See these resources for additional info:
With annotations, QlikView users can now engage each other in discussions about QlikView content. A user can create notes associated with any QlikView chart, graph, list box, or other object. Other users can then add commentary to create a threaded discussion. Users can capture snapshots of their selections and include them in the conversation so others can get back to the same place in the analysis when reviewing notes and comments. QlikView captures the state of the object (current selections), as well as who made each note and comment and when, for a lasting record of how a decision was made.
Annotations are available in QlikView Server Enterprise Edition (EE), QlikView Server Small Business Edition (SBE), and QlikView Extranet Server (QES). Annotations are not supported in QlikView Information Access Server (IAS).
Annotations work with the Ajax client and Internet Explorer plug-in. They work with QlikView Desktop only when the user opens a document on QlikView Server from within QlikView Desktop. (Annotations are server based.) Annotations work on all mobile device platforms on which QlikView supports HTML5 browsers (Apple iOS devices and Android smartphones and tablets). For this to work properly, the device must be connected to the QlikView Server in full screen mode, not small screen mode.
Users can create annotations at the object level (per chart, graph, list box, etc.), not at the document or data level -- though users can access existing annotations at the document level via a toolbar option.
Users can take snapshots, which preserve the state (user selections) of the application. (Snapshots are like bookmarks, except a snapshot is specific to a discussion thread.) Users can post snapshots in notes and comments. Others can click on them to view the selections made by the person who created the snapshot. Keep in mind that snapshots are not static screenshots. They preserve the state of the application, but the underlying data may have changed. So that users know the data may have changed, QlikView Publisher posts a reload date/time stamp comment into the discussion thread.
Annotations in QlikView 11 support only text and snapshots.
Not at this time.
Yes, users can create annotations during collaborative sessions. However, all annotations will be attributed to the user who initiated the collaborative session.
Yes. When determining who can view a note or comment, users can choose from these three options: Only me, specific people, or anyone who has permissions to view the object.
Annotations are stored in the .SHARED file along with other collaboration objects.
There is an impact on the shared file. We will be monitoring cases where users see a performance degradation due to having a large body of annotations in place. We don't anticipate an effect on memory utilization.
Annotations are preserved during reload. If an object is removed, the annotations are also removed.
An individual annotation can be limited to specific named users. It can also be restricted to just the users who have permission to access an object.
Yes, users can modify their own annotations after they have been saved. Users cannot modify annotations created by others.
When using the annotations capability on iPad, users can create snapshots just fine. They can also click on snapshots others have created in notes. However, there is a bug in QlikView 11 that prevents users from interacting with the snapshots associated with comments (replies in the thread). Unfortunately, due to uncertainties regarding potential related problems and program priorities we cannot guarantee a fix date for this bug at this time.
Not at this time.
Using the QlikView Management Console, administrators can remove entire notes, but cannot remove individual comments from notes.
Shared sessions improve the quality of business decisions for geographically-distributed and mobile users who work in teams to analyze information and make decisions. Users can jointly interact with a QlikView app in real-time―sharing selections and testing scenarios together to better uncover insights and solve problems.
A user can invite others—even those who don’t have a QlikView license—to join a session by distributing a one-time-use URL. Each participant interacts with the same QlikView app at the same time, for the duration of the session—without having to pass control from one to the other. This new capability is designed to augment a voice conversation. Collaborative sessions work on tablets and smart phones as well as desktop and laptop computers.
No, collaborative sessions are fully interactive for all participants. All participants can make selections and interact with the QlikView app in real time. The session ends when the person who started it ends the sessions or closes the application.
No additional license is required for collaborative sessions. Licensed users can initiate a collaborative session with anyone, including non-licensed users.
Yes. It is up to partners to turn off this feature if they don't want to make it available to their users.
Collaborative sessions are available in QlikView Server Enterprise Edition (EE), QlikView Server Small Business Edition (SBE), and QlikView Extranet Server (QES). They are not supported in QlikView Information Access Server (IAS).
There is no known hard limit on the number of people who can participate in a collaborative session. We have tested it with ~19 people. But the realistic limit is the number of people who can realistically have a productive conversation. We recommend limiting it to no more than a few. Otherwise the interaction with the QlikView application could get confusing because QlikView does not identify which participant is making selections in QlikView.
Yes. The invitation link is good for 15 minutes. After that, it will not work. During the 15-minute period, invitees can forward the link to others, who will be able to join the session. Prior to joining a collaborative session, individuals are invited to choose a user name. If "Donald Duck" joins the session, the initiator will be able to see this.
No. Keep in mind that non licensed users may participate in collaborative sessions. When invitees join a collaborative session, they give themselves a user name. The initiator of the session can then see that that user has joined.
Yes, collaborative sessions work on tablets and smart phones as well as desktop and laptop computers. Keep in mind that on smartphones, collaborative sessions do not work in small screen mode -- it works only in full-screen mode.
No application development is supported on iPad at this time. A user on an iPad could, however, participate in a shared session as a viewer while another person using the Ajax client on a laptop is creating and modifying objects.
Collaborative sessions work only with the Ajax client. They do not work with the Microsoft Internet Explorer plug-in or QlikView Desktop.
Users can view and create annotations during collaborative sessions. But keep in mind that during a collaborative session, all annotations are attributed to the user who initiated the session. Also: each participant in a collaborative session must click "show/hide notes" to have the annotations object appear on their screen. And participants do not see each other creating notes/comments during collaborative sessions -- though after someone creates an annotation and clicks "done," others in the session will be able to see it.
An administrator can control collaboration sessions on a server and on individual documents. But the rights of the initiator are passed to the participants in the session. Caution: The initiator of the collaborative session must think it through before inviting others to participate in collaborative sessions. All users in a shared session can see and interact with the app as if they were the license holder, with one exception: while a collaborative session is under way the ability to download and export to Excel are disabled.
All participants must have access to the QlikView Server. If a QlikView app is behind the firewall, all participants must be able to get to the server via the VPN.
Collaborative sessions have no known impact on application performance or the size of the shared file. There is a small impact on memory utilization for each additional user. But as each individual user is sharing the same session, the impact is much smaller than if each user were to start their own individual sessions.
One of the core capabilities of QlikView is associative search. QlikView 11 takes our associative analytics to a whole new level.
Business users can quickly gain new kinds of insight when analyzing information in QlikView, with new comparative analysis options. App developers can now create multiple selection states in a QlikView app; they can create graphs, tables, or sheets based on different selection sets.
Business users can then compare multiple selections of data inside one app, one chart, or one object, to spot trends, outliers, or differences. This makes it easier for information workers to gain new insights into patterns of use, opportunities and threats, and relative performance.
Yes, users can compare multiple different sets of data. The data can be displayed in a single chart or in multiple charts.
Comparative analysis and set analysis complement and extend each other. QlikView developers can use sets to perform aggregation functions. Aggregation functions normally aggregate over the set of possible records defined by the current selection. But an alternative set of records can be defined by a set expression. Hence, a set is conceptually similar to a selection. Set analysis provides a method of defining groups (sets) of information that are independent of the current selections. Comparative analysis enables business users themselves, on their own, to create comparisons using multiple groupings of their choice. It could be used, for example, to compare sales for different products or demographics or analyze consumer purchasing baskets.
You can see examples of comparative analysis in action in these demo apps, which are accessible on the QlikView 11 demo site:
With mobile Business Discovery, information workers can take advantage of being in a particular place at a particular time and generate insights “on location.” QlikView on mobile delivers full Business Discovery and the power of QlikView to mobile devices connected to a server—including the associative experience, interactive analysis, access to live data, and search. For Apple iPads, QlikView also provides offline views of data.
Yes, QlikView provides offline views of data for iPads. The QlikView for iOS iPad and iPhone app, available in the Apple App Store, complements QlikView on mobile browser-based access. The app provides a native user experience for QlikView AccessPoint, while extending and enhancing QlikView’s universal HTML5 approach for analytics applications. Users get all the power and flexibility of QlikView Business Discovery when connected, and when using an iPad can take advantage of a new disconnected mode for offline access. And there are no additional costs, because the app is a free download and works with any QlikView 11 server license. For more information see the QlikView on Mobile data sheet.
Yes, for Apple iOS devices. This app is an HTML5 wrapper. The iPad version provides offline views of data.
Out of the box, location awareness is not supported at this time. However, with document extensions in QlikView 11, customers can create this functionality on their own. See this demo app: GPS Store Finder.
No, there is no additional license cost.
No, QlikView 11 does not include a mobile SDK.
See these resources for additional info:
Organizations can get better usability and faster time to value from their QlikView investments by giving business users access to apps via native HTML5 browsers on Apple iPads and Android tablets. This means users get a seamless experience with their QlikView apps across tablets and desktop and laptop computers. They get the same functionality and interactivity, without waiting for developers to create new versions of the app for each specific mobile platform.
QlikView 11 delivers mobile functionality for Apple iOS and Android tablets and smartphones. QlikView supports Android tablets when the following conditions are met:
Currently our HTML5 web apps support only Apple and Android handhelds. Because many Blackberrys are older devices that don't fully support HTML5 (and many are non-touch), we don't have a web-based solution for them at this time.
Organizations can get higher adoption of Business Discovery apps, and more value from their QlikView investments, by giving business users the ability to interact with mobile QlikView apps through a full set of native, intuitive, touch-based gestures. QlikView 11 on Android tablets supports many gestures including hold tap on a chart, get the green square, resize and select. We have tested this on Samsung Galaxy Tab and Motorola Xoom.
No, though with each new release we put more and more functionality in the Ajax client. QlikView Desktop provides functionality for designers and developers beyond the functionality in the Ajax client. Ajax, for example, doesn't support custom objects, automation APIs, and client side APIs. For more information see the QlikView Server and Publisher manual (download the manual here).
No. QlikView users can perform most of the same modifications to QlikView apps while using tablets that they can make using the Ajax client on their desktop or laptop computer. But QlikView Desktop is the primary development environment for QlikView apps, whether those apps are deployed to desktops/laptops or mobile devices.
QlikView supports Apple iOS and Android smartphones. We have not yet tested it for BlackBerry smartphones. Customers that want to support BlackBerry smartphone users can do so with our older native BlackBerry client. QlikView on Mobile has not been tested with the browser on Windows Mobile devices.
When a user points their Apple iOS or Android smartphone to the application on QlikView Server, they will have the option to interact with the application in small screen mode. When they choose this mode, they will see all the sheets (tabs) and objects in the application represented by icons or thumbnails in a tile view. They can swipe on the screen to scroll through all the available objects. To access an object, they tap on the tile representing that object. They then see just that one object on the screen. They can interact with that object (making selections) just as they would in full screen mode.
Information workers get improved usability by accessing QlikView on their Apple and Android smartphones using the device’s native HTML5 browser. When QlikView Server detects the user is accessing an app from a smartphone, the server automatically displays the app on the device one object at a time. For small-screen devices such as iPhone and Android Phone, single-object display mode delivers an intuitive user experience without the need for developers to rebuild apps.
With Business Discovery, there are no “end users.” Instead, every user is the start of something, a node in the creation of insight that is no longer highly centralized and radial. A rapid analytic app platform helps developers and business users contribute to the creation of analysis quickly and simply―without requiring extensive ongoing involvement from experts.
QlikView 11 includes new and improved capabilities that meet the needs of QlikView app developers and third-party software developers―as well as the needs of business users who want to create their own analytic apps.
Please see these additional resources:
QlikView 11 makes it easier for developers to extend the platform.
No, QlikView does not support Eclipse. Our Workbench product, which is used to create web pages that embed QlikView -- or to build extension objects and document extensions, requires Visual Studio.
QlikView supports export to Excel .XLS but not .XLSX.
QlikView does not support emailing Excel output via QlikView Publisher. Users can, of course, email Excel files to others after exporting the data from QlikView.
QlikView 10 supports Iframe (inline frame). In QlikView 11 we also offer an HTML DIV tag option, which defines a division or a section in an HTML document. This should make integration with enterprise portals easier. Customers will still need to build a portlet around the DIV tag content and address security requirements
Business users with the Ajax browser client gain a more streamlined, effortless experience when working with data from external analytic systems. They can interact with data returned from other analytic systems directly within QlikView—without having to access the external system in a separate, disconnected mode. Like the extension objects we introduced in QlikView 10. Once created, document extensions can be reused in multiple QlikView apps.
The new Visual Studio project template includes all the files needed to build a working QlikView extension object and publish it to QlikView Server. The new Visual Studio project template also includes:
Developers can use QlikView Workbench to create QlikView extension objects in Microsoft Visual Studio more quickly and easily than ever before.
QlikView customers can download sample extension objects in a demo app called Extension Examples (download from the demo site here). This demo app includes an organizational chart, whisker pie chart, geographic heat map, bullet chart, and calendar view. Customers can find additional sample extension objects in QlikCommunity.
QlikView extension objects work only with the Ajax client and web view mode in QlikView Desktop. They do not work with the IE plug-in.
For more information, see this blog post, "QlikView Connector for Informatica PowerCenter Now Available" or download the data sheet, "Data sheet: QlikView Connector for Informatica PowerCenter."
Benefits of the QlikView Connector for Informatica PowerCenter:
QlikView 10 and higher.
The QlikView Connector for Informatica PowerCenter supports the following Informatica PowerCenter versions on Unix and Windows: 8.6.1 and 9.0.1.
QlikView for Salesforce.com is a native connector within QlikView that provides a transparent and intuitive means for QlikView developers to access data from Salesforce.com. Installed as an add-on adapter, the .dll-based connector instantly offers a view into all out-of-the-box and custom fields within a Salesforce.com deployment, including Chatter data and archived data. Because it is a native connector, the speed at which data is accessed and loaded into a QlikView application is extremely fast. With this connector, QlikView customers can quickly and easily bring their Salesforce.com data into QlikView for exploration and analysis. Here is a blog post that contains more information, "QlikView Salesforce Connector Version 11.00 Now Available." More detail is in the data sheet, "Data sheet: QlikView for Salesforce.com" (download).
Customers can download the connector from the QlikView download site.
This version of the QlikView Connector for Salesforce is DLL (dynamic linking library) based and is available for both 32- and 64-bit systems. It contains some key enhancements:
The QlikView Connector for Salesforce.com recognizes a mix between SOQL and SQL that introduces both limitations and enhancements to SOQL. These changes have been made in order enable better communication between QlikView and Salesforce and for the sake of backwards compatibility. SOQL-style relationship queries are not enabled. The SQL-style date and time format “YYYY-MM-DD hh:mm:ss” is now automatically converted to the SOQL date and time format “YYYY-MM-DDThh:mm:ssZ.” Also, it is now possible to use an asterisk (“*”) in place of a field list. Similar to SQL, the asterisk acts as a wildcard that selects all fields in the table. Qualifying the field name by prefixing it with the name of the table is not allowed in the SELECT Statement.
This release of the connector recognizes a few more data types: “anyType”, “time”, “encryptedstring”, “masterrecord”, and “DataCategoryGroupReference.” The type “time” denotes a time of day, as opposed to the type “datetime” which holds both a date and a time of day.
The QlikView Connector for Salesforce.com works with QlikView 8.5 and higher.
QlikView 11 delivers new and improved capabilities to make it easier for developers and business users to create QlikView applications.
Using a new option in the File menu, QlikView developers connect a QlikView app to a source control system such as Microsoft Team Foundation Services or Apache Subversion. The source control system then provides change tracking and rollback and can merge changes made by multiple developers. Each element of the QlikView app―such as script, properties, and user interface object definitions―is stored separately and can have changes tracked separately.
For more information, see the QlikView Technology White Paper, QlikView 11 Source Control Walkthrough.
Benefits of version control integration include:
Developers can now use comments and tags during document construction to limit field selection (using search criteria), provide labels, and support data structure analysis. This expands upon the comments and tags introduced in QlikView 10.
When creating or editing QlikView applications, developers can more easily search for and find relevant data fields and visualization objects using comments, tags, and labels.
See these links for more information:
QlikView developers and business users can now create QlikView charts, graphs, list boxes, etc.—all of which can be shared as collaboration objects—using improved dialog boxes, drag and drop, and visual assembly. QlikView presents the most frequently-used menu items at the highest level, with others nested below.
Creating QlikView objects (e.g., charts, graphs, and list boxes) in the Ajax browser client is easier than ever before, especially for non-technical users.
Granular chart dimension control enables developers to more easily create meaningful comparisons among dimensions in a chart.
Developers can more easily display the lowest values, first values, top values, etc., in a single chart. In previous releases of QlikView, his required the use of macros and advanced aggregation functions.
Developers can now manipulate QlikView objects to provide refined context based on a user’s action, selections, or role, or any underlying data condition. Developers can specify conditions that control when a dimension or expression is used on a chart, or when a table is used, based on any criteria.
One use of this new capability is to more easily support ad hoc report creation. (For an example, see the Reports tab in the What's New in QlikView 11 demo app.) Overall, conditional enabling of dimensions and expressions improve the user experience.
Container objects give QlikView designers a means of presenting multiple perspectives on a set of facts in a single, space-saving object. In QlikView 11, designers can now create QlikView apps that are more efficient and user friendly by placing multiple objects on a single tab, snapped together in a grid.
Container object enhancements make better use of screen real estate. Users gain consolidated viewing context.
In the Ajax client, we’ve improved the way users navigate from one sheet (tab) to another within a QlikView app. Users can now scroll through tabs to find the sheet they want, or select a sheet from a drop down menu. They can also add new sheets more easily.
Improved tab navigation makes it easier for users to find QlikView content and add new sheets (tabs).
With Direct Discovery, a capability of QlikView 11.2, QlikView brings relevance and context to Big Data. QlikView Direct Discovery provides connectivity to SQL-based data sources such as Cloudera Impala and Teradata Integrated Data Warehouse. Within a single app, users can work with data stored in Big Data repositories as well as data in QlikView’s in-memory engine. With this hybrid approach, users get the associative experience across all data in the app, regardless of where it is stored—a capability unique to QlikView.
QlikView Direct Discovery delivers thorough, unified analysis. Users can easily expand their analysis to include Big Data sources that have not yet been tapped. They can drill down from in-memory data sets to detailed measures stored in Big Data systems. Direct Discovery delivers the same easy-to-implement, rapid app development experience to data sets that were previously used separately, or not used, because of their bulk and the development effort required.
No, it does not.
While Business Discovery platforms must deliver business user benefits such as insight everywhere, mobility, and a social and collaborative experience, they can’t stop there. Business Discovery platforms must also meet IT requirements for security mechanisms to protect sensitive data, the ability to crunch massive volumes of data quickly, and advanced yet easy-to-use administration tools. QlikView 11 is packed with new and improved capabilities designed to improve performance of large deployments and make them easier for IT pros to secure and administer.
QlikView 11 provides several new and improved capabilities to improve system performance.
QlikView 11 introduces important changes to the QlikView Publisher component, which is used for reloading QlikView apps and distributing derivative QlikViews. We’ve significantly improved the performance of QlikView Publisher reload and loop and reduce tasks.
Publisher performance improvements mean fresher data for business users.
Reload requires a QlikView engine which is terminated on completion of the reload. Another QlikView engine is used for distribution, which is also terminated on completion of the distribution.
We added an additional algorithm for load balancing, in deployments that utilize QlikView Web Server, to help QlikView administrators better manage a cluster of QlikView Servers. QlikView Web Server can now route traffic in several ways: randomly, by RAM (random access memory), and/or by CPU (central processing unit) utilization. These factors work in tandem. Administrators can configure the environment so that, for example, a large QlikView app is not moved to a server that may have plenty of disk space but is overloaded with processing.
These improvements help QlikView administrators better manage a cluster of QlikView Servers.
Administrators now have control over which nodes in a cluster execute which apps. For example, administrators can choose to assign larger QlikView apps to larger servers and can achieve better utilization of commodity hardware for smaller loads.
With more granular clustering, QlikView administrators managing deployments that have large data volumes can reduce the complexity and cost by optimizing resources.
We have usability tested the unified QlikView 11 management console for significant improvements in speed and ease of use. We’ve made improvements in areas like task searching and filtering, task execution history within the status task page, task templates and creation wizards, and event notifications (such as when a service is down).
The QlikView management console improvements in QlikView 11 save administrators time.
In QlikView 11, the management console UI was changed to give administrators a much better experience overall, to better manage tasks, shared objects, etc. QlikView 11 also provides better and easier access to the logs. In this way, errors and triggers are much easier to manage. In addition, a global services error bar has been included, which makes it easier to detect events such as a service going down.
No, this is not supported.
AccessPoint is the QlikView portal where users can find and access QlikView apps to which they have security rights.
See below screen shot. New and improved capabilities include:
With QlikView management services API enhancements, administrators can programmatically interact with the QlikView management service to customize or automate various aspects of QlikView Server and QlikView Publisher administration.
QlikView 11 includes more than 50 new QlikView management services API calls that support automation in areas like collaboration object management, directory service connector lookup and validation, importing of tasks, remote administration, log file access, QlikView Server and QlikView Publisher license configuration, and section access management.
The QlikView Management Services API enhancements in QlikView 11 enable additional automation beyond what was possible with QlikView 10.
No, AccessPoint does not support SAML.
We introduced changes to user management in QlikView 10 that made it easier for administrators to see which users have access to which documents. In QlikView 11, we changed the QlikView Management Console user interface to give administrators a much better experience overall. They can better manage tasks, shared objects, etc. However, no new changes were implemented to give increased visibility into user authorization.
New optional settings within QlikView Management Console enable administrators to more effectively audit user interactions. Administrators can audit QlikView usage not only at the system level (the entire QlikView Server), but down to the document level.
Document-level auditing helps administrators improve risk management and compliance. Administrators can improve the accuracy of audit results when conducting a usage audit by tracking which users access what documents, and performing this analysis retroactively.
The audit log on QlikView Server captures information such as a time stamp, the name and path of the QlikView document / application, name of the user, type of selection action (e.g., selection, bookmark) made, and information about the type of selection or the application of a bookmark.
QlikView administrators can now assign privileges at both the document and user level.
QlikView administrators can improve control and manageability when applying privileges for document download and/or data export.
QlikView developers and architects can now manage data by creating QVD (QlikView data) file layers from a centralized, server-side, QlikView Publisher location. Developers and architects can now create QVDs without the additional overhead of managing a QVW file solely for the purpose of creating a QVD; they can create QVDs via a script. Optionally, QlikView administrators can also assign NTFS (New Technology File System) security to QVDs using this mechanism.
Central data management is easier than ever before for QlikView developers and architects.
Correct. QVDs do not have to be generated in the script of a QVW now, for basic QVD generation tasks.
QVD loads should support anything that can be done in the QlikView script. But we recommend that customers use Publisher to generate QVDs only for basic implementations. For more complex implementations, we recommend customers continue to use QVW files as the engine for creating QVDs.
The QlikView Governance Dashboard helps IT professionals maximize data governance and optimize their QlikView investments by discovering how QlikView is used at a granular level. With this knowledge, they can introduce more manageable and repeatable processes when developing QlikView applications, as well as address data lineage and impact analysis questions. They can also ensure compliance with regulatory acts, policies and standards that require an understanding on how data is created, protected and delivered. The QlikView Governance Dashboard is a free QlikView application available on QlikMarket (market.qlik.com).
See these additional resources: