If the echo skill is running as a root bot, this trigger ends the dialog.If the echo skill is running as a skill, this trigger ends the dialog and returns control to the root bot.Select the Dialog management > End this dialog action. Set the bot response to: Thanks for using the echo skill To the new stop trigger, add a Send a response action to respond to the user's input. This trigger will fire for any message that contains the strings "stop", "cancel", or "quit" anywhere in the utterance. Name it stop and set its regEx pattern to stop|cancel|quit. To the EchoSkill dialog, add an Intent recognized trigger. Since the echo skill will now loop, you need to give the user a way to exit from the skill and return to the root bot.Ĭhange the Recognizer/Dispatch type to Regular expression, which can recognize intents without LUIS or the need for extra Azure resources. By default, Auto end dialog is true.Īdd a trigger to let the user exit the skill In the properties pane, change Auto end dialog to false to let the skill loop.In the properties pane, change the Responses under Bot Responses to: You said, $ On the authoring canvas, select the Send a response action. Select the EchoSkill dialog's Unknown intent trigger. Update the unknown intent trigger to echo the user's utterance. Update the skill's Unknown intent trigger This response is the first message the user will receive when another bot uses a "startSkill" event to start the skill. Set the response to: I will repeat what you enter, until you enter **stop**. On the authoring canvas, add a Send a response action to the trigger. In the properties pane, set the trigger's Condition property to: = "startSkill" Select Event received (Event activity) for the activity type.Select Activities for the type of trigger.You can define an event the root bot should initially send when it starts the skill.Įvery event activity should have a name property assigned.Īdd a "startSkill" event trigger to the skill to work as a greeting when the skill is invoked from a skill consumer.Īdd a new trigger to the EchoSkill dialog. Select the Send a response action and change the greeting to: Welcome to the **EchoBot**. Select the EchoSkill dialog's Greeting trigger. This greeting won't be triggered when the skill bot is invoked as a skill from another bot. The greeting is triggered when the skill bot is accessed directly by the user-when used as a root bot. In a later step, you'll add an Intent recognized trigger to allow the user to start the skill. Select the RootBot dialog and change the recognizer type it uses to the Regular expression recognizer, which can recognize intents without LUIS or the need for extra Azure resources. Give your bot a name and description-the bot used in this article is named RootBot-and select OK.Select Create from template, select the Echo Bot template, and select Next.In later steps, you'll change the recognizer type and add an Intent recognized trigger to allow the user to start the skill. Orchestrator, an intent recognizer, can recognize intents without LUIS or the need for extra Azure resources. The Get started panel contains links to more information about creating bots. Then select Create to have Composer create the bot.Give your bot a name-the bot used in this article is named RootBot.Select + Create new, select the C# tab, select the Empty Bot template, and select Next.In the Home view, create a new empty bot:
0 Comments
Leave a Reply. |