1. Is it available for Python or .NET users?
At the moment it is only available for Java developers. However, Python and .NET editions will also be released in the coming months.
2. What is the difference between a bot instance and a bot account?
The bot instance is the program running in your infrastructure and the bot account is the service account your administrator defines in the admin console.
3. Is it possible for two bots to talk to each other with only one program?
Absolutely! Being able to manage multiple bot accounts from one instance allows granular control over bot to user interactions, mapping for instance a level of contracts such as freemium, premium, silver, and gold.
4. What is the difference between the old and new versions of BDK?
The BDK has a full mapping to the entire Symphony API provided in an intelligent way to ease coding.
It comes with new services such as message templating where you can plug your own templating engine or use one provided out of the box. A new Activities API, real foundation to implement workflow automation that I will detail later, and also logging and monitoring services to make sure your bot is reliable and make sure you are alerted when something wrong happens.
We know go-to-market is a key factor of success for innovations developer teams are trying to achieve, that’s why we took time to provide smooth integration with development frameworks such as SpringBoot and others, as well as making sure code assistance will provide an intuitive coding experience.
5. Please provide more details on what has been showcased during live demos?
1. Symphony Bot Generator
In order to leverage the Symphony Bot generator, we navigate to our terminal and create a new folder. Once inside, you can run the command $ yo symphony 2.0. This command launches the Symphony Bot Generator and prompts us with a number of questions to bootstrap our Bot.