Release Notes

• Library RPA.Browser.Selenium (#1058):

• Fixed options passing with Firefox. (when a binary location is specified)

• General improvements to RPA.*.Application libraries (#1055):

• All: Better error handling (COM -> runtime), improved generic docs and troubleshooting guiding, fixed document closing (if was closed already) and app open/quit management, improved warnings and logging, file paths are tested for existence when operating on documents and raise errors in their absence.

• Excel:

• Removed deprecated parameter tabname from Add New Sheet. (use sheetname)

• Save Excel As raises when there’s no workbook open. (use Open Workbook first)

• Outlook:

• Removed deprecated keywords: Send Message (use Send Email) and Wait For Message (use Wait For Email).

⚠️ Breaking changes in the Application libraries listed above.

Worker release v6.34.7.

Fixes an issue where extracted RCC executable was sometimes locked for the first API call.

You can find the detailed changelog for Workforce Agent Core here.

• Setup Utility force creates necessary folders in order to operate properly
• Running diagnostics after network config add/remove
• RDP connection available only if worker is running
• Ensuring profile in common path - controlled by Admin account
• Forcefully removing unknown workers
• UI/UX improvements all across the board
• Main Page has now specific guidance for users
• RCC Speed Test implementation & integration
• All dependency vulnerabilities are fixed
• New version of embedded RCC at version 14.15.4
• Service Helper Embedded at version 1.13.2
• Internal Status page updated

Download from here and check our updated documentation here

Have a splendid day! 🎉

We are excited to announce some updates to the pricing plans and to the Work Item UX. The 3-minute step run time limit on the Developer plan has been removed, and the Consumption plan has 1500 free run minutes in addition. The plan updates have been rolled retroactively, so you can enjoy the benefits immediately. On the Work Items, mass actions have been updated for you to be able to process more items at once.

Pricing Plan Changes

We felt that some limitations in the Developer plan were too inconvenient to properly try out the platform and that the Flex plan had some discrepancies in the upgrade path, so we decided to tune them a bit in a way that lets you get more bang for your buck.

On the free Developer plan, we have decided to remove the 3-minute time limit for step runs. The forced timeout caused many problems for users, in some cases even terminating the run before the environment was set up in the Worker. This change should allow you to run longer running automations, up to the fixed 240 minutes included in the plan.

The Flex plan has been renamed to Consumption plan to better reflect that it allows you to fully take advantage of the consumption-based pricing and scaling that our platform offers. It is the first plan that does not limit you to a fixed amount of run minutes per month (as in Developer and Starter plans).

In addition, we have decided to add 1500 free run minutes to the Consumption plan to be in line with the upgrade path, so you will also have a base capacity you can use without extra cost.

Work Item UX Improvements

The Work Item mass actions have been previously limited to the page size. Now you can select all filtered Work Items, and perform actions on them. This will reduce the amount of clicks needed in e.g. cases where you have had a lot of application exceptions and want to retry all Work Items at once.

Worker release v6.34.6.

Minor update that improves logging and updates the RCC to latest version (14.15.4).

You can find the detailed changelog for Workforce Agent Core here.

Workforce Agent Core v6.34.4

• Add more information to the artifact upload end event
• Bundle RCC into the Worker executable and extract it during runtime
• Upgrade RCC to v14.15.3

You can find the detailed changelog for Workforce Agent Core here.

• Library RPA.DocumentAI.Base64AI (#719):

• Fix signature matching API.

• Better documentation and errors.

• Library RPA.PDF (#1051; rpaframework-pdf 7.1.6):

• Make the reader parameter optional in the Save PDF keyword.

• Fix PDF fields retrieval, value decoding and setting. (#872)

• Library RPA.Salesforce (#1003): Add keywords Auth with connected app and Execute APEX.
• Library RPA.Email.ImapSmtp (#1054): Fix handling of To, Cc and Bcc fields in Send Message keyword.

In this Control Room update, we are introducing brand new and improved Worker views for you to conveniently manage a large number of Workers, along with a few smaller UX improvements and bug fixes.

Improved Worker Views

The Worker views have been updated to enable more convenient management of Workers and troubleshooting of potential issues in your unattended automations, especially in cases where there are multiple self-hosted Workers or groups involved.

The new views have been structured to provide more information about how the Worker is used in different Processes, Steps, and Groups, in addition to sorting and filtering of data, which helps you to stay on top of operations. Also, the user experience of linking new Workers and managing groups has been improved.

Other improvements and bugfixes

• The parallel execution limit in steps is no more limited by the Worker group size
• Autoremove option has been added to the group link tokens, enabling better management of temporary execution environments
• The rare case of scheduler double triggering process runs has been fixed
• UX improvements to the Vault UI
• The bug where VSCode was unable to get secrets when "Prevent viewing Vault secret values" was enabled has been fixed

As always, we in Robocorp would be most interested to hear what you think about the update, so don't hesitate to contact us in the community Slack!

Maintenance release that brings a bunch of security and bug fixes.

Updates

• Updated default RPA Framework version to 24.1.2

Bugfixes

• Fixed race condition in diagnostics dialog that caused soft lock
• Several security updates to dependencies

To address common security and compliance policy needs encountered often in different organizations, in this update, we are introducing a control to Vault secret visibility on the UI, the possibility to provide a reason for stopping Process Runs for auditing purposes, and new audit log events.

Organization Privacy & Compliance settings

To enable the new features, we have added two new options under the "Privacy & Compliance" tab in the Organization settings. These settings can be accessed by the Organization Owners and Admins.

Vault Secret Visibility

By toggling the "Prevent viewing Vault secret values", vault secrets won't be visible to users after creation from the UI. This can prevent leaking of secure credentials by accident (by e.g. in a screen share) and can be a requirement in IT security policies.

Process Run Stop Reason

By toggling the "Require a reason for stopping a Process Run", users need to provide a reason when stopping process runs manually. This will add the reason to the audit log event regarding stopping the run and is useful for e.g. SOX compliance.

New Audit Log Events

We have added User login (with IP address) and SSO mapping change events to the audit log to cover common security policy and auditing needs.

As always, we at Robocorp would be most excited to hear your thoughts about the features! Feel free to contact us in Slack or other channels if you have any feedback in mind.

Have you tried ReMark💬, our generative AI assistant that helps developers deliver value (bots!) faster? One of the early users said, "Something that used to take me 1 hour to do now takes me 10-15 minutes". Don't miss out on this significant shift in developer productivity. ReMark💬 is available for free here.

The most recent update makes the use of ReMark💬 easier, especially when working on multiple things at the same time. We added conversations. The new left sidebar will keep your conversations in order. As ReMark💬 uses previous messages and responses to answer your questions, remember to hit the "New Chat" button to start fresh when you are changing topics.

Features

• Organise chats with ReMark💬 in conversations
• Rename and delete conversations
• Stop text generation button when ReMark💬 is answering
• Thumbs up and down buttons to give feedback on the quality of answers

Updates

• Better error messages in cases when OpenAI API returns an error

• Library RPA.Robocorp.Storage (robocorp-storage 0.3.2): Fix bug when retrieving assets containing spaces in their names.

• Library RPA.Browser.Selenium (#1035; rpaframework-core 11.0.5): Fix chromedriver download issues with Chrome 115 and over.

• Adds the ability to the Worker to check for the rcc executable in the Workers Common Path
• If rcc executable isn't found in either path (the instance path & the Workers Common Path), it will download it as it did before
• This will provide a more reliable determination in use cases involving Setup Utility

Have a good day!

• Issues with launching Setup Utility are now fixed - missing required entities caused the app to freeze in certain situations
• Everything should now be ensured in the bootstrap sequence
• Upgrading to the former version (v0.15.0), shouldn't cause any problems
• Upgrading to the latest version is always recommended

Have a good day!

• Library RPA.Browser.Selenium (#1021; rpaframework-core 11.0.4):

• Correctly handles and downloads a valid existing webdriver version when there’s a need for one.

• Ability to provide a default browser binary location with the RPA_SELENIUM_BINARY_LOCATION environment variable. (useful when the webdriver isn’t able to automatically detect and start your system browser)

• Portal example taking these into use: here

• Library RPA.Browser.Playwright: Renders documentation for robotframework-browser==17.1.0.

• Service Helper v1.11.2 is recommended

• Go to Internal Status page and upgrade Service Helper

• Latest Service Helper sets the correct permissions for log on service, you don't need the last steps in Setup Utility anymore when adding a new Windows Worker

  • Checking if the user already has a worker designated to it - one worker per user; if the user has already a worker, a new worker is rejected

  • Enable/Disable video stream/data transfer is now possible directly from Setup Utility

  • Test the RDP Connection by opening one directly from Setup Utility

  • Adding a new Windows Worker is prefaced by an automatic profile deployment to the user - the current profile from the Admin account is used for the deployment - as such, the proper rcc environment is propagated to all users

  • Manually deploy the current profile to a desired user account from Profile Management

  • Reinforced clean up after Worker is removed - deleting known files from known locations

• Fixed the Submit Issue problems

• You can now reliably Submit Issues to us and we thank you for them :)

• Improvements in the UI/UX in certain areas of the app

• Download from here and check our updated documentation here

Have a splendid day! 🎉

• Library RPA.Robocorp.Storage: Takes into use robocorp-storage 0.3.1 and replaces the limited generic keywords with the ones below. (#1016)
• Set Bytes Asset & Get Bytes Asset
• Set Text Asset & Get Text Asset
• Set JSON Asset & Get JSON Asset
• Set File Asset & Get File Asset

⚠️ Breaking changes: Old Set Asset & Get Asset keywords are gone, please replace them with one of the pairs above.

24.0.0 - 18 Jul 2023

Other noticeable past releases

23.5.2 - 29 Jun 2023

• Library RPA.Robocorp.Storage: Add support for using Assets in VSCode

23.5.1 - 28 Jun 2023

• Library RPA.JavaAccessBridge:
• Update and pin java-access-bridge-wrapper to version 0.14.1

23.5.0 - 27 Jun 2023

• Library RPA.JavaAccessBridge:
• Update java-access-bridge-wrapper to version 0.13.0
• Add keyword Print Locator Tree

23.4.0 - 22 Jun 2023

• Add new library RPA.Robocorp.Storage for managing assets within Asset Storage in Control Room. (#957)

Updates on Robocorp Code

• The logging from robocorp.tasks/robocorp.log is now integrated directly into VSCode (ROBO TASKS OUTPUT view).
• Note: Requires robocorp.tasks 2.1.2, robocorp.log 2.3.0 and Robocorp Code 1.7.0.
• Elements which have a location can now be clicked to open the related file directly inside of VSCode.
• The terminal view can now also show entries logged from robocorp.log debug|warn|info|critical and not just stdout/stderr.

Other noteworthy changes in Robocorp Code:

• Fixed issues in Run Task / Debug Task code lenses (launching robocorp.tasks):

• Robot environment properly used when robot is available.

• The input work item is properly selected when available.

• If multiple entry points in the same file were available the selected one will be run.

• If a robot.yaml has preRunScripts they'll be run prior to launching.

Noteworthy changes in robocorp.log:

• Added robocorp.log.debug (so, there's one more level available to log messages).

• It's possible to filter log levels by using setup_log(log_level='debug|info|warn|critical') (so that log levels filtered out won't even be added to the log.html).

• It's possible to also redirect to sys.stdout or sys.stderr the messages added with log.debug, log.info, log.warn and log.critical by using setup_log(output_log_level='debug|info|warn|critical') along with setup_log(output_stream={'debug': 'stderr'}) (note that the current default is just redirecting critical calls to stderr).