Working with the Dialog Node

Dialog Node lets you start a new dialog task within an existing dialog task if the user intent changes.

For example, let us consider a travel bot that has the following three dialog tasks: Flight Availability, Book a Flight, and Book a Hotel. You may want to invoke the Book a Flight dialog task from the Flight Availability dialog task.

Key Features

The key features of dialog nodes are listed below:

• The ability to carry data from the current dialog task to the target dialog task as entity pre-assignments described in the later section.
• When a target dialog task is invoked, the current dialog flow begins at the root intent of the new dialog task. If you write transitions for the dialog node, then the flow returns to the source dialog task after completing the target. If you do not write transitions, the dialog task ends after executing the target dialog task. This differs from an optional User Intent node, where the dialog flow processes a related user intent and then continues in the same dialog task thereafter.

Configuring a Dialog Node

Follow the below steps to set up a Dialog Node to invoke a new Dialog Task:

Add a Dialog Node to the Dialog Task

1. Open the Dialog Task in which you want to add the dialog node.
2. Click the icon next to the respective node.
3. Click Dialog Task and select the respective dialog task from the available list (you cannot create a new Dialog Task from within a Dialog like other nodes).
4. The Dialog window is displayed with the Component Properties tab selected by default.

Define Component, Transition & NLP Properties

1. On the Component Properties tab, under the General Settings, you can modify the Name and Description.
2. Click the Connections tab and set the transition properties to determine the node in the dialog task to execute next. You can write the conditional statements based on the values of any Entity or Context Objects in the dialog task, or you can use intents for transitions. If you have defined the Transition Property as End the current task, then these settings are ignored.
   1. Under the Connection Rules section, click Add IF.
   2. Configure the conditional expression based on one of the following criteria:
      • Entity: Compare an Entity node in the dialog with a specific value:
        • Select the Entity.
        • Select an operator from the drop-down lists: Exists, equals to, greater than equals to, less than equals to, not equal to, greater than, and less than.
        • Type the number in the Value field.  For example, PassengerCount (entity) greater than (operator) 5 (specified value).
      • Context: Compare a context object in the dialog with a specific value using one of these operators: Exists, equals to, greater than equals to, less than equals to, not equal to, greater than, and less than. For example, Context.entity.PassengerCount (Context object) greater than (operator) 5 (specified value).
      • Intent: Select an intent that matches the next user utterance.
   3. In the Then go to drop-down list, select the next node to execute in the dialog flow if the conditional expression succeeds. For example, if the PassengerCount (entity) greater than (operator) 5 (specified value), Then go to Offers (sub-dialog).
   4. In the Else drop-down list, select the node to execute if the condition fails.
      Note: If you want to write multiple If conditions, click Add Else If below the last If conditional expression.
3. From the NLP Properties tab, you can perform actions from the below-listed sections:
   • Machine Learning settings to provide user utterances to improve the detection for this node.
   • Bot Synonyms or related phrases for this node.
   • Patterns to capture this node if the user’s utterance contains these specific patterns.

Define Instance Properties

Instance Properties include the settings for this instance of the dialog.

1. Click the Instance Properties tab on the Dialog window.
2. Click Advanced Controls to set up the below-listed options:
   • Interruptions Behavior
     • Use the task level ‘Interruptions Behavior’ Setting: The bot refers to the Interruptions Behavior settings set at the dialog task level.
     • Customize for this node: You can customize the Interruptions Behavior settings for this node by selecting this option and configuring the same. Read the Interruption Handling and Context Switching article for more information.
   • Custom Tags defines tags to build custom profiles of your bot conversations. See here for more.

   

3. In the Entity Pre-Assignments section, you can pre-assign values from this session or node data to the entities required by the Dialog Task. Any remaining required values are handled by the sub-intent.  (see below for details)
4. In the Entity Post-Assignments section, it displays a list of entities available in the current task with an option to add custom variables. These entities are assigned with values from the linked dialogs session data. For example, context.entities.lists the entities from the linked sub-dialog for selection. The values are assigned once the linked dialog execution is complete.
   NOTE: This option is available only if the Transition Options is set to return to the current node on task completion. This feature was introduced in v7.1 of the platform.
   Currently, there is a limitation when using URL entity types. URL values with http as opposed to https or without www suffix will not work.
5. In the Transition Options section, you can define the flow to be followed once the task completes. You can choose from two options:
   • Return to the current node on task completion.
   • End the current task and initiate this task.

   

About Entity Pre-Assignments

You can pre-populate data for the destination dialog task by:

• Adding values to the entity keys.
• Adding additional custom keys and values to pass data from the current dialog task Context object to the destination dialog task as needed.

By default, entity nodes defined in the target dialog task are displayed as key/value pairs. You can then define values for associated entities or add custom keys and values as needed using session and context variables.

Transitioning from the source dialog task to the destination dialog task occurs at the runtime when the user input matches one of any linked dialog tasks. When you map more than one dialog task, you can define which dialog tasks are displayed to the end-users using conditional transitions.

When you call another dialog task, you want to carry information from the first dialog task to the next dialog task. For example, customer information collected in a Book a Flight dialog task is passed to the Book a Hotel dialog task.

In the Bots platform, you can use the mappedIntents variable in the Context object which holds the reference of the intent nodes as well as the context of the source dialog task as shown in the following JSON syntax:
{ 'title': 'title of the link', 'link':' url for the link' ,'postbackpayload': 'system generated payload'}
For example, a link to GetEmail in the Context object can be:

{
   "title":"GetEmail",
   "link":"https://app.collab.ai/wf/1.1/market/users/bots/st-bb1eb3da-cfa7-5244-b241-b5042d333e76/dialogue/dg-15fd2927-219c-5795-b038-5b830718bea7/execute?nodeId=message2&contextId=dcx-f9bae173-4d69-53e4-9aa7-21e89aae776d&intent=GetEmail",
   "postbackpayload":"MappedDialog_dc-f7b42932-dc06-53ac-92c0-1db706794f91_dg-15fd2927-219c-5795-b038-5b830718bea7_dcx-f9bae173-4d69-53e4-9aa7-21e89aae776d"
}

You can access and present these variables in a prompt message to a user to display a list of mapped dialog tasks with the link, or as a list of choices. You can pass the source dialog context to the target dialog task even if the source dialog task is no longer actively using the Context object.

The value for the postbackpayload key is generated by the Bots platform and is used in some channels, such as Facebook and Slack, which defines when a link or choice is made for a target dialog task.

For more information, refer to Using Session and Context Variables in Tasks and the Context Object.