New features: Runner and task visualization, error alert information by e-mail and Office 365 plugin

Blog
1

This is a discussion topic for the original post at New features: Runner and task visualization, error alert information by e-mail and Office 365 plugin - BotCity | Python RPA | Blog

Hello, world! :wave:

We have fantastic news to share with you about our Python RPA tools. Follow this article.

[0] Runners visualization

From now on, you can have a new way to view runners in the BotCity Maestro interface.

By clicking on “Runners” in the menu on the left side of BotCity Maestro, you have the distribution of the runners in “cards” as small squares, each with a runner, with the status, name in link format, an icon to copy the runner’s name, the screen, and the three dots icon to access the options menu.

image-9-1024x473.png1024Ă—473 26.6 KB

But now, next to the runners status filter, you can click on the icon to choose one of the available screen view formats. In one format you will have the runners in the organization informed above, in another you will have the list format.

image-7-1024x477.png1024Ă—477 25.8 KB

This list has identified columns:

  • screenshot: if it is a desktop runner, this column will have the screen print; if it is a background runner, there will only be a generic image;
  • name: to inform the name of the runner and this name is a link that, by clicking on it, you will access the runner’s information screen;
  • machine id: is the runner’s identification;
  • type: tells you the runner’s type;
  • status: when it is red, it means that the runner is offline; when it is green, it means that the runner is online;
  • In the last column is the three dots icon, with the same menu options as the screen laid out in card format.

You can still continue to use the filters as usual to view only what you need at that moment. For example, bring only the runners that are online.

image-5-1024x479.png1024Ă—479 18.6 KB

[1] Task queue visualization

The same change that occurred for runners has also been applied to the task queue view.

Next to the filters is the icon for changing the view mode. In one of the formats, we can identify the tasks in cards, as is already possible today.

image-8-1024x470.png1023Ă—470 18.3 KB

The second form of visualization is organized in a list.

image-6-1024x475.png1024Ă—475 25.1 KB

And in this list, we have some columns with the following identifications:

  • id: which informs the task’s ID;
  • priority: which tells you the priority of the task (from 0 to 10);
  • state: line with the color that indicates the status of the task. To find out what each color means, check the legend located above the search filters;
  • automation label: identification of the automation by which the task was created;
  • runner: informs the runner in which the task was executed;
  • user name: indicates the name of the user who created the task;
  • date creation: field in which is the date and time that the task was created;
  • date last modified: field containing the date and time at which the task was last modified;
  • finish message: informs the message that the task was finished.

[2] New information in the e-mail error alert

Until now, it was already possible to set up error alerts to be received by e-mail. However, there has been an enhancement to these alerts, in which we have included more information to better understand what has happened and whether any action is required.

image-4.png482Ă—560 20.5 KB

In the alert we have the information:

  • organization: which indicates which organization the automation was created as a link to access, if necessary;
  • task id: contains the id of the task that had an error as a link to access it, if necessary;
  • automation label: which informs the identification of the automation as a link for access, if needed;
  • bot id: which informs the bot’s identification as a link to access, if necessary;
  • bot version: which indicates the version of the bot that was executed;
  • error type: which contains the type of error that occurred during execution;
  • error message: which tells you the error message.

It is important to remember that you can configure and customize both errors and alerts by using the BotCity Maestro SDK in your project, as oriented in our documentation. Access the link about the errors here and the link about the alerts here.

[3] Office 365 Plugin

We have several plugins that can be very useful during the development of your automations. All the documentation about these plugins and how to use them is on this link, and you can easily follow the step-by-step process.

And now we have the new plugin to make it easier to use the Office 365 (or Microsoft 365) API if you need it. To better understand how to use this plugin in your project, either to integrate with Onedrive or Excel, see our documentation with all the guidelines.

Important: Before any step, you need to create your credentials. Without this, you will not be able to use the plugin to integrate with services correctly. So start by creating the credentials and understand that part first with the guidelines in this link in our documentation.

Keep following to know the next news

We hope you have enjoyed these new features. And soon we will bring you more content. Be a part of our community by joining slack, following the news in our documentation and here on the blog, and learn a lot from our forum.