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. How Tos
  5. How to manage Bot Release Lifecycle

How to manage Bot Release Lifecycle

In this How-To, we will explore a scenario wherein your organization has set up multiple stages before a bot is finally made available to the end-users for the purpose of bot development, testing, pilot and production release.

Problem Statement

Consider the case wherein the developer has completed the bot development and it needs to be moved to the testing environment for the QA team to access and test the same. The bot definition does not change drastically except for a few environment-specific values.

In this document, we will show how the bot export and import functionality can be used to achieve the same. Refer here for more on Bot Import and Export.

Pre-requisites

  • Bot building knowledge
  • A fully developed and functional bot. Here we are using the Banking Bot.

Implementation

Step 1 – Export Bot

  1. In the development environment, open the bot you want to move to the testing environment.
  2. Select the Deploy tab from the top menu
  3. From Bot Management, select the Import & Export option.
  4. Choose the Export tab
  5. Select the bot components you want to export. The first time you will want to export all components, subsequently, you might want to choose to export only selected components.
  6. Click Export.
  7. The bot definition is exported as a ZIP file.
  8. The file may be used to check the bot definition into your code repository or to attach it to any ticketing system.

Step 2 – Modify config.json

  1. Any variables that need environment-specific values will be available in the ​config.json​ file present in the exported file.​
  2. Update these Global Variables (see here for more on Global Variables and here for an example).
  3. Now the file can be shared with the infrastructure / DevOps teams for initiating deployment in other environments.
  4. If you have permissions, you can import the bot to the target environment by following the steps given below.

Step 3 – Import Bot

  1. Extract the files from the zip file exported in the previous step.
  2. In the testing environment, create a new bot.
  3. Select the Deploy tab from the top menu
  4. From Bot Management, select the Import & Export option.
  5. Choose the Import tab
  6. Select the Bot Definition File, Bot Config File, and Custom Script File (if any) from the previous step.
  7. Select the Full Import Import Option. Note that if you are using this option in an existing bot the current bot configurations will be erased and replaced with the imported bot.
  8. Click Import.
  9. Your Bot is ready in the testing environment for the QA team to test.
  10. Note: While exporting/importing a virtual assistant, only authorization profiles used in dialog or alert tasks are included. Unused authorization profiles are ignored. See Bot Authorization to understand more about authorization profiles.

Step 4 – Update Bot

Chances are you need to modify the bot and apply those changes to the bot in the testing environment.

  1. From the development environment, open the modified bot.
  2. Select the Deploy tab from the top menu
  3. From Bot Management, select the Import & Export option.
  4. Choose the Export tab
  5. Select the bot components you want to export. You might want to choose to export only modified components.
  6. Click Export.
  7. The bot definition is exported as a ZIP file.
  8. Extract the files from the zip file.
  9. Change the values for any variables that need environment-specific values in the ​config.json​ file present in the exported file.​
  10. In the testing environment, open the bot that needs to be updated.
  11. Select the Deploy tab from the top menu
  12. From Bot Management, select the Import & Export option.
  13. Choose the Import tab
  14. Select the Bot Definition File, Bot Config File, and Custom Script File (if any) from the previous extract step.
  15. Select the Incremental Import from the Import Option section
  16. Click Import.
  17. Your Bot is updated and ready in the testing environment for the QA team to test.

How to manage Bot Release Lifecycle

In this How-To, we will explore a scenario wherein your organization has set up multiple stages before a bot is finally made available to the end-users for the purpose of bot development, testing, pilot and production release.

Problem Statement

Consider the case wherein the developer has completed the bot development and it needs to be moved to the testing environment for the QA team to access and test the same. The bot definition does not change drastically except for a few environment-specific values.

In this document, we will show how the bot export and import functionality can be used to achieve the same. Refer here for more on Bot Import and Export.

Pre-requisites

  • Bot building knowledge
  • A fully developed and functional bot. Here we are using the Banking Bot.

Implementation

Step 1 – Export Bot

  1. In the development environment, open the bot you want to move to the testing environment.
  2. Select the Deploy tab from the top menu
  3. From Bot Management, select the Import & Export option.
  4. Choose the Export tab
  5. Select the bot components you want to export. The first time you will want to export all components, subsequently, you might want to choose to export only selected components.
  6. Click Export.
  7. The bot definition is exported as a ZIP file.
  8. The file may be used to check the bot definition into your code repository or to attach it to any ticketing system.

Step 2 – Modify config.json

  1. Any variables that need environment-specific values will be available in the ​config.json​ file present in the exported file.​
  2. Update these Global Variables (see here for more on Global Variables and here for an example).
  3. Now the file can be shared with the infrastructure / DevOps teams for initiating deployment in other environments.
  4. If you have permissions, you can import the bot to the target environment by following the steps given below.

Step 3 – Import Bot

  1. Extract the files from the zip file exported in the previous step.
  2. In the testing environment, create a new bot.
  3. Select the Deploy tab from the top menu
  4. From Bot Management, select the Import & Export option.
  5. Choose the Import tab
  6. Select the Bot Definition File, Bot Config File, and Custom Script File (if any) from the previous step.
  7. Select the Full Import Import Option. Note that if you are using this option in an existing bot the current bot configurations will be erased and replaced with the imported bot.
  8. Click Import.
  9. Your Bot is ready in the testing environment for the QA team to test.
  10. Note: While exporting/importing a virtual assistant, only authorization profiles used in dialog or alert tasks are included. Unused authorization profiles are ignored. See Bot Authorization to understand more about authorization profiles.

Step 4 – Update Bot

Chances are you need to modify the bot and apply those changes to the bot in the testing environment.

  1. From the development environment, open the modified bot.
  2. Select the Deploy tab from the top menu
  3. From Bot Management, select the Import & Export option.
  4. Choose the Export tab
  5. Select the bot components you want to export. You might want to choose to export only modified components.
  6. Click Export.
  7. The bot definition is exported as a ZIP file.
  8. Extract the files from the zip file.
  9. Change the values for any variables that need environment-specific values in the ​config.json​ file present in the exported file.​
  10. In the testing environment, open the bot that needs to be updated.
  11. Select the Deploy tab from the top menu
  12. From Bot Management, select the Import & Export option.
  13. Choose the Import tab
  14. Select the Bot Definition File, Bot Config File, and Custom Script File (if any) from the previous extract step.
  15. Select the Incremental Import from the Import Option section
  16. Click Import.
  17. Your Bot is updated and ready in the testing environment for the QA team to test.
Menu