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
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
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
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
LLM and Generative AI Logs
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
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer
  1. Home
  2. Docs
  3. Virtual Assistants
  4. Advanced Topics
  5. Data Table

Data Table

You can create a data table and share it with virtual assistants, apps and process assistants.

Step to create a new table:

  1. Go to the Data tab in the Home page and select the Data Tables option and click Create Data Table.
  2. Alternatively, click New Table to create a new data table..
  3. In the New Table page, enter the following details:
    • Name of the Data Table.
    • Description of the Data Table.
    • Columns to be included in the Table.
    • Indexes for the Table.
    • Bot Assignments to let virtual assistants access data in this table.
    • App Assignments to let apps access data in this table.
    • Process Assignments to let a process app access data in this table.

  4. Click Create.

Columns

The second step in defining a Data Table is to add columns required in the table.

  • Name of the column (see here for reserve words which cannot be used as the name of a column);
  • Type of the data that can be stored in this column. It can be:
    • string;
    • date; or
    • number.
  • Required flag to mark the column as mandatory.
  • Encrypted flag to secure the data in this column.
  • Reference Column to create a dependency with a column from another table i.e. to add a foreign key constraint. This would ensure that the value entered for this column exists in the referenced table column.
  • Max Length to limit the maximum length for the column values.
  • Default Values to be taken in case the value is missing while adding a row.

By default, the platform defines the following columns:

  • sys_Id: A platform generated unique identifier for each row in the table.
  • Created_On: Timestamp when this table was created.
  • Updated_On: Timestamp when this table was updated.
  • Created_By: User id of the developer who created this table.
  • Updated_By: User id of the developer who last updated this table.

Index

For an improved performance during Data search and retrieval, you can define Indices for your Data Table.

This includes:

  • Index Name for reference.
  • Is Unique flag to define if the index is expected to contain unique values.
  • Column & Sort Order – List of columns to be included in the index; you can select multiple columns and specify the sort order (ascending or descending) for each of the selected columns.

Assignments

You can define the assignments for each of the data tables as follows:

  • Assign bots:
    • Assign bots with Read, Write, and Delete permissions. You can select the bots from the list presented, these will be the list of bots owned by you and shared with you.
    • Only the assigned bots will be allowed to access the data from the data table using the Service Nodes in the Dialog Tasks of that bot.
  • Assign apps:
    • Assign apps with Read, Write, and Delete permissions.
    • You can select from the list or create a new app.
    • The data table CRUD APIs will be restricted to access only the tables that are assigned to the app.
  • Assign process apps:
    • Assign process apps with Read, Write, and Delete permissions. You can select the process apps from the list presented, these will be the list of process apps owned by you and shared with you.

Import & Export

You can export and import Data Table definitions as JSON format files.

Export a Data Table

Steps:

  1. Hover over the table definition that you want to Export
  2. Click the more (ellipses) icon and select Export Definition
  3. A JSON file is generated and downloaded.

Import a Data Table

Steps:

  1. Click the down arrow next to the New Table button.
  2. Select the Import Table Definition option.
  3. Enter a Table Name and select the JSON file containing the table definition.
  4. Click Import.

Sample Data Definition in the JSON file

{"name":"customertable",
 "description":"Table containing customer details",
 "indexes":[],
 "schemaDef":[{"name":"CustEmail",
               "type":"string",
               "isRequired":false,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":""},
	      {"name":"CustType",
               "type":"string",
               "isRequired":false,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":"Preferred"},
	      {"name":"Address",
               "type":"string",
               "isRequired":false,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":""},
	      {"name":"CustName",
               "type":"string",
               "isRequired":true,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":""},
	      {"name":"CustId",
               "type":"number",
               "isRequired":true,
               "isEncrypted":true,
               "reference":{},
               "maxLength":"5",
               "default":""},
	      {"name":"sys_Id","type":"string","isRequired":true,"readOnly":true},
	      {"name":"Created_On","type":"date","isRequired":true,"readOnly":true},
	      {"name":"Updated_On","type":"date","isRequired":true,"readOnly":true},
	      {"name":"Created_By","type":"string","isRequired":true,"readOnly":true},
	      {"name":"Updated_By","type":"string","isRequired":true,"readOnly":true}]}

Change Table Owner

The table owner can transfer the ownership to another user to let them manage the table’s definition and app assignments. An account administrator can also change the table owner.

Steps to change the table owner:

  1. Hover over the data table for which you want to change owner.
  2. Click the more (ellipses) icon and select Change Owner option.
  3. In the Change Table Owner dialog, select the new owner from the list and click Proceed.
  4. Review the related tables associated with this table which may have changes in ownership.
  5. Once the ownership changes, a successful completion message will appear.
  6. Once the Ownership is changed, all related tables and views ownership is also transferred to the new owner. The table is moved to the new owner, and all the app assignments of these tables are lost.
    The Related tables and views refer to any associated table or view to a particular table based on the foreign key relations or view definitions. Following are the examples:

    • View 1 is based on Table A and Table B.
    • View 2 is based on Table A and Table C.
    • View 3 is based on Table D.
    • Table E is not used in any View.
    • Table F column is referenced to a column in Table A.

    Scenario 1: Change Owner action on Table A indicates that the ownership of Table B, Table C, Table F, View 1, and View 2 is transferred.

    Scenario 2: Change Owner action on Table F indicates that the ownership of Table A, Table B, Table C, View 1, and View 2 is transferred.

Share Data Tables

The Kore.ai XO Platform allows you to share Data Tables by assigning them to bots, process apps, or apps.

Note: In the Shared Tables tab, you can view only the tables shared with a user who has permission to view. When you share the data tables with users, they cannot edit or update the table or view definitions.

The bot or process developers can see the data table definitions using a Service node.

  • From the Data Service Request Definition, users can select the Get Data action and click Test to view metadata. For more information, read the Get Data section in Data as a Service post.
  • Users can also see all column names while configuring Add Data or Update Data actions. For more information, read the Add Data section in the Data as a Service post.

Reserve Words

Following is the list of words that are reserved and cannot be used as the names for a column:

  • ACCESS
  • ADD
  • ALL
  • ALTER
  • AND
  • ANY
  • AS
  • ASC
  • AUDIT
  • BETWEEN
  • BY
  • CHAR\
  • CHECK
  • CLUSTER
  • COLUMN
  • COMMENT
  • COMPRESS
  • CONNECT
  • CREATE
  • CURRENT
  • DATE
  • DECIMAL
  • DEFAULT
  • DELETE
  • DESC
  • DISTINCT
  • DROP
  • ELSE
  • EXCLUSIVE
  • EXISTS
  • FILE
  • FLOAT
  • FOR
  • FROM
  • GRANT
  • GROUP
  • HAVING
  • IDENTIFIED
  • IMMEDIATE
  • IN
  • INCREMENT
  • INDEX
  • INITIAL
  • INSERT
  • INTEGER
  • INTERSECT
  • INTO
  • IS
  • LEVEL
  • LIKE
  • LOCK
  • LONG
  • MAXEXTENTS
  • MINUS
  • MLSLABEL
  • MODE
  • MODIFY
  • NOAUDIT
  • NOCOMPRESS
  • NOT
  • NOWAIT
  • NULL
  • NUMBER
  • OF
  • ONLINE
  • ON
  • OFFLINE
  • OPTION
  • ON
  • ORDER
  • PCTFREE
  • PRIOR
  • PRIVILEGES
  • PUBLIC
  • RAW
  • RENAME
  • RESOURCE
  • REVOKE
  • ROW
  • ROWID
  • RONUM
  • ROWS
  • SELECT
  • SESSION
  • SET
  • SHARE
  • SIZE
  • SMALLINT
  • START
  • SUCCESSFUL
  • SYNONYM
  • SYSDATE
  • TABLE
  • THEN
  • TO
  • TRIGGER
  • UID
  • UNION
  • UNIQUE
  • UPDATE
  • USER
  • VALIDATE
  • VALUES
  • VARCHAR
  • VARCHAR2
  • VIEW
  • WHENEVER
  • WHERE
  • WITH

Data Table

You can create a data table and share it with virtual assistants, apps and process assistants.

Step to create a new table:

  1. Go to the Data tab in the Home page and select the Data Tables option and click Create Data Table.
  2. Alternatively, click New Table to create a new data table..
  3. In the New Table page, enter the following details:
    • Name of the Data Table.
    • Description of the Data Table.
    • Columns to be included in the Table.
    • Indexes for the Table.
    • Bot Assignments to let virtual assistants access data in this table.
    • App Assignments to let apps access data in this table.
    • Process Assignments to let a process app access data in this table.

  4. Click Create.

Columns

The second step in defining a Data Table is to add columns required in the table.

  • Name of the column (see here for reserve words which cannot be used as the name of a column);
  • Type of the data that can be stored in this column. It can be:
    • string;
    • date; or
    • number.
  • Required flag to mark the column as mandatory.
  • Encrypted flag to secure the data in this column.
  • Reference Column to create a dependency with a column from another table i.e. to add a foreign key constraint. This would ensure that the value entered for this column exists in the referenced table column.
  • Max Length to limit the maximum length for the column values.
  • Default Values to be taken in case the value is missing while adding a row.

By default, the platform defines the following columns:

  • sys_Id: A platform generated unique identifier for each row in the table.
  • Created_On: Timestamp when this table was created.
  • Updated_On: Timestamp when this table was updated.
  • Created_By: User id of the developer who created this table.
  • Updated_By: User id of the developer who last updated this table.

Index

For an improved performance during Data search and retrieval, you can define Indices for your Data Table.

This includes:

  • Index Name for reference.
  • Is Unique flag to define if the index is expected to contain unique values.
  • Column & Sort Order – List of columns to be included in the index; you can select multiple columns and specify the sort order (ascending or descending) for each of the selected columns.

Assignments

You can define the assignments for each of the data tables as follows:

  • Assign bots:
    • Assign bots with Read, Write, and Delete permissions. You can select the bots from the list presented, these will be the list of bots owned by you and shared with you.
    • Only the assigned bots will be allowed to access the data from the data table using the Service Nodes in the Dialog Tasks of that bot.
  • Assign apps:
    • Assign apps with Read, Write, and Delete permissions.
    • You can select from the list or create a new app.
    • The data table CRUD APIs will be restricted to access only the tables that are assigned to the app.
  • Assign process apps:
    • Assign process apps with Read, Write, and Delete permissions. You can select the process apps from the list presented, these will be the list of process apps owned by you and shared with you.

Import & Export

You can export and import Data Table definitions as JSON format files.

Export a Data Table

Steps:

  1. Hover over the table definition that you want to Export
  2. Click the more (ellipses) icon and select Export Definition
  3. A JSON file is generated and downloaded.

Import a Data Table

Steps:

  1. Click the down arrow next to the New Table button.
  2. Select the Import Table Definition option.
  3. Enter a Table Name and select the JSON file containing the table definition.
  4. Click Import.

Sample Data Definition in the JSON file

{"name":"customertable",
 "description":"Table containing customer details",
 "indexes":[],
 "schemaDef":[{"name":"CustEmail",
               "type":"string",
               "isRequired":false,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":""},
	      {"name":"CustType",
               "type":"string",
               "isRequired":false,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":"Preferred"},
	      {"name":"Address",
               "type":"string",
               "isRequired":false,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":""},
	      {"name":"CustName",
               "type":"string",
               "isRequired":true,
               "isEncrypted":false,
               "reference":{},
               "maxLength":"",
               "default":""},
	      {"name":"CustId",
               "type":"number",
               "isRequired":true,
               "isEncrypted":true,
               "reference":{},
               "maxLength":"5",
               "default":""},
	      {"name":"sys_Id","type":"string","isRequired":true,"readOnly":true},
	      {"name":"Created_On","type":"date","isRequired":true,"readOnly":true},
	      {"name":"Updated_On","type":"date","isRequired":true,"readOnly":true},
	      {"name":"Created_By","type":"string","isRequired":true,"readOnly":true},
	      {"name":"Updated_By","type":"string","isRequired":true,"readOnly":true}]}

Change Table Owner

The table owner can transfer the ownership to another user to let them manage the table’s definition and app assignments. An account administrator can also change the table owner.

Steps to change the table owner:

  1. Hover over the data table for which you want to change owner.
  2. Click the more (ellipses) icon and select Change Owner option.
  3. In the Change Table Owner dialog, select the new owner from the list and click Proceed.
  4. Review the related tables associated with this table which may have changes in ownership.
  5. Once the ownership changes, a successful completion message will appear.
  6. Once the Ownership is changed, all related tables and views ownership is also transferred to the new owner. The table is moved to the new owner, and all the app assignments of these tables are lost.
    The Related tables and views refer to any associated table or view to a particular table based on the foreign key relations or view definitions. Following are the examples:

    • View 1 is based on Table A and Table B.
    • View 2 is based on Table A and Table C.
    • View 3 is based on Table D.
    • Table E is not used in any View.
    • Table F column is referenced to a column in Table A.

    Scenario 1: Change Owner action on Table A indicates that the ownership of Table B, Table C, Table F, View 1, and View 2 is transferred.

    Scenario 2: Change Owner action on Table F indicates that the ownership of Table A, Table B, Table C, View 1, and View 2 is transferred.

Share Data Tables

The Kore.ai XO Platform allows you to share Data Tables by assigning them to bots, process apps, or apps.

Note: In the Shared Tables tab, you can view only the tables shared with a user who has permission to view. When you share the data tables with users, they cannot edit or update the table or view definitions.

The bot or process developers can see the data table definitions using a Service node.

  • From the Data Service Request Definition, users can select the Get Data action and click Test to view metadata. For more information, read the Get Data section in Data as a Service post.
  • Users can also see all column names while configuring Add Data or Update Data actions. For more information, read the Add Data section in the Data as a Service post.

Reserve Words

Following is the list of words that are reserved and cannot be used as the names for a column:

  • ACCESS
  • ADD
  • ALL
  • ALTER
  • AND
  • ANY
  • AS
  • ASC
  • AUDIT
  • BETWEEN
  • BY
  • CHAR\
  • CHECK
  • CLUSTER
  • COLUMN
  • COMMENT
  • COMPRESS
  • CONNECT
  • CREATE
  • CURRENT
  • DATE
  • DECIMAL
  • DEFAULT
  • DELETE
  • DESC
  • DISTINCT
  • DROP
  • ELSE
  • EXCLUSIVE
  • EXISTS
  • FILE
  • FLOAT
  • FOR
  • FROM
  • GRANT
  • GROUP
  • HAVING
  • IDENTIFIED
  • IMMEDIATE
  • IN
  • INCREMENT
  • INDEX
  • INITIAL
  • INSERT
  • INTEGER
  • INTERSECT
  • INTO
  • IS
  • LEVEL
  • LIKE
  • LOCK
  • LONG
  • MAXEXTENTS
  • MINUS
  • MLSLABEL
  • MODE
  • MODIFY
  • NOAUDIT
  • NOCOMPRESS
  • NOT
  • NOWAIT
  • NULL
  • NUMBER
  • OF
  • ONLINE
  • ON
  • OFFLINE
  • OPTION
  • ON
  • ORDER
  • PCTFREE
  • PRIOR
  • PRIVILEGES
  • PUBLIC
  • RAW
  • RENAME
  • RESOURCE
  • REVOKE
  • ROW
  • ROWID
  • RONUM
  • ROWS
  • SELECT
  • SESSION
  • SET
  • SHARE
  • SIZE
  • SMALLINT
  • START
  • SUCCESSFUL
  • SYNONYM
  • SYSDATE
  • TABLE
  • THEN
  • TO
  • TRIGGER
  • UID
  • UNION
  • UNIQUE
  • UPDATE
  • USER
  • VALIDATE
  • VALUES
  • VARCHAR
  • VARCHAR2
  • VIEW
  • WHENEVER
  • WHERE
  • WITH
Menu