Chatbot Overview
Conversational Bots
Intents & Entities
Intelligent Bots
Kore.ai's Approach
Kore.ai Conversational Platform
Bot Concepts and Terminology
Natural Language Processing (NLP)
Bot Types
Bot Tasks
Starting with Kore.ai Platform
How to Access Bot Builder
Working with Kore.ai Bot Builder
Building your first Bot
Getting Started with Building Bots
Using the Dialog Builder Tool
Creating a Simple Bot
Release Notes
Latest Updates
Older Releases
Deprecations
Bot Builder
Creating a Bot
Design
Develop
Storyboard
Dialog Task
User Intent Node
Dialog Node
Entity Node
Supported Entity Types
Composite Entities
Supported Time Zones
Supported Colors
Supported Company Names
Form Node
Logic Node
Message Nodes
Confirmation Nodes
Service Node
Custom Authentication
2-way SSL for Service nodes
Script Node
Agent Transfer Node
WebHook Node
Grouping Nodes
Connections & Transitions
Managing Dialogs
Prompt Editor
Alert Tasks
Alert Tasks
Ignore Words and Field Memory
Digital Forms
Digital Views
Knowledge Graph
Terminology
Building
Generation
Importing and Exporting
Analysis
Knowledge Extraction
Small Talk
Action & Information Task
Action Tasks
Information Tasks
Establishing Flows
Natural Language
Overview
Machine Learning
ML Model
Fundamental Meaning
NLP Settings and Guidelines
Knowledge Graph Training
Traits
Ranking and Resolver
NLP Detection
Bot Intelligence
Overview
Context Management
Session and Context Variables
Context Object
Dialog Management
Sub-Intents
Amend Entity
Multi-Intent Detection
Sentiment Management
Tone Analysis
Sentiment Management
Default Conversations
Default Standard Responses
Channel Enablement
Test & Debug
Talk to Bot
Utterance Testing
Batch Testing
Record Conversations
Publishing your Bot
Analyzing your Bot
Overview
Dashboard
Custom Dashboard
Conversation Flows
Bot Metrics
Advanced Topics
Bot Authorization
Language Management
Collaborative Development
IVR Integration
Data Table
Universal Bots
Defining
Creating
Training
Customizing
Enabling Languages
Smart Bots
Defining
Sample Bots
Github
Asana
Travel Planning
Flight Search
Event Based Bot Actions
koreUtil Libraries
Bot Settings
Bot Functions
General Settings
PII Settings
Customizing Error Messages
Bot Management
Bot Versioning
Using Bot Variables
API Guide
API Overview
API List
API Collection
SDKs
SDK Overview
SDK Security
SDK App Registration
Web SDK Tutorial
Message Formatting and Templates
Mobile SDK Push Notification
Widget SDK Tutorial
Widget SDK – Message Formatting and Templates
Web Socket Connect & RTM
Using the BotKit SDK
Installing
Configuring
Events
Functions
BotKit SDK Tutorial – Agent Transfer
BotKit SDK Tutorial – Flight Search Sample Bot
Using an External NLP Engine
Bot Administration
Bots Admin Console
Dashboard
User Management
Managing Users
Managing Groups
Managing Role
Bots Management
Enrollment
Inviting Users
Bulk Invites
Importing Users
Synchronizing Users from AD
Security & Compliance
Using Single Sign-On
Security Settings
Cloud Connector
Analytics
Billing
How Tos
Creating a Simple Bot
Creating a Banking Bot
Transfer Funds Task
Update Balance Task
Context Switching
Using Traits
Schedule a Smart Alert
Configure Digital Forms
Add Form Data into Data Tables
Configuring Digital Views
Add Data to Data Tables
Update Data in Data Tables
Custom Dashboard
Custom Tags to filter Bot Metrics
Patterns for Intents & Entities
Build Knowledge Graph
Global Variables
Content Variables
Using Bot Functions
Configure Agent Transfer
  1. Home
  2. Docs
  3. Bots
  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. From Settings -> Bot Management, select Export Bot option.
  3. 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.
  4. Click Export.
  5. The bot definition is exported as a ZIP file.
  6. 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. From Settings -> Bot Management, select the Import Bot option.
  4. Select the Bot Definition File, Bot Config File, and Custom Script File (if any) from the previous step.
  5. 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.
  6. Click Import.
  7. Your Bot is ready in the testing environment for the QA team to test.

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