Release Notes

Robocorp Inspector includes Locator Manager, which streamlines the process, allowing you to edit, validate, and delete locators—all within a single, integrated package inside our Robocorp Code extension for VS Code, eliminating additional installation steps.

In our Inspectors, we balance recording, automatic locator generation, and giving the full power to the developer also to solve complex cases. The recording and UI are there to help and make the simple cases… well, simple, but it also allows you to directly edit and write the locator yourself and use the validation tools to see the results.

🪟 For Windows automations

✅ Parent-Child Rule Creation: Effortlessly define relationships between elements to enhance accuracy.

✅ Interactive Field Selection: Directly select fields to create rules, eliminating guesswork.

✅ Real-Time Validation: Instantly verify the effectiveness of your locators to ensure reliability.

✅ Screenshot Capture: Automatically save screenshots for reference, providing a visual confirmation of your locator.

🌐 For browser automations

✅ Recording: Seamlessly record your browser activities, and the Inspector generates accurate locators on the fly

✅ Strategy Adjustment: Switch between locator strategies and methods flexibly, ensuring the most robust solution for your needs.

✅ Locator Validation: Validate your locators within the tool quickly, ensuring optimal performance

✅ Code Generation: Copy and paste generated Python code directly into your project, saving time and reducing the potential for errors

✅ Screenshot Capture: Automatically takes screenshots to help recall the associated elements for your stored locators

...Image and Java locator supports will be following shortly.

TL;DR: We are transitioning from Robot Framework and moving all our focus to Python. Existing bots developed in Robot Framework will continue to operate as usual. We'll provide critical updates related to Robot Framework-specific issues until Feb 15th 2025, according to our one-year LTS plan for Enterprise customers. All our new developments will be directed towards Python's dynamic and expansive ecosystem. We recommend our users develop all new automations on Python.

Robocorp platform will be Python-only

Advancements in Generative AI and LLMs have revolutionised how we approach problem-solving and automation. We realized the potential of Python as a language for automation and AI early. Last year, we announced that we invested heavily in Python on our platform, ensuring that, at minimum, everything that was possible using Robot Framework would be available for Python developers. We have reached that date now.

👉 Today marks a significant milestone in our platform's evolution. As part of this transition, we're announcing discontinuing support for Robot Framework on the Robocorp platform. While we will continue to offer bug fixes and security updates for Robot Framework related features until February 15th, 2025, official support will cease thereafter. It's crucial to understand that automations developed with Robot Framework will remain fully functional within the Robocorp ecosystem. 👈

Robot Framework has served us well, providing a solid foundation for automation - all based on Python. However, by focusing on Python only, we allow our customers to enjoy scale and speed that only comes with an ecosystem as vibrant as Python.

What will happen in detail?

There is no immediate impact on existing bots: Automations built on Robot Framework will continue functioning as usual, ensuring your ongoing operations are not disrupted.

We announce a deprecation of Robot Framework on the Robocorp platform on Feb 15th 2024, with one-year long term support guaranteed for Enterprise customers (until Feb 15th 2025). The old Robot Framework bots will continue working even after this; we simply do not issue fixes to Robot Framework-related tooling anymore.

Our developer tooling going forward only supports Python. However, we will issue CVE fixes for the following year.

• Language Server Protocol (LSP) for Robot Framework extension for VS Code remains open-source and available, but we cease to support new features or new versions of Robot Framework.

• Robocorp Code Extension will support only Python code generation in the inspectors/recorders and its other features. The same will apply to the ReMark developer AI assistant.

• Our documentation site will be focused on Python tutorials and examples. However, we will keep a snapshot of current Robot Framework examples and docs until 2025.

We will restructure our automation libraries over time to focus on Python and to remove the dependency on Robot Framework that exists today in RPA Framework. This work was already started mid 2023 with the introduction of robocorp libraries. See details of all automation libraries here.

• RPA Framework (our open-source project with the automation keywords many of our users have gotten familiar with) remains available and supports RPA use-cases (like Java apps, Excel, Outlook, PDFs and much more). However, examples and documentation are added only in Python going forward.

• Some RPA Framework libraries will be deprecated as there are better ways to accomplish the same functionality directly with well-maintained Python libraries. This will be communicated later.

Our recommendation for action

While there are no immediate consequences to currently running Robot Framework bots, we recommend our customers take the following action:

• Start developing new automation workflows in Python. All three certification courses are available now in Python and are a great starting point for developers.

• Review the “Switch to Python” page for detailed instructions on what is new, and decide if your organisation will implement any existing Robot Framework automations in Python. We do not require this, but in some cases, it will help with maintenance.

Relevant links

• Read the full blog post with more details

• Switching from Robot Framework to Python page

• Python automation certification courses

• ReMark code generation assistant

• Snapshot of Robot Framework-related documentation

Updates:

• When the "use desktop" option is enabled from Control Room, create a proxy executor only when the worker is running with "--service" CLI argument

• By default a service created with Service Helper "setup-desktop" command will set the worker to run with this argument

• Better error handling when fetching CA certificates from system store

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

Enable/Disable Processes

You can now disable (and enable) any Process in the Control Room: useful if the process targets a system that needs maintenance and you don't want to run automations needlessly. Disabling the process will prevent the start of new runs via the UI, API, schedules or triggers. Any ongoing runs will progress as usual until completed.

Here's how it works:

Git Task Package Update via API

For the Task Packages connected to Github or Gitlab, you can now programmatically update the Git reference (tag, commit or branch) via the API. This makes it much easier to roll out task package updates as part of your CI / CD pipeline. Read more from the API docs.

• Library RPA.Excel.Application (#1149):

• Add new keyword Create Pivot Field for creating pivot fields for the pivot table.

• Add new keyword Create Pivot Table for creating pivot tables in a spreadsheet.

• Add new keyword Create Table for creating a table in a spreadsheet.

• Add new keyword Find for finding a value in a range.

• Add new keyword Get Pivot Tables for getting pivot tables in a spreadsheet.

• Add new keyword Get Range for getting a range in a spreadsheet.

• Add new keyword List Tables for listing tables in a spreadsheet.

• For all RPA.*.Application libraries (#1149): Add new utility keyword for Robot Framework syntax Set Object Property

• Security dependency fix given the bump of cryptography package to version 42.0.2. (#1149)

Read pull requests linked above for more information.

In this release, we are introducing Enable / Disable for Workers to make maintenance operations more convenient, a new self-service option for MFA, along with some UX updates.

Enable / Disable Workers

Due to popular demand, we have added a functionality that lets you temporarily disable Workers. Any ongoing work at the time of disabling the worker will be completed, but new work will not be allocated to this Worker while the status persists. This enables you to conveniently do maintenance operations, e.g., updating Workers or target systems, without having to change the related process configurations. When the Worker is re-enabled, it will continue processing the pending work.

When disabling a Worker, you can optionally enter a reason, which will be visible in the Worker Event Log. Also the related events are generated in the Workspace Audit Log, along with the information of the actor.

Self-service option for MFA

We have added a new self-service option for MFA, which lets you to require entering an authenticator code to be able to access the Control Room to enable an additional layer of security. The MFA can be enabled from the user settings, after which you will be guided through the setup. Organization and Workspace administrators are able to see which users have the MFA enabled from the member list.

Features

• Enable / Disable Workers
• Self-service option for MFA

Updates

• UX Improvements:
  • Settings pages have been updated to match the rest of the Control Room
  • You can now select a role when inviting users to an Organization

Your friendly code gen assistant ReMark is a bit better again! Apart from tweaks and minor fixes, we’ve done two bigger things, both visible in the screenshot below.

Connect Action Server

Last week, we released the developer preview of Action Server. This new feature allows you to create AI Actions that interact with any data or application and connect them with any AI App and Agent framework, such as GPTs and LangChain.

⭐ Please leave a star to Action Server project in GitHub, and help us keep building open-source!

Testing your AI Actions run with Action Server is now possible with ReMark! Just hit “Connect Action Server”, then copy-paste the exposed URL and bearer token that you’ll get when starting the Action Server with action-server start --expose , and you are good to go! This is a handy way to test things while developing new AI Actions.

Reorganised “tool” collections

Remember that we created separate tools from different source data types, like Python docs, Robot Framework docs, API specs, etc. While moving over to agent/tool architecture has been great, it wasn’t optimal. So we went halfway back. 😎

There are now just two instead of multiple tools (or source data collections). These two highlight the biggest “choice” our users make: whether to build bots on Python or Robot Framework language. The generic source data is replicated on both collections, with the only difference being that they aim to serve you better than before, prioritizing the language (and examples) of your choice.

Features

• Connect Actions Server to ReMark

Updates

• Reorganised RAG data sources to two main collections: Python and Robot Framework

17 Jan 2024

• Library RPA.Cloud.Google (#1145, rpaframework-google 8.2.0):
• All init_ keywords will return initialized service instance.
• Library level documentation refactoring. Authentication related examples are now in their own markdown file.

See Github pull request for more details on the release.

We're thrilled to introduce a new addition to the Robocorp platform: AI Actions and the Action Server. You can think of AI actions as the connective tissue between AI agents and your applications and data.

These new features are available as a developer preview for the community and are fully open-source under the Apache 2.0 license.

Developers can now create AI Actions that interact with any data or application, along with our low latency Action Server connecting them with any AI App and Agent framework such as GPTs and LangChain.

Given the recent release of the OpenAI GPT Store, and the success of AI app frameworks like LangChain, developers are looking for ways to integrate these with various data sources and platforms. Robocorp provides the easiest way to enable AI agents, assistants, and copilots to use custom actions, all written in Python. It’s easier than building Flask apps, or figuring out how to deploy to Vercel.

The community preview release includes the following:

• Introducing the new package robocorp.actions with @action decorator. AI Actions are Python scripts, workflows, or automations that are securely exposed to AI apps. They are defined by their inputs and outputs, and are described in natural language. This makes it easy for AI apps to comprehend and use them. You can conveniently build and debug these actions with the Robocorp Code extension for VS Code.

• Action Server is a stand-alone executable that connects Actions with AI apps. This server automatically generates an OpenAPI specification for your Python code, allowing various AI/LLM Agents to understand and invoke your @action. It also offers a straightforward local UI for testing and monitoring, handling the full Action lifecycle, and provides comprehensive event traceability during runs.

• LangChain Robocorp Toolkit and a template for quick startup. Extending the AI apps built with LangChain is as simple as one, two, three. The new langchain-robocorp package lets you import all your actions into your project effortlessly.

• Revamped Robocorp Github Repository - This is your gateway to AI Actions and open-source Python automation. We've consolidated all the key features into one repository, which includes the Python framework with automated logging, libraries for automating tasks such as browser and desktop applications, and the new Action Server.

It's time to get started! Visit the GitHub repository for more details, and don't forget to leave a ⭐ while you're there.

We at Robocorp wish you a happy new year 2024! In this year's first release, we are introducing the new Activity View and Vault endpoints to the Control Room API.

Activity View

With the new Activity View, you are conveniently able to track what is going on in all of your Workspace from a single view.

You can see the status of the recent Process Runs, Step Runs and Assistant Runs, and also see what's going to be run next from the Scheduled Runs tab. With filters and search, you are able to filter e.g. all Failed runs, which will streamline the exception handling and troubleshooting flows.

API endpoints for Vault

To cover more use cases with the Control Room API, we have added new endpoints that you can use to create and update Vault secrets. This will enable you to programmatically manage your secrets, e.g. by automating credential updates.

For more information about the new Vault API, see the API documentation.

Features

• Activity View
• New API endpoints for Vault
• Account Member Management for Partners

A lot of improvements based on feedback to the new Web and Windows Inspectors

• Web inspector:

  • Test locators with a push of a button on all views.
  • Support iframes
  • Detect page changes
  • Define target webpage over inspections
  • UX improvements

• Windows Inspector:

  • Always provide the main application locator code line
  • UX improvements

• SideBar renaming to the new terminology (from Robot -> Task Package/Tasks/etc.)

Full changelog here

• Library RPA.Outlook.Application (#1144): Add reply_to and check_names parameters for Send Email.

Check Github PR for more details on these parameters.

Updates:

• Upgrade RCC to v17.12.0
• Improve RDP connection error messages
• Close the FreeRDP client gracefully to make sure the full logs are received
• Ignore native-certs module load failure in Windows evaluation versions
• If the module is not loaded the support for loading CA certificates from system store is disabled

New experimental feature to use Windows Remote Desktop Connection Manager tool as the RDP connector with desktop setup. RDCMan is used automatically if config file is found from path: %LOCALAPPDATA%\robocorp\workforce-agent-core-service\rdcman-config.rdg. It can also be configured via the environment variable "RC_WORKER_RDCMAN_CONFIG_PATH", pointing to the RDCMan config file path.

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

New Robocorp Inspector is now available and directly integrated in VS Code.

The new Inspector is integrated into VS Code, so no extra pieces are needed; this comes with the Robocorp Code extension v1.14.0

👉 Get going via: Command-palette → Robocorp: Open Inspector

Web recorder in action:

Windows Locators in action:

🚀 Use Web Recorder to get started seamlessly, then fine-tune the recorded actions into locators you can store and manage later.

• Change strategies after picking/recording, the browser stays on while you develop, etc.

• Complete freedom to create more advanced locators

• Code generation for Python, get single lines or complete scripts

• Built on Playwright, but the locators work with Selenium and RFW

🚀 Much improved Windows capabilities

• Pick from an application or browse from the UI tree.

• Complete freedom to the developers to use the way they need to:

  • Create and combine rules into parent-child locators, use the UI, or type the advanced locator you know.

  • The test-button for each step is right there to enable you to create solid locators no matter what.

• Store as locators or just get the generated Python code, just like for the Web recorder.

We've had a 4-month gap in updating the latest RCC, which ends now 🚀

For the last four months, we've been working hard on the new enterprise Firewall setups coming online and finding solutions to work with those. RCC is the keystone in solving and distributing these solutions.

The breaking change between v16 and v17 is that we dropped the interactive commands for profile creation. These were only used to help bootstrap new network profiles, so the change is quite limited. The task of profile creation is now handled by Setup Utility, which has all the testing and diagnostics tools right next to profile creation with a nice UI.

The new features and improvements list is a long one, but I am raising a few here:

• A lot of TLS-related testing and diagnostic solutions were added
• A lot of tooling around certificates needed and used by the MITM firewalls
• Improvements in environment build speeds
• Space usage tracking to enable simpler cleanups
• Less load subprocess monitoring
• Detecting multiple users sharing ROBOCORP_HOME

That's not all; please check the full changelog for all the details.

(This version of RCC is already available in the latest Worker and is coming out to VS Code and other tools as well).

• Library RPA.Browser.Selenium (#1139): Keyword Open Available Browser won’t anymore try to initialize webdrivers for browsers that are not installed in the system.
• Library RPA.Crypto (#1140): Fix AES256 return types for keywords Generate Key and Decrypt String.
• Library RPA.Hubspot (#1106): Extract the RPA.Hubspot library out of the main package and into its own package rpaframework-hubspot. This is a breaking change, please update your conda.yaml accordingly.

⚠️ Warning

This is a breaking change if you are using the RPA.Hubspot library within your task packages, please add the rpaframework-hubspot package into your conda.yaml to continue using the library.

In this release, we are introducing Work Item Log, Documentation for Processes, new possibilities to integrate with AWS, and new Audit Log events.

Work Item Log

Want to know more about how your Work Items have been processed for troubleshooting or auditing purposes? The new Work Item Log feature enables you to do exactly that!

When you open the Work Item Log from the Work Item details, it will show you what has interacted with the Work Item, how, and when. This enables you to see the lifecycle of the item, giving broader visibility to the processing flow.

Process Documentation

Say hello to the new Process Documentation feature! You are now able to add a description for Processes, where you can include descriptive information about the Process itself, e.g., what the Process is about, how the Process works, and who are the responsible contact persons.

The Documentation supports Markdown syntax, so you are able to add images, links, or whatever you see as valuable to convey the information. And, of course, we also have an API available so you can programmatically fetch the process information, including the description!

AWS integrations

Robocorp Control Room runs on AWS, and so do many of our customers. AWS-native integrations can enable convenient and secure integrations utilizing the AWS backbone. Today we are announcing the first two:

• Production release: Accessing AWS resources from Robocorp-hosted Cloud Workers

• Early Access: EventBridge

Audit Log improvements

We have increased the retention time of Audit Log events to 365 days for new events recorded after the 16th of November. Also, three new events have been added to the Audit Log:

• Process Schedule Created

• Process Schedule Updated

• Process Schedule Deleted

Features

• Work Item Log
• Process Documentation
• New AWS integrations
• Audit Log improvements

Updates:

• Worker network actions now use CA certificates automatically from the system certificate store (NodeJS support for firewall / proxy certificates)
• Upgrade RCC to v17.10.0
• Fix an issue where a slow environment resulted to a backlog of desktop stream files to be sent long after execution had finished

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

In this release, we are bringing new features to help utilize the new Control Room API, to improve Task Package version management, and to get familiar with the available Control Room features by examples.

New API helper features

Say hello to the new and improved API Helper! With the API Helper, you are able to conveniently select what you want to do, and the API Helper will select the right parameters, helps you to create keys with right permissions, and gives an example call in curl, python, and javascript code. In addition, you are able to directly test the calls from your browser to see that they work exactly the way you want.

Version control improvements

We have enhanced the Control Room version control integrations and introduced a new pinned version capability. With the new feature, you are able to select the exact commit or tag you want your tasks to use, which is useful when e.g., integrating with external CI/CD systems or when you need total control over your release cadence.

Example processes in the Control Room

Getting started with Control Room or want to have a quick walkthrough of the most important features? Try out the brand new example processes! When creating an example process, you will get a fully setup process with an example configuration, that you are able to explore at your own pace. In addition, you are of course, able to change the parameters to modify the example to suit your needs.

Features

• New & Improved API Helper
• Link to Commit / Tag with Version Control
• Improved Control Room New User Experience

• Library RPA.Robocorp.Vault (#1129): Improve error message when trying to connect to Control Room Vault without valid connection details.
• Library RPA.SAP (#1130): Add keywords for pressing F1 or F4 on textfield and gridview elements. Thanks to Enrico Franzelli for the contribution!
• Relax importlib-metadata version requirement to allow 4.13.0 and above.