In my old CRM there was a drop down list in the right corner that allowed users to quickly navigate between accounts without going back to the list view. There were also two arrows that allowed you just to jump to the next account without using the drop down. The feature would allow you to stay on the same page but just refresh the data to display the new client that was loaded.
The Queues are a similar idea. I can show a list of clients with a page include and load the clients in. In some ways it is better because it is searchable and filterable. I had 2 questions:
1. When I click on the next account in the list it resets my tabs to the starting point instead of remembering what tabs I had open. I do have the tabs to “remember user’s last tab”. Since it doesn’t remember where the user was it is not getting as much excitement as the old crm’s feature. (If I am updating medical records I always want to stay on the same page to enter data for each client).
2. Are there any creative ways to reclaim the screen real estate. For instance the standard “Create New” Salesforce menu hides away on the left side of the page. It can either be kept open or kept closed. Is it possible to have a similar effect with the Queue? I can keep it open when I am maneuvering a lot and keep it closed when I want more screen real estate.
These ideas aren’t drop dead necessary they would just speed up my UI or make it flexible for both types of users.
Thanks
1.- I think the remember tab is only working with that object (or row, probably if you go to the previous account the tab will be remembered. quick solution, put that tab the first.
2.- To have in the queue the same behaviour than in the left menu you have to do it with javascript. You can make a button to toggle css(display none) in the classes nx-queue and nx-queue-header to hide or show the queue.
Rich - Sounds like you were up late thinking about making your system better. That’s either really cool or really sad. I’m not sure which.
A few responses:
1. We can emulate the “drop down account picker” with the action framework. There have been some posts about arbitrary filters. You can check those out.
2. There are some challenges to a “previous / next” button. Mostly related to interrogating which row in the model should be shown. Its not beyond what could be done in Javascript - but its not 100% declarative.
3. The two suggestions you provided (Remember tabs in queue detail pages and Collapsalbe queues) are definitely on our list. We’ve known about them and they will be fixed. I just can’t say when… Sorry.
Thanks for the good commentary though.
Rich - that is just beyond cool! Thanks for sharing. Consider yourself a poster child for the kind of continuous improvement culture we are trying to point folks to.
Rich,
We are EVER-thankful for your continuous kind words and helping get the word out about Skuid! It’s so neat to hear about all the awesome work you’ve been able to do for your organization. Keep us posted!
Emily
View our Community Site Map
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.