Hey guys - it's What's New in Qlik Sense time and I have prepared a brief video to share some of the awesome highlights in our next release Qlik Sense April 2018.
Highlights include:
Assisted data visualization with Qlik Sense chart suggestions / recommendations
Qlik Sense recommendations make it easier to create a visualization by allowing you to simply drag and drop fields onto your sheets. Chart suggestions are created using the Cognitive Engine in Qlik, which leverages insights from the data loaded and combines them with best practices for data visualization.
NEW Grid Size control
Now with the creation of a new sheet, the application author can choose between 3 grid sizes - small, medium and large.
Maps visualizations improvements
Qlik Sense April 2018 features significant improvements to the built-in maps visualization:
Support for multiple layers.
Labels for point layers and area layers.
Quick look up of countries, divisions, cities, postal code areas.
Circle select with distance measure.
Drill down support.
Layer control, zoom limit and draw order.
English or local name in the background map.
Publishing an app from the hub
In Qlik Sense April 2018 you can publish an app that you have created to any stream for which you have publish access. If you have published an app to a stream, you can move your app between the streams for which you have permission to publish.
Qlik Geocoding A new subscription service part of the Qlik GeoAnalytics product package, that allows you to coordinate geo lookups all the way down to the street level.
Also included:
Keyboard navigation support for Qlik Sense hub
To improve accessibility, Qlik Sense hub now supports keyboard navigation and shortcuts.
Linking Qlik Sense Mobile to third-party applications
Qlik Sense Mobile can now interact with third party mobile applications through a custom generated URL (deep link). The link can be embedded within the third party mobile application, with appropriate selections and filters. Clicking the link opens the app in Qlik Sense Mobile with the filters and selections that were applied during original presentation. As a result, user experience is improved and context is provided when interacting with the app.
Enable anonymous users to export data
From Qlik Sense April 2018 anonymous users can print and export data.
For a complete list of fixes and improvements check out the release notes in the Qlik Help site.
You can download it from our customer downloads site or play with it right now on http://qlikcloud.com/.
Note: Our amazing product content and media team has also produced a number of updated videos supporting this release, check them out here on the Qlik Help YouTube channel:
Hi Richard - sorry for the delay I was on vacation last week and just saw this now - I did send this out to one of our engineers that works with our APIs - but he was out on vacation - and he stated this:
"I am sure it can be done via enigma js" - I added jvs (Yianni) to this comment so he may add more detail. He was on vacation when I asked it, and then I went on vacation when he got back. Just in case - for the future - it may be best to open a new Qlik Community thread perhaps in this section Qlik Sense - Integration, Extensions and APIs - that way others in the community will see it and hopefully you get a faster reply. I will double check with Yianni later today when he is in. Thanks again for your question and sorry for the delay.
I do not see why not! All of the Engine classes are available.
The problem with the anon sessions are that everything the user does, stay on that session only. If he/she closes the browser, all of the doc level changes are lost
That's fine. We removed the virtual proxy since the exportData method now works anonymously, but didn't realise that the call app.bookmark.apply( id ) would no longer work. As such, I'm just looking for the simplest way to re-instate this (while not going back to using the virtual proxy).
I have no experience of using websockets and am only used to client-side scripting, so please forgive my ignorance, but when I read the help on connecting to the Engine API, I am unclear as to whether a virtual proxy is required. It seems to suggest that I can just add port 4747 to the server in the connection script, e.g.
const ws = new WebSocket('wss://server.domain.com:4747/app/'........
