We are excited to announce a new set of developments that our team has been working on over the last two weeks.
Our cloud orchestrator BotCity Maestro received major user experience improvements and new features!
Over the next sections we will cover what changed and guide you through the new features! I hope you enjoy it!
Simplified Sign Up
Do you have an e-mail and a password in mind? Great! That’s all you need!
From the new login and password recovery screens all the way to a major product redesign we refreshed BotCity Maestro design and worked to make it more functional and pleasant to work with.
Your door into BotCity Maestro now not only looks better but it is also more functional and bring you easy access to our community channels.
The password recovery screen also received a visual update and bug fixes.
New Home Screen
The log management was only available via the BotCity Command Line Interface (CLI) or via SDK. Logs visualization and download were the only available options via the BotCity Maestro portal.
Today we are glad to announce the availability to not only visualize and download but also create and exclude logs directly from the BotCity Maestro interface.
Clicking on the New Log button will take you to the Log creation screen where you can define the Log label, which is the unique ID to be used when interacting with this Log via the BotCity Maestro SDK or API as well as the columns.
Another major change in regards to logs is that they are no longer limited or tied to a single Automation. Now you can create as many logs as you desire to better organize your data and automation management.
We recently updated our terminology with the intent to simplify the understanding of what
Machines are. Recent updates on the BotCity Maestro replaced all occurrences of the term
Machine with the more appropriate term
To remember, a Runner is a service created by BotCity which runs on a host (computer, virtual machine, cloud-based host, container or some other form). A host can have one or more BotCity Runners being executed in parallel depending on the use case and hardware capabilities.
In the past we had to create Runners via the BotCity CLI using a command like the one describe below:
BotCLI machine new -machineId vm01
Now you can create Runner instances directly from the BotCity Maestro interface by clicking on the New Runner button.
The Runner card contains the other operations that you can perform:
- View instance information
- View Runner instance log file
- Capture Screenshot
- Edit the instance
- Remove the instance
Another great change that we are proud to present is the new feature to manage Bots via the BotCity Maestro interface.
Before this feature was added, the only way to handle the lifecycle of a Bot (Deploy, Release and Update) was via our command line interface and exclusion of bots was not allowed.
Starting now, you will be able to perform all those operations directly from the BotCity Maestro user interface with a couple of clicks.
From the new My Bots menu you can now deploy new bots and versions, mark versions of bots as released, update the bot code and exclude them.
Here is how to do it.
Deploy is the process used to add new bots or new versions of existing bots on the BotCity Maestro platform.
You can deploy a bot by simply clicking on the Deploy button and filling the form with the
technology used. Very similar to the syntax of the command line which was:
BotCLI bot deploy -botId demoWeb -version 1.0 -file demoWeb-1.0.tar.gz -python
Update is the process used to overwrite or replace the code or executable that a given bot is associated with. Please note that this process is irreversible and will overwrite an existing version even if it is marked as release so please be careful.
You can update a bot by simply clicking on the pencil icon on the right side of the line associated with your desired bot version and selecting a new file to replace the current one. That is much simpler than the command line which was:
BotCLI bot update -botId demoWeb -version 1.0 -file demoWeb-1.0.tar.gz -python
Release is the process used to mark which of the bot available versions is the one currently being used when executing the tasks. This version will be downloaded by the BotCity Runner and executed on your host.
You can define the released version by simply clicking on the ribbon icon (highlighted by the red arrow below).
The equivalent procedure via the command line interface was:
BotCLI bot release -botId demoWeb -version 2.0
A new feature! To remove a deployed version, you can simply click on the trash can icon (highlighted by the red arrow) and confirm on the confirmation dialog that will be displayed.
Create your Account
Don’t have a BotCity Account? Sign up for Free
More on the Way
We hope you are enjoying the new features as much as we are while developing and using them.
As always, if you have questions or find any sort of issues or would like to suggest a feature, feel free to reach out to us via one of our community channels.
I won’t give you spoilers but there are many cool features coming up over the next weeks! 🚀
Keep an eye out and make sure to follow us on the social media channels so you can be notified when we release them!
Have fun automating! 🦾🤖