Custom Buttons - Expanded options

[AlexOnTheHill]

Currently, if I design a custom button it can perform one function only, if I want to add multiple buttons then the top bar where they appear starts to get cluttered quickly.

Would it be possible to have an enhancement to the custom buttons that allow them to be nested?

For example if I were to have a quick calls button I could have 5 options below that give the top 5 closure types, defining the closure category and resolution text at the same time.

We previously used SupportWorks which had a quick calls facility and a custom button with nested options would help replicate that.

I am aware of the option to display drop down if the custom buttons are more than x value, this is slightly different to that. 

Many thanks

[Steve Giller]

If you set the filters on the Button it will only appear for relevant Requests.
Frequently the clutter is from showing the buttons at all times, rather than only when they're relevant.

[AlexOnTheHill]

I do understand how to use filters, I have quite a number of them already in place to ensure the right teams get to see buttons or buttons only show under predefined circumstances (such as if a custom field is missing).

What I mean by this is just to have one button which can expand to have multiple options rather than use all the limited space with multiple buttons which are in effect doing one thing.

I would, for instance, have a Service Desk Quick Calls button that could have 'Password Reset', 'Unlocked Account', 'Set up MFA', 'Power Cycled Device', 'Reset MFA' and make that one button visible to the Service Desk.

We already use custom buttons for multiple purposes and I think this would help make much better use of the available space.

[AlexOnTheHill]

@Steve Giller does the above make sense?

Perhaps custom buttons are not the way to go with quick calls, perhaps they could be buttons added to the resolution action instead.

That said, I do think that having the ability to expand and collapse custom buttons would be useful.

[Steve Giller]

3 minutes ago, AlexOnTheHill said:

Perhaps custom buttons are not the way to go with quick calls

Probably not, that's not really what they're designed for.

You can fairly easily achieve what you're describing by having a single button which will check the Category and overwrite the Resolution Text based upon that (or vice versa - e.g. if you have Resolution Text Snippets to keep text consistent) then do whatever the individual Auto Tasks were doing.
You could also do this in the Request's Workflow, but I suspect that would involve editing a number of separate Workflows rather than creating a single Auto Task Workflow.