Form Node

Form node lets you integrate the Digital Forms with Dialog Task. This facilitates the presentation of form to capture user inputs for specific use cases.

The primary purpose of the Form node is to represent a UI Form in the dialog task and make the form available for end-users on their channel. For example, let us consider a banking bot that has a form to capture the customer details to open a new account. You want to use the form instead of prompting for each and every entity value.

Set-Up

Setting up a form node in a dialog task involves the following steps:

Add Node

To add a form node to the dialog task, follow the below steps:

1. Open the dialog task to add the Form node.
2. Add form node in the designated place. For steps in adding nodes, refer here.
3. The Form Node window is displayed with the Component Properties tab selected by default.

Configure Node

Component Properties

The Form Component Properties allow you to configure the General Settings, User, and Error Prompts.

1. On the Component Properties tab, under the General Settings section, enter a Name and Display Name for the form node. Node names cannot have spaces. The UI Form property is set to the UI Form you selected and it cannot be changed.
2. In the Prompt Message text box, enter the prompt message that you want the user to see for this form. It gives instructions to the user to click on the link to initiate the form. It is not recommended to change the context variable reference (of the form {{context.form_node.formLink}})coded therein. You can enter channel-specific messages for user prompts. For more information, refer to Using the Prompt Editor.
3. In the Error Message text box, review the default error message, and if required modify it. For more information, refer to Using the Prompt Editor.
4. In the Submit Message text box, review the default message that is displayed after successful submission of the form, and if required, modify it. This message is applicable only when the UI Form is opened in a browser tab and not for Web/Mobile SDK. For more information, refer to Using the Prompt Editor.
5. Under the Web/Mobile SDK Form Behavior section, you can set how the form is displayed. You can select:
   • Open full page popup form – This is the default setting where the form opens as a full page on the SDK chat interface.
   • Open inline form – The form opens as an inline form within the chat window.
6. In the Variable Namespaces section, associate the variable namespaces used to execute this node and its transitions. This option is visible only when the variable namespace is enabled for the bot. You can go with the task level settings or customize it for this node. For more information, refer to Managing Namespace.

Instance Properties

Use the Instance Properties to define any user tags that you want to set.

1. On the Form window, click the Instance Properties tab.
2. Under the Custom Tags section, add tags to build custom profiles of your bot conversations. Click here for more

Connections Properties

From the node’s Connections tab, you can 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.
To setup Component Transitions, follow the below steps:

1. On the Form window, click the Connections tab.
2. Under the Connection Rules section, you can select a node from the Default drop-down list.
3. To configure a conditional flow, click Add IF.
4. Configure the conditional expression based on one of the following criteria:
   • Entity: Compare an entity node 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. Select the entity, operator using the respective drop-down lists, and type the number in the Value box. 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.
5. From 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).
6. In the Else drop-down list, select the node to execute if the condition fails.
7. Click Save.