3.1.5 Default Nodes in Experience Designer
- Lydia Hou (Deactivated)
- Rajkiran Alla (Deactivated)
Login to the Experience Manager
Create a new project. Refer 3.1.1 Projects | Create a new project
Select Experience Designer from the Project side navigation menu.
To familiarize yourself with the Orbita Voice Experience Designer, we provided you with default flows (also referred to as tabs) in the Experience Designer.
Start here
This tab contains the Project Reference node and the Comment node. Double click on the Getting Started Comment node to read the onboarding instructions.
Project Reference node
The Project Reference node is placed on the canvas by default when you create a new tab. This node anchors your flow to the project.
Do not delete this node.
Comment node
The comment node is used for display purposes only.
The Title changes the display name of the node and you can put any text in the Body section.
Base
The Base tab contains the most used intents and respective bot says to those intents, while using a voice assistant.
Intent node
The Intent node lets you choose intents created in the Experience Manager. Refer How do I create an intent?
When a chatbot user says an utterance that corresponds to the intent on the Experience Designer canvas, the intent will get triggered to initiate the flow.
Say node
The chatbot will respond to the chatbot user with the content present in the Say node.
You can connect multiple intents to one Say node.
For example, in the below screenshot, the NoIntent and the StopIntent intent nodes are connected to the Say node that says Good bye.
Response node
The Response node connects the entire flow to the chatbot. The Response node denotes the end of the execution.
None Intent Request node
None intent gets triggered when the intent is present in the Interaction model but not used on the Experience Designer canvas.
The Interaction model is the collection of intents, slots, and synonyms that are created in the Experience Designer and deployed to Google or Alexa. The Interaction model is project-specific and you can view the Interaction model of a project at Project side navigation menu > Develop > Deployment > Alexa tab. The interaction model is the same for Alexa and Google deployment.
Refer, How to Publish the interaction model to Dialogflow?
Session End Request node
The Session End Request node ends the execution of a Skill. This happens for one of 3 reasons:
The user says exit.
The user does not respond.
An error occurs.
Debug node
The Debug node is used to capture the payload at any point in the Experience Designer flows. This node is used for debugging purposes.
Intent Debug node
The Intent Debug node is available for debugging purposes and it listens to any intent activity within the project.
If you have multiple intents on the canvas, instead of adding multiple debug nodes to all the intent nodes, you can use this node and add a debug node to capture if any of the intents in the project got triggered.
Launch
The Launch flow contains the Launch node and an Intent node (Hello World). These nodes are connected to their respective say nodes and finally to the response node.
Launch node
The Launch node receives the request to start the application from Echo Google home, Mobile Chat, or a web chatbot. It does not provide any command mapping to an intent.
Loading a chatbot in the webpage will trigger the Launch node in the Experience Designer.
Bot Manager
The Request/Response from/to the chatbot is managed by the Bot manager flow.
You can learn more here, How do I configure Chatbot | Chatbot Endpoint setup
Access the Chatbot
Select the Get http in node. (connected to the Bot view template node)
Click on the button to open the chatbot in a new tab.
Chatbot Settings
You can override the chatbot settings using the App Settings function node in the Bot manager flow.
You can change the chatbot settings at Experience Manager > Project side navigation menu > Develop > Chatbot Settings > settings tab
Refer, Chatbot Settings for more information.
Default Intent nodes
The help, cancel, and stop intent nodes are available on the Experience Designer canvas by default with their respective say nodes. When the help, cancel, or stop are used in the Flow studio (Single input, Choose one, Choose many controls) and when there is no other intent node with the flow studio state (or any other state) that captures these default intents' utterances, the default intent nodes will get triggered and the corresponding say node response will be given to the chatbot user. This will break the flow as these say nodes have no state.
If you want to use these default intents utterances within flow studio and do not want to break the flow, then connect these default intent nodes with appropriate state mentioned and connect to flow manager node.
Supporting Documentation
No additional supporting documentation
Useful Links
Related Content