Vizlib Container Grid Changelog

Font settings component displayed incorrectly.

Text alignment settings component displayed incorrectly.

When the users exported data from Vizlib Container, the filters were not applied.

Better handling of errors - Vizlib has committed itself to better handling of Qlik errors. In this release the focus was around 'Error code -2'.

Default view for Vizlib Container Grid - The default view can now be defined in the Property panel under Container Objects. The new Buttons, Always default & Last active, define how the container will behave once the user refreshes the page/re-enters the page from a previous sheet.

Invalid parameters error - When navigating the tabs of the Vizlib Container Grid there was a situation where an error would appear saying 'Invalid parameters.' This has been resolved in this release.

Cloud - Data Export option missing in the Context menu - Missing the option to Export Data on Qlik SaaS/Cloud when an extension is within the Vizlib Container Grid.

Remember Tab state when coming back from the Selections menu. Now using the Vizlib Container Grid you can go from Analyse mode to the Selection menu and back without loosing the tab state you left the Vizlib Container Grid on.

Remember Container Tab on bookmark.

When creating a Bookmark and you are on a different tab other than the default tab, the newly created Bookmark Remembers the tab that was visible on the Vizlib Container Grid.

Note: You must select "Save layout" when creating a bookmark to save the Tabe state within the bookmark.

Unable to view the export options in Qlik SaaS Government - When right-clicking on the Container Grid in Qlik SaaS Government, the Export option for tables within was not being displayed.

Mashup on server results in Windows Authentication Error - Users saw “Windows Authentication” console log error when using icons in the Container Grid tab header.

New Context Menu and improvement to the Snapshot process - We have implemented a new Context Menu for the Vizlib Container Grid. Seen in the images below we have made it possible to use the context menu of master items and simplified the action by allowing you to access the context menu of any chart anywhere when right-clicking inside the Vizlib Container. In the below example the top 2 visualizations are the Vizlib Bar Chart and the Vizlib Table.

Listed below are the steps to access the Snapshot capability for a specific chart:

1. Right-click and access the context menu.

   

2. I can now select the Vizlib Bar Chart's Context Menu

   

3. From the options presented, you can now select 'Take snapshot'. The Snapshot is taken instantly.

   

The Snapshot of the Vizlib Bar Chart is then found in 'Storytelling'.

See below of a video example:

Note: There is no loader to indicate when a snapshot has been completed in this iteration of the Vizlib Custom Snapshot implementation. Please wait for the next release where we will include it. The Custom Snapshot works near instantly so wait 1 second and your visualisation should appear in the Storytelling mode.

Getting logged out of the app (on the current proxy)when using custom virtual proxies with container grid.

Corrected issue with multi select objects when container had an active condition.

Implement true show-hide in hidden mode. If no tab is selected (via condition) the container will be hidden/empty. Before the vizlib wizard was shown.

Implement true show-hide in hidden mode. If no tab is selected (via condition) the container will be hidden/empty. Before the vizlib wizard was shown.

The context menu (right-click) on some objects (ie the native pivot table) was not displayed. When exporting a pivot table a corrupted data message was showing up in some scenarios. When exporting the vizlib pivot table the data was not formatted.

When added items to accordion mode those were not reflected until that item was modified on the property panel.

Export object was not working when a container was within another container. Master Item selector dropdown wizard was not working on IE.

Conditional show/hide wasn't activating the remaining tab if the condition was fulfilled, a manual click was required to activate that MI.