In this update we’ve implemented a new algorithm of building unique selectors for web-elements through Browser Picker, added a feature of forcing a bot to stop in case the normal stop fails to work and made important changes to the Orchestrator’s UX. Read these newest Release Notes and find out what we’ve prepared for you!

Main Changes

Here’s the overview of the main changes:

• New feature (Studio Pro) - New unique selector search algorithm (Browser Picker).

• New feature (Studio Pro, Bot Runner) - Hard stop for bots.

• Improvement (Orchestrator SaaS) - Various UX/UI adjustments (prevent users from publishing bots with missing parameters, use existing name and description when republishing etc.).

Complete Changelog

Improvements

Studio Pro:

1. New unique selector search algorithm (Browser Picker). Browser Picker tool (for Chrome) now always creates a unique identifier (selector) for the specified element. The necessary attributes and hierarchy levels are selected automatically.

2. Hard stop for algorithms. Users now have a choice when stopping bots execution. It is possible to use ‘soft’ stop (by waiting until the current action is complete) same as before. Alternatively, now it’s also possible to ‘hard' stop it and not wait until the action is complete.

3. Prevent users from exporting algorithms with unset parameters. Now it won’t be possible to complete the export to .neex file if the algorithm has unset parameters. 

Bot Runner:

1. Show the subprogram in error messages. Now if an error occurs during execution of an algorithm that contains subprograms, the exact subprogram that caused the error will be mentioned in the error message. 

Orchestrator SaaS:

1. Various UX/UI adjustments.

   1. Prevent users from publishing bots with missing parameters. Similar to exporting to .neex in Studio, this change also prevents users from publishing algoirthms with missing parameters. 

   2. Use existing name and description when republishing. If a user decides to republish an existing bot, the existing name and description will be used for it. 

   3. The horizontal tabs in Orchestrator SaaS - “Bot Runners”, “Workflows” - have been replaced with a new vertical menu:

      1. The menu contains four pages: 'Dashboards', ‘Workflows’, ‘Bot Runners’ and ‘Integrations’.

      2. It’s shown in the left part of the screen similar to the menu in the account home page.

      3. As some of the functionality is not present yet, the corresponding tooltips are added.

2. Other interface changes and fixes.

   1. 1. New ‘Added’ status. It’s displayed if a bot is added to Orchestrator but there is no Bot Runner assigned to it.

      2. Added tooltips for all the statuses.

      3. Display of the next launch time of the workflow (if scheduled). If the launch is scheduled for today, then the ‘Today at…’ text will be shown. If the launch is planned for the other day, then this date will be shown according to the user’s local time.

      4. Improved home page design - the large product cards are replaced with smaller ones as well as cards leading to “Teams” and “Billing” are added.

      5. The “User Account Settings” section contains more information about the user.

Bug Fixes

Studio Pro:

1. Fixed an issue when the ‘Stop’ button in the popup won’t actually stop bot execution in debug mode.

2. Optimization of mechanisms that led to long launch time of Picker.

3. ‘Read emails’ activity: fixed incorrect behavior of calendar, fixed overwriting of files with duplicate names.

4. Fixed an issue when opening a workflow file that has ‘()’ in its name.

5. Fixed an issue with repeated output of error messages.

6. Fixed an issue when saving an algorithm with pending changes could lead to an error.

7. Fixed a crash when using ‘Do-while loop'.

8. Fixed incorrect path to a screenshot when using ‘Click on image’.

9. Fixed an error when interacting with with web elements that have type = file property.

10. Fixed wrong behavior of the ‘Get element value’ activity that caused Cannot read property 'code' of undefined error.

11. Fixed an issue when focus was removed from the last executed block in debug mode.

12. Addressed performance issues when running big algorithms.

13. Fixed an error that appears after clicking the ‘Force to close Chrome’ button.

14. Fixed uncontrolled changing of properties when adding ‘Write Excel file’ to the canvas.

15. Fixed an issue when copying an activity with an interface element to a newly created workflow would require saving the workflow before pasting the copied activity.

16. Fixed issues with wrong behavior of Chrome picker when selecting some web elements.

17. Fixed an issue when ‘Block input’ activity would negatively affect the algorithm execution time.

18. Fixed incorrect errors handling in ‘Get property’ and 'Get value' activities.

19. Fixed occasional memory leaks when running algorithms containing JS scripts.

Bot Runner:

1. Fixed wrong behavior of ‘Get element value’ activity that caused Cannot read property 'code' of undefined error.

2. Fixed an error that appears after clicking the ‘Force to close Chrome’ button.

3. Fixed an issue when Bot Runner could not execute ‘User Notification’ activities.

4. Fixed the ‘Disable status window’ option not working.

Orchestrator SaaS:

1. Fixed an issue with duplicated ‘Event’ column.

2. Fixed validation messages in the login window.

3. Fixed behavior of the menu in the left part of the screen.

4. Fixed an issue with images not loading properly.