GETTING STARTED
Kore.ai XO Platform
Virtual Assistants Overview
Natural Language Processing (NLP)
Concepts and Terminology
Quick Start Guide
Accessing the Platform
Navigating the Kore.ai XO Platform
Building a Virtual Assistant
Help & Learning Resources
Release Notes
Current Version
Recent Updates
Previous Versions
Deprecations
Request a Feature
CONCEPTS
Design
Storyboard
Overview
FAQs
Conversation Designer
Overview
Dialog Tasks
Mock Scenes
Dialog Tasks
Overview
Navigate Dialog Tasks
Build Dialog Tasks
Node Types
Overview
Intent Node
Dialog Node
Dynamic Intent Node
GenAI Node
GenAI Prompt
Entity Node
Form Node
Confirmation Node
Message Nodes
Logic Node
Bot Action Node
Service Node
Webhook Node
Script Node
Process Node
Agent Transfer
Node Connections
Node Connections Setup
Sub-Intent Scoping
Entity Types
Entity Rules
User Prompts or Messages
Voice Call Properties
Knowledge AI
Introduction
Knowledge Graph
Introduction
Terminology
Build a Knowledge Graph
Manage FAQs
Knowledge Extraction
Import or Export Knowledge Graph
Prepare Data for Import
Importing Knowledge Graph
Exporting Knowledge Graph
Auto-Generate Knowledge Graph
Knowledge Graph Analysis
Answer from Documents
Alert Tasks
Small Talk
Digital Skills
Overview
Digital Forms
Digital Views
Introduction
Widgets
Panels
Session and Context Variables
Context Object
Intent Discovery
Train
NLP Optimization
ML Engine
Overview
Model Validation
FM Engine
KG Engine
Traits Engine
Ranking and Resolver
Training Validations
NLP Configurations
NLP Guidelines
LLM and Generative AI
Introduction
LLM Integration
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Kore.ai XO GPT Model
Intelligence
Introduction
Event Handlers
Contextual Memory
Contextual Intents
Interruption Management
Multi-intent Detection
Amending Entities
Default Conversations
Conversation Driven Dialog Builder
Sentinment Management
Tone Analysis
Default Standard Responses
Ignore Words & Field Memory
Test & Debug
Overview
Talk to Bot
Utterance Testing
Batch Testing
Conversation Testing
Conversation Testing Overview
Create a Test Suite
Test Editor
Test Case Assertion
Test Case Execution Summary
Glossary
Health and Monitoring
NLP Health
Flow Health
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
Deploy
Channels
Publishing
Versioning
Analyze
Introduction
Dashboard Filters
Overview Dashboard
Conversations Dashboard
Users Dashboard
Performance Dashboard
Custom Dashboards
Introduction
Custom Meta Tags
Create Custom Dashboard
Create Custom Dashboard Filters
NLP Insights
Task Execution Logs
Conversations History
Conversation Flows
Conversation Insights
Feedback Analytics
Usage Metrics
Containment Metrics
Universal Bots
Introduction
Universal Bot Definition
Universal Bot Creation
Training a Universal Bot
Universal Bot Customizations
Enabling Languages
Store
Manage Assistant
Team Collaboration
Plan & Usage
Overview
Usage Plans
Templates
Support Plans
Invoices
Authorization
Conversation Sessions
Multilingual Virtual Assistants
Get Started
Supported Components & Features
Manage Languages
Manage Translation Services
Multiingual Virtual Assistant Behavior
Feedback Survey
Masking PII Details
Variables
Collections
IVR Settings
General Settings
Assistant Management
Manage Namespace
Data
Overview
Data Table
Table Views
App Definitions
Data as Service
HOW TOs
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking 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
Composite Entities
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
Intent Scoping using Group Node
Analyze the Assistant
Create a Custom Dashboard
Use Custom Meta Tags in Filters
Migrate External Bots
Google Dialogflow Bot
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
SDK Security
SDK Registration
Web Socket Connect and RTM
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
SDK Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
Widget SDK Tutorial
Web SDK Tutorial
ADMINISTRATION
Introduction to Admin Console
Administration Dashboard
User Management
Add Users
Manage Groups
Manage Roles
Data Tables and Views
Assistant Management
Enrollment
Invite Users
Send Bulk Invites
Import User Data
Synchronize Users from AD
Security & Control
Using Single-Sign On (SSO)
Two-Factor Authentication (2FA)
Security Settings
Cloud Connector
Analytics
Billing
  1. Home
  2. Docs
  3. Virtual Assistants
  4. How Tos
  5. Updating Data in Data Tables

Updating Data in Data Tables

In this How-To, we will explore a scenario in a Banking Bot, where the account-related data for a customer is stored in a Data Table. We will see how the data can be updated by a request from the user.

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

Problem Statement

Consider a Banking Bot, for a given customer, the following data is stored. This data needs to be updated as per customer request. Customers can update only email id and address details.

  1. Id;
  2. Name;
  3. Email id;
  4. Address; and
  5. Type

Pre-requisites

  • Bot building knowledge;
  • A Banking Bot with access to the above-mentioned table, and data existing in that table (refer here for use case example to create and add data).

Configurations

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

  1. Dialog Task to:
    1. gather required information; and
    2. invoke a service to update the customer information.

Dialog Task Configuration

We will be creating a dialog task to gather the required information, and use a Service node to update the data table with the values thus gathered.

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, UpdateCustomer
    • 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 add an Entities to capture the customer id:
    Entity Name Type User Prompts
    CustId String Enter your customer id
  5. First, we will fetch data from the table for the given Cust Id and then use a Logic node to control the process flow.

Fetch Data

You can use a Service call to fetch data from the table:

  1. Click the + against the entity node.
  2. Select Service -> New Service Node option.
  3. From the General Settings section configure the following:
    • Name say GetCustomerData
    • Display Name say Get Customer Data
    • Service Type select Data Service
    • Type select Table
  4. Under Request Definition click Add Request to define a request to fetch data from the table.
  5. In the Data Service Request Definition page, enter the following:
    • Choose Table Name as customertable
    • Actions as Get Data
    • Choose Filters to select the CustId = {{context.entities.CustId}}

  6. Save the definition and close the service node.
  7. Add a Message Node to display the records fetches using the following context variable values, since we are fetching only one record, we are using a static [0] reference to the row:
    'For the customer number entered, we have the following details: {{context.GetCustomerData.response.body.queryResult[0].CustName}}, {{context.GetCustomerData.response.body.queryResult[0].CustEmail}}, {{context.GetCustomerData.response.body.queryResult[0].Address}}, {{context.GetCustomerData.response.body.queryResult[0].CustType}}'

Update Data

We will be using an entity node and a logic node to capture the inputs from the customer and to control the process flow:

  1. Click the + against the last message node added above.
  2. Select an Entity Node and add a List of Items (enumerated) type entity with the following settings.
    Display Name Value
    Email Id Email Id
    Address Address
  3. Add a Logic Node and based upon the value from the entity node above fetch either Email ID or Address from the customer, here CustEmail and CustAddress are the entities to capture customer email id and customer address.
  4. Also populate the context variables with the current details, these variables would be used to update the data table.
  5. From the Email Id and Address entity trigger a Script Node to modify the context variables appropriately using the following script:
    if (context.entities.CustUpdateChoice == 'Address') {
        context.custAdd = context.entities.CustAddress;
      }
    else {
       context.custEmail = context.entities.CustEmail;
     }
  6. Select Service -> New Service Node option.
  7. From the General Settings section configure the following:
    • Name say UpdateCust
    • Display Name say Update Customer Data
    • Service Type select Data Service
    • Type select Table
  8. Under Request Definition click Add Request to define a request to add data to the table.
  9. In the Data Service Request Definition page, enter the following:
    • Choose Table Name as customertable defined earlier
    • Actions as Update Data
    • Assign Values from the entities defined as follows, remember you need to include all the fields and their values, else the field would be set to null value:
      Column Entity context
      CustName {{context.CustName}}
      CustEmail {{context.CustEmail}}
      Address {{context.CustAddress}}
      CustType {{context.CustType}}
      CustId {{context.CustId}}

  10. Add a Message node to display the success message.
  11. Using Talk to bot option, enter the values when prompted and see the message being displayed.

Conclusion

In this post, we have seen:

  • How to fetch the data from the table using a service node and use it for further processing;
  • How to update data to the table from the Dialog task using a service node;

Updating Data in Data Tables

In this How-To, we will explore a scenario in a Banking Bot, where the account-related data for a customer is stored in a Data Table. We will see how the data can be updated by a request from the user.

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

Problem Statement

Consider a Banking Bot, for a given customer, the following data is stored. This data needs to be updated as per customer request. Customers can update only email id and address details.

  1. Id;
  2. Name;
  3. Email id;
  4. Address; and
  5. Type

Pre-requisites

  • Bot building knowledge;
  • A Banking Bot with access to the above-mentioned table, and data existing in that table (refer here for use case example to create and add data).

Configurations

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

  1. Dialog Task to:
    1. gather required information; and
    2. invoke a service to update the customer information.

Dialog Task Configuration

We will be creating a dialog task to gather the required information, and use a Service node to update the data table with the values thus gathered.

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, UpdateCustomer
    • 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 add an Entities to capture the customer id:
    Entity Name Type User Prompts
    CustId String Enter your customer id
  5. First, we will fetch data from the table for the given Cust Id and then use a Logic node to control the process flow.

Fetch Data

You can use a Service call to fetch data from the table:

  1. Click the + against the entity node.
  2. Select Service -> New Service Node option.
  3. From the General Settings section configure the following:
    • Name say GetCustomerData
    • Display Name say Get Customer Data
    • Service Type select Data Service
    • Type select Table
  4. Under Request Definition click Add Request to define a request to fetch data from the table.
  5. In the Data Service Request Definition page, enter the following:
    • Choose Table Name as customertable
    • Actions as Get Data
    • Choose Filters to select the CustId = {{context.entities.CustId}}

  6. Save the definition and close the service node.
  7. Add a Message Node to display the records fetches using the following context variable values, since we are fetching only one record, we are using a static [0] reference to the row:
    'For the customer number entered, we have the following details: {{context.GetCustomerData.response.body.queryResult[0].CustName}}, {{context.GetCustomerData.response.body.queryResult[0].CustEmail}}, {{context.GetCustomerData.response.body.queryResult[0].Address}}, {{context.GetCustomerData.response.body.queryResult[0].CustType}}'

Update Data

We will be using an entity node and a logic node to capture the inputs from the customer and to control the process flow:

  1. Click the + against the last message node added above.
  2. Select an Entity Node and add a List of Items (enumerated) type entity with the following settings.
    Display Name Value
    Email Id Email Id
    Address Address
  3. Add a Logic Node and based upon the value from the entity node above fetch either Email ID or Address from the customer, here CustEmail and CustAddress are the entities to capture customer email id and customer address.
  4. Also populate the context variables with the current details, these variables would be used to update the data table.
  5. From the Email Id and Address entity trigger a Script Node to modify the context variables appropriately using the following script:
    if (context.entities.CustUpdateChoice == 'Address') {
        context.custAdd = context.entities.CustAddress;
      }
    else {
       context.custEmail = context.entities.CustEmail;
     }
  6. Select Service -> New Service Node option.
  7. From the General Settings section configure the following:
    • Name say UpdateCust
    • Display Name say Update Customer Data
    • Service Type select Data Service
    • Type select Table
  8. Under Request Definition click Add Request to define a request to add data to the table.
  9. In the Data Service Request Definition page, enter the following:
    • Choose Table Name as customertable defined earlier
    • Actions as Update Data
    • Assign Values from the entities defined as follows, remember you need to include all the fields and their values, else the field would be set to null value:
      Column Entity context
      CustName {{context.CustName}}
      CustEmail {{context.CustEmail}}
      Address {{context.CustAddress}}
      CustType {{context.CustType}}
      CustId {{context.CustId}}

  10. Add a Message node to display the success message.
  11. Using Talk to bot option, enter the values when prompted and see the message being displayed.

Conclusion

In this post, we have seen:

  • How to fetch the data from the table using a service node and use it for further processing;
  • How to update data to the table from the Dialog task using a service node;
Menu