Hi All! As many of you know, I have been pretty scarce around the QlikView community as of late. As crazy as it feels to say it, I am no longer working as a QlikView Developer. I have accepted a new role, in which I will be focusing my time on user experience design and product development. No more editing script for me, I suppose. This is an exciting change, but I will miss QlikView and, more importantly, I will miss the QliKView Community. For now, I will keep my blog around. Who knows, maybe I will post some UX Design insights down the road. Thank you for all your support over the years… until next time!
This isn’t a design post, but I thought you could all relate! Add your favorites in the comments below.
1. The Vague But Desperate Poster
This poster usually includes a desperate plea for help in the title but then no information whatsoever in the body of the post. We can tell you need help, but with what? Help us help you!
2. The Really Important Guy
This poster needs help right now. Drop what you are working on and help him – his deadline is your deadline!
3. The TMI Poster
This poster includes his entire QVW script in his question. All thirty-four pages of it. The error is in there somewhere!
4. The Boss
This poster lists a set of requirements for the application he needs you to build. Oh, and he needs that by tomorrow afternoon. So if you could come in on Saturday…
Flat UI has been the latest trend in interface design and many QlikView developers are adopting its principles in designing dashboards that are clean and easy to read. If you are interested in jumping on the Flat bandwagon, but don’t know where to begin, download my Flat UI QVW below. Based on inspiration from Arturo’s post here and the color schemes listed here, I have put together some sample interface components to get you started. Take a look and let me know what you think. For more information about Flat design and where it originates, check out this link.
When users want to search for a very specific date range, it can be time-consuming to use List Boxes to click and drag through a large date range. In addition, many novice QlikView users do not know that they can use advanced search strings to select a date range (i.e. ‘>=6/1/2010<=7/31/2010'). One way that I have found to simplify this process is by including a Calendar icon in my filters that allows users to input a From Date and a To Date and a button to 'Select' the date range.
To implement this functionality, I use variables to hide the date range selector when not in use, calendar objects to select the date ranges, and an action to select the date range in the date field. As a precaution against invalid selections, I also include an IF statement on the action and an error warning when the End Date falls before the Start Date.
Take a look at my attached example document to try it out. To use, click the Add Filter button in the upper right hand corner, then click the Calendar icon. Select a valid Start and End date and click the Select button. To return to the Filter, click the ‘Back’ arrow icon.
This scatter plot is a simple take off one of my latest projects. The goal was to take a large number of scatter plot variations (x, y, and z axis combinations) and combine them into one interactive scatter plot in order to save real estate. By clicking on the graph icon in the upper right, the user can change the axes, turn the bubble size on or off, and adjust the plotted values. The plus-sign icon opens the available filters and displays the user’s current selections. Take a look, see what you think, and let me know how you would change/improve it!
I really liked the color scheme and tabular layout of QlikView’s Plant Operations application, but I thought it was a bit crowded with so many list boxes on the left hand side. With that in mind, I set out to create a cleaner version that maintains the same functionality but offers more space for graphs and charts. I used a variable to add a filter box in the upper right hand corner, and added a notice to tell the user when the data is filtered. There is still plenty of room for sub-tabs or additional information, I just didn’t have much data. The information contained within this document is from the U.S. Trade Capacity Building Database. Included in the Zip file below is my document and a copy of the QlikView demo. See what you think!
One of the most difficult aspects of QlikView design is anticipating the needs of the end user. A design can look great, but if the interface isn’t user-friendly, then it will be of no use to your clients. When designing for the iPad, I recommend using large scroll bars, easy-to-read font sizes, and large buttons. In addition, make sure your workspace either fits all into one screen or is formatted for easy scrolling. There is a great technical brief about designing for mobile devices at http://community.qlikview.com/docs/DOC-2191. Take a look at the iPad-friendly design I created and see what you think.