Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Working with the Builder
Building a Virtual Assistant
Using Workspaces
Release Notes
Current Version
Previous Versions

Dialog Tasks
Dialog Builder
Node Types
Intent Node
Dialog Node
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Group Node
Agent Transfer
User Prompts
Voice Call Properties
Dialog Task Management
Connections & Transitions
Component Transition
Context Object
Event Handlers
Knowledge Graph
Knowledge Extraction
Build Knowledge Graph
Add Knowledge Graph to Bot
Create the Graph
Build Knowledge Graph
Add FAQs
Run a Task
Build FAQs from an Existing Source
Traits, Synonyms, and Stop Words
Manage Variable Namespaces
Move Question and Answers Between Nodes
Edit and Delete Terms
Edit Questions and Responses
Knowledge Graph Training
Knowledge Graph Analysis
Knowledge Graph Import and Export
Importing Knowledge Graph
Exporting Knowledge Graph
Creating a Knowledge Graph
From a CSV File
From a JSON file
Auto-Generate Knowledge Graph
Alert Tasks
Small Talk
Digital Skills
Digital Forms
ML Engine
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
NLP Configurations
NLP Guidelines
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Sentinment Management
Tone Analysis
Test & Debug
Talk to Bot
Utterence Testing
Batch Testing
Conversation Testing
Conversations Dashboard
Performance Dashboard
Custom Dashboards
Meta Tags
Dashboards and Widgets
Conversation Flows
NLP Metrics
Containment Metrics
Usage Metrics
Smart Bots
Universal Bots
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Manage Assistant
Plan & Usage
Usage Plans
Support Plans
Multilingual Virtual Assistants
Masking PII Details
IVR Settings
General Settings
Assistant Management
Data Table
Table Views
App Definitions
Sharing Data Tables or Views

Build a Flight Status Assistant
Design Conversation Skills
Create a Sample Banking Assistant
Create a Transfer Funds Task
Create a Update Balance Task
Create a Knowledge Graph
Set Up a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Add Data to Data Tables
Update Data in Data Tables
Add Data from Digital Forms
Train the Assistant
Use Traits
Use Patterns for Intents & Entities
Manage Context Switching
Deploy the Assistant
Configure an Agent Transfer
Use Assistant Functions
Use Content Variables
Use Global Variables
Web SDK Tutorial
Widget SDK Tutorial
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters

API Reference
API Introduction
API List
API Collection
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Using the BotKit SDK

Assistant Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Assistant Management
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Compliance
Using Single-Sign On
Security Settings
Cloud Connector
  1. Home
  2. Docs
  3. Virtual Assistants
  4. How Tos
  5. Adding Data into Data Tables from UI Forms

Adding Data into Data Tables from UI Forms

In this How-To, we will explore a scenario in a Banking Bot, where the user can create an additional account.

We will see how data collected from the UI Forms can be used to create the account in a Data Table.

For details on what UI Forms are and how it is implemented in the Bots platform, refer here.
For details on what Data Tables are and how it is implemented in the Bots platform, refer here.

Problem Statement

Consider a Banking Bot trying to address the following scenarios:

  1. An already registered user wants to open an additional account.
  2. There are three types of accounts that are available, each with further options:
    • Savings Account;
    • Checking Account with an option to opt for a Cash Card and set a Minumum Balance;
    • Credit Card with an option to choose the type of card to be Platinum, Gold, Silver or Basic
  3. The above data is collected from the user using a UI form.
  4. This data needs to be updated to the data table.


  • Bot building knowledge
  • A Banking Bot with access to
    • Customer details table as created here
    • Account details table, using the same steps shown in the above link create the following data table:
      1. Name, say accountdetails;
      2. Description, say Account details Table;
      3. Under the Column section add the following details:
        Column Name Type Required Additional Settings
        AccountId number Yes Encrypted & Max Length of 5
        AccountName string Yes
        AccountType string No
        CustId number Yes Reference table & column as
        CashCard string No
        WithdrawalLimit number No
        CCType string No

    • UI Form, we will be using the UI Form configured as shown here.


Let us consider each of the following scenarios one by one:

  1. Dialog Task to:
    1. capture the customer id;
    2. trigger the UI Form to gather account details; and
    3. invoke the service node to add the account data.

Dialog Task Configuration

We will be creating a dialog task and adding a form node to trigger the UI Form created in the above step and use a service node to make a service call to add the new account from the form data.

Create Dialog Task

  1. From the left navigation menu, select Bot Tasks -> Dialog Tasks.
  2. Click the + against the Dialog Tasks to create a new Task
    • Enter IntentName, say, AddAccount
    • Create & Proceed to open the dialog builder page.
  3. Retain the Intent Node default settings, and close the Intent Node.
  4. Click the + next to the intent node and select the Entity node. This will be used to capture the customer id
    1. Enter Name, say, CustId
    2. Select Type, as Number
    3. User Prompt, as Enter your Customer Id
    4. Close the entity node.
  5. Add a Service node to check for the validity of the customer id entered.
  6. Add a Logic node to proceed with the Form if the customer id is valid else prompt for the customer id.
  7. The InvalidCustId is a Message node with the following JavaScript:
    context.entities.CustId = null;
    print('You have entered an invalid customer id, try again');
  8. Next, add a Form node and from the dropdown list select the form (OpenAccount).
    • You will be prompted to select the Form Experience. Bots platform allows you to gather user input both from the form and through conversation based on the channel.
    • For this use case, let us select Only Form UI experience.
    • A Form Node would be added, you can customize the form name, etc.
    • We are changing the Name to OpenAccountForm and Display Name to Form to open account.
  9. Using a Service node, fetch any existing account details for the customer id.
  10. Next, we will see how to capture the values returned by the Form Node using a Script node and process the same to get the next account id value and set to null the unwanted fields.
    • Use the following script:
      //get the next account id
      var resultSet = context.GetAcctData.response.body.queryResult;
      var id = 0;
      if (!resultSet.length) {
      } else {
          for (var i=0; i<resultSet.length; i++) {
              if (id < resultSet[i].AccountId) {
                  id = resultSet[i].AccountId;
      context.accountid = id;[0].CustName;
      //set unwanted fields to null
      if (context.forms.OpenAccount.accounttype == 'Savings')
      	{ context.cashcard = null;
      	  context.withdrawallimit = null;
      	  context.cardtype = null;
      if (context.forms.OpenAccount.accounttype == 'Checkings')
      	{ context.cardtype = null;
            context.cashcard = context.forms.OpenAccount.cashcard;
      	  context.withdrawallimit = context.forms.OpenAccount.withdrawallimit;
      if (context.forms.OpenAccount.accounttype == 'Credit Card')
      	{ context.cashcard = null;
      	  context.withdrawallimit = null;
      	  context.cardtype = context.forms.OpenAccount.cardtype;
  11. Use a Service node to add the account details using the context variables populated in the previous Script node.
  12. Your dialog with form and service nodes to update the data table is ready.
  13. Talk to bot and follow the steps to add an account to a given customer id.


In this post, we have seen:

  • How to fetch data from data tables;
  • How to trigger the From from a Dialog;
  • How to add the data captured from the form to a data table.