Botframework-composer: Trigger names

Created on 28 Jan 2020  路  10Comments  路  Source: microsoft/BotFramework-Composer

Is your feature request related to a problem? Please describe.
Current naming of triggers is a bit confusing.

image

Describe the solution you'd like

Screen Shot 2020-01-21 at 4 09 28 PM

All 10 comments

Screen Shot 2020-02-03 at 6 30 46 PM
Updated design: https://www.figma.com/file/HLtKaKHctLldivPnzQ7BqQOI/Composer-MI---lotsotings?node-id=2108%3A13658

(also addresses other issues with usability/discoverability for Trigger types but I cannot find that).

Need more clarification and also need to address the RecognizerSet as well .

@mareekuh FYI. You might have already found this in the trigger menu:

I think the first trigger type in the Message events drop-down menu should be Message received. What is shown now is

Message events
-> Message events
-> Message deleted
-> Message reaction
-> Message updated

What it is supposed to be:

Message events
-> Message received
-> Message deleted
-> Message reaction
-> Message updated

Untitled

Thanks.

Yes : Message received vs Message Events
The dropdown should not have the word 'events' in it, per our discussion.
Trigger type: Language understanding/Dialog/Message/Other activities/Custom. Yes?

Hey @mareekuh
I agree that the word 'events' should be removed from some of the drop-down menus.
However, I also think it might be helpful to keep 'events' in the first-level menu. Thanks to @boydc2014 who explained "events" and "triggers" to me so that I have a better understanding of the two terms.

Here are my rough thoughts:

What initiates the trigger?
-> Recognizer events
-> Dialog events
-> Message activity events
-> Other activity events
-> Custom event

The major reason to include events in the first-level menu is that it might help users to understand that triggers are created to react to some type of events.

Thanks.

No I'd like to leave out the word event.
Select a trigger type:
Intent _(the 2nd field should show all existing intents and 'create new' at the top)_
Not recognized intent _(2nd field is empty)_
Dialog trigger
Message activity
Other activity
Custom trigger

https://www.figma.com/file/HLtKaKHctLldivPnzQ7BqQOI/Composer-MI-lotsotings?node-id=2663%3A15274

@mareekuh It looks good! Just one thing, can we add the word "trigger" to each of them? I feel it's more consistent. But this will bring another issue, some trigger names may be too long.

We can use 'trigger' in the first menu, but don't need it again in the 2nd.

Yes, I agree. No need to duplicate in the 2nd level menu.

Was this page helpful?
0 / 5 - 0 ratings