TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Print and Action Buttons in Drop List rather than individual
It would clean up the page if Print Buttons and Action buttons were placed in a drop list (like the Export function on a View header)

User Experience

Date Created
7/13/2015 10:32:47 PM
Date Updated
2/2/2017 10:20:28 AM
Promoted By
Dale OliverTony Hawkinsgerardo garcia
Philipp Matuschka (MMB) 7/21/2015 4:57:12 AM
If you do implement this then make it a configurable choice as it could lea to additional clicks which are not always desirable.
basenine 7/21/2015 4:58:59 AM
@Phillipp....definitely agree --> good idea 😃

Tony Hawkins 7/21/2015 5:20:32 AM
The above make sense but just to endorse the original concept I have 23 buttons on one of my views and it is very cluttered
Philipp Matuschka (MMB) 7/21/2015 5:41:08 AM
I guess I just haven't reached those heady numbers yet and where you only have 2 or 3 buttons, the drop list is an unnecessary extra click.

Another possible approach is to have the buttons on the right or left side of the screen.

There is also an idea somewhere in this forum about allowing buttons to be seen as icons, with the meaning of the button being a tooltip.

Perhaps all of these could be merged into one good design
basenine 9/3/2015 11:25:51 PM
If we could get some of these:

Into a drop list like this

Tony Hawkins 9/4/2015 4:52:42 AM
Maybe one dropdown for documents and one for (workflow)actions or the ability to add buttons to customisable drop down lists.
basenine 9/4/2015 5:10:12 AM
Yes. That's the idea....I definitely did not make that clear.
One drop list for each type
Thanks for the pick up 😀
Kirill Bondar  Staff  9/10/2015 6:17:55 AM
For custom buttons and documents we've added new Category property.

If category is not set, the item is rendered as a push button named after the item - as it is now.
If category is set for a single item it is rendered as a push button, but named after category rather than item.
If category is set and shared between multiple items they are rendered as a dropdown button named after category with items forming a menu.

Custom buttons and documents are processed separately; their categories are not shared. For example:

Button 1 (No category)
Button 2 (Category 1)
Button 3 (No category)
Button 4 (Category 2)
Button 5 (Category 1)

are rendered as

Button 1 - push button
Category 1 - dropdown button with items Button 2, Button 5
Button 3 - push button
Category 2 - due to single item Button 4 in a category it is rendered as a push button.
Tony Hawkins 9/10/2015 6:37:24 AM
Thank you. That is great.
basenine 9/10/2015 6:45:36 AM
Nice work guys. Can't wait to implement it across the board

Thanks for your consideration
Robert Gustavsson 9/10/2015 7:14:33 AM
Looks good except it should be possible to use the same button name under different categories.
Michael Ver Duin 9/10/2015 10:22:10 AM
I've added catagories, but they buttons don't collapse into a dropdown. Will this only work in record view? It would help if this also worked on a table view for my buttons on the left hand side of my records
Kirill Bondar  Staff  9/10/2015 10:36:23 AM
@Michael: we'll think to improve this in the future
Michael Ver Duin 9/10/2015 10:50:53 AM
Thanks, I have to abbreviate my buttons right on a table view because otherwise I'd have more buttons than data!

Great improvement though!
calvin peters 9/10/2015 12:11:00 PM
I think I could get some real mileage out of "Colorization" based on "Category" much like the side bar menu has now for grouping categories of views.

Users are predictably unattentive to text and accutely aware of Graphics and Colors when quickly scanning for action buttons. Especially on mobile platforms.

That would be a big help.

basenine 9/17/2015 12:23:14 AM
Another nice addition would be to be able to multi select documents (in Setup) and assign all the same category.

calvin peters 9/17/2015 9:47:47 AM

That would be a solid enhancement.
basenine 10/2/2015 1:18:25 AM
Could this be extended to the Table view as well please?
basenine 3/29/2016 5:02:40 AM
BUMP for TABLE views please...


Kirill Bondar  Staff  4/6/2016 4:43:33 AM
Works now in table/timeline/tile views
basenine 4/6/2016 4:57:14 AM
Michael Ver Duin 4/8/2016 3:32:26 PM
Woo Hoo! Works awesome!
James Ross 4/13/2016 1:57:18 PM
Love it. Its so much neater. Thanks
Rick Cogley 4/14/2016 6:27:49 AM
Nice enhancement! One thing I noticed: when you have 2 buttons that are set up to show "either or", if you apply the same category to both, whichever one is active just gets the name of the category, and appears (of course) as a single button not a dropdown. This tripped me up when I forgot the logic I programmed to show either or.
basenine 4/14/2016 6:31:38 AM
Yes - good point @Rick....consistency is required esp for end users
Philipp Matuschka (MMB) 10/6/2016 7:14:21 AM
I've just come across a similar thing to Rick on 4/14/2016. I have a category WORKFLOW with five different actions below it, 2 or 3 of which are usually available depending on filters. When only one is available the button text is WORKFLOW. The problem is that the user doesn't know which of the underlying buttons actually lies behind that word.

So it would be great if when only one Button is available in a category, it shows the button text, not the category text.

Philipp Matuschka (MMB) 1/30/2017 12:59:09 PM

Could you have a look at the last comments raised by Rick, Basenine and me. I guess this shouldn't be too hard to do but would make such a difference to user experience.

Kirill Bondar  Staff  1/31/2017 9:47:38 AM
It's not hard to change, but we are afraid to break some existing logic.

One can set up multiple versions of the button or document, each one available for particular role(s) (that's - mutually exclusive) and use category to hide name variations (due to name uniqueness requirement).

@Rick: haven't you used this approach in one of the databases?
Philipp Matuschka (MMB) 2/1/2017 6:58:47 AM

Your suggested workaround only works in the very specific circumstance of the presentation of buttons being role dependent. The scenario for which this enhancement is being requested is much more dynamic than that.

Fear is not something I normally associate with you guys.
Are you afraid of breaking logic on your side. Or are you afraid that logic which has been implemented on our side assuming the current behavior will be broken by making this change?

If it is the former, I would be fully confident that you guys can solve it.

If it is the latter, then you could always provide a tick box which decides when there is only one button left whether the button text of the category text is displayed on the button. Default this to category text for all existing uses and everyone is happy.
Kirill Bondar  Staff  2/2/2017 10:01:47 AM
Role scenario is indeed an edge case and I'm not sure if I have seen it in action or these are my mind games. Just updated to display button/doc name instead of category name if there is only one in category.
Philipp Matuschka (MMB) 2/2/2017 10:20:28 AM
Tested. Excellent. Thank you
Back to Search Results