Separation of development and production environments on the Botmaker platform

In this article, you will learn about the separation of development and production environments on the Botmaker platform.

Estimated reading time: 05 minutes

Platform usability specifications

The client will have access to all the Botmaker platform features and will be able to perform, independently, the training and configuration of the bot. In addition, the client will be able to perform content expansions, integrations with APIs and web services, and the creation of manual support teams.

To accomplish these initiatives, the Botmaker platform offers a separation of environments so that new features and implementations do not affect the productive version of the bot until they have been tested and approved. In this sense, two fundamental issues are considered:

  • Setup intents in test mode and then publish them

After logging into the platform, through Menu>Chatbots, clients will be able to access the Chatbots section to configure the conversational flows of their bot. Once the topic or intent has been created, they will not be visible until they are published, as shown in the following image:

1

Thus, topics and intents can be modified as many times as required before they are published and visible to end-users.

  • Set up custom roles with the assignment of responsibilities to achieve cross control

The platform allows creating custom roles and assigning responsibilities to build a cross-control scheme where implementation roles cannot publish changes to their own implementations. This means that publishing will be done by agents with QA and testing roles.

Custom roles are typically used by teams having specific agents and service queues for different areas of the business or company and are assigned for different functions.

For this purpose, the platform has editable permissions that allow defining test and deployment environments. The permissions enable the performance of different actions and are as follows:

  • Account
  • Agents
  • Audiences
  • Campaigns
  • Channels
  • Change history
  • Chatbots and flow manager
  • Chats
  • Code
  • Configuration
  • Dashboards
  • Entities
  • Flow manager
  • Help
  • Import contacts
  • Intents
  • Metrics
  • Notifications
  • Queues
  • Recommendations
  • Responses
  • Roles
  • Segments
  • Shortcuts
  • Templates
  • Variables
  • User groups
  • Webhooks

Edit roles

2

Available permissions

3

Development environment considerations

The platform has a test bot to assess the conversational flows of the client's bots so that the necessary modifications can be made before the flows are productive and available to users. Thus, in any section of the Menu, by clicking on the icon 4in the upper right corner of the screen, it is possible to test the bot to see how it responds.

5

On the other hand, in the Chats section, Menu>Conversations>Chats, it is possible to mark a conversation as Tester to be answered by the "Development" bot and evaluate its performance according to the configured intent tree before it is released to production.

This option is available to test the Development bot from all connected channels.

6

In this way, the Botmaker platform offers a clear separation of development and production environments that ensures secure operability and reflects customer needs.

Remember to visit our Help Center for further information.

Written by: Botmaker Team

Updated: 6/15/2022

Articulos relacionados

Tags

Botmaker Information