This trigger is the component of the AtBot Logic Flow connector that defines when this Flow should be used from your bot. The skills in AtBot start from this trigger. A pre-configured Intent Vector, created in AtBot Admin, will be associated with this trigger. The selected Intent Vector determines the output parameters produced by the trigger for use in the Flow.
The trigger description is used in the AtBot Admin Portal to help identify the skill as well as in the autogenerated help card that comes back from AtBot
Bot Trigger Type
The bot trigger type defines whether this skill can be run by anyone in the organization (Shared) or just you (Personal)
LUIS Intent Vector
The LUIS Intent Vector to associate with this bot skill. This translates to the LUIS App/Intent combination configured in the Intent Vector and the configured Entities which become the output parameters of the trigger in the Flow.
When this is set to Yes, users may branch out to other skills or QnA Maker while the answering follow-up questions from the Intent Vector.
This is the raw text that the user sent to trigger this skill
This is a special scope property that must be used in any subsequent actions to maintain the bot conversation
This is the Login Name (UPN) of the user who triggered the skill
LUIS Intent Vector Fields
The trigger will dynamically define return data based on the selected LUIS Intent Vector. The schema of what is returned is based on the Entities defined in the LUIS Intent Vector in AtBot Admin.
Bot Scope Scope
The name of the scope the bot is coming from. This can only be set in DirectLine bot embed code.
Bot Scope Type
The type defined in the scope the bot is coming from. This can only be set in DirectLine bot embed code.
Bot Scope Uri
The URI defined in the scope the bot is coming from. This can only be set in DirectLine bot embed code.
Branch Signal Type
Contains the type of skill the user was in (Date, Person, Choice) when they branched to this skill.