Using Bot editor

As a Bot Creator, you can build bots on the workbench and perform various bot operations. The Bot editor provides an easy to use feature-rich experience.

Default view in the Bot editor

We provide implicit preference to retain the default view, so you do not have to set them explicitly in the Bot editor. When you create or modify an existing bot in the Bot editor, your preferred default view (List, Flow, or Dual) will persist; and if you switch to another browser or log out and log back into the Control Room, you will see your default view. When you open a bot in the Bot editor, the default view is displayed as follows:
  • If you open the bot for the first time, Flow view is shown as the default view. However, you need to change the view by selecting it based on your preference so that you can see the same view upon your subsequent login.
  • For all subsequent visits to the Control Room, your last selected view will be set as the default view.
The set default view remains the same across browsers and user sessions.

Ignore pop-ups during automation execution

You can choose to ignore unexpected pop-ups as part of automation resiliency settings. This enables the bot to complete the task without any runtime issues.

Managing unexpected pop-ups | Create your first bot | Edit a bot

Line markers for collapsible sections of code

When you create bots using Loop, If/If-else, Step, Trigger-loop, Try, Catch, and Finally statements, you will see the visually highlighted collapsible sections on the Bot editor. These visual indicator line markers are displayed at the beginning and end of the collapsible section. Additionally, when you select the collapsible section a line displays that connects the beginning and end brackets.
Note: The visual indicator line marker for the collapsible section applies only to the List view in the Bot editor.

Visually highlighted collapsible sections on the bot editor

Error messages with descriptive information

When you create a bot where the parent bot calls a child bot, and if an error occurs in the child bot, the error message displays the following details:
  • Line number of the parent bot which ran the child bot.
  • Line number of the child bot where the error occurred.
  • Error message details, such as what went wrong with that line number and the corresponding corrective action.
The following example shows different error messages displayed during runtime:
  • One parent bot calls two child bots.

    For example, you build a parent bot such as Bonus calculation. The parent bot calls the child bot Company performance, and then the child bot Company performance calls another child bot Profits2022. If the error is in the child bot Profits2022, the following error message will be displayed:

    Error message displayed when you have less than three bots

    View the following video that outlines the sample error scenario

  • One parent bot calls multiple child bots.

    For example, you build a parent bot such as Bonus calculation. The parent bot calls the child bot Company performance, and then the child bot Company performance calls another child bot Employee performance. Then Employee performance calls Completed targets > Profits2022 . If the error is in the child bot Profits2022, the following error message will be displayed:

    Error message displayed when you have more than three bots