Release Notes

The following improvements are now available in Robocorp Log 2.7.0:

• if statements now create a scope in log.html (when the function is not a generator).

• If an exception has a cause or context the context/cause is now shown in the log (i.e.: when an exception is raised from another exception or is raised while handling another exception all exceptions are shown).

• continue and break inside a loop are properly handled.

• continue and break are now shown in the logs.

• It's now possible to expand / collapse recursively in log.html.

• log.html: When navigating using left arrow, if the element is already collapsed the parent is focused.

• Spec version changed from 0.0.3 to 0.0.4.

• re.Pattern is now accepted at add_sensitive_variable_name_pattern.

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).

We're excited to announce our new automation framework for Python automations – simply called robocorp. The release brings the experience of developing Python automations on par with Robot Framework on our platform. The project templates in our VS Code extension have been updated to use the new framework and leverage its capabilities.

Check out our blog post for in-depth story about the new features, or view and read the summary below.

Features

• New @task Decorator: Any method decorated with @task becomes runnable, and can thus be scheduled or otherwise managed as a part of a Process or Assistant in Control Room.
• Visual and Autogenerated Logs: We've brought the loved logging features from Robot Framework to Python, all without you having to write a single line of code. Furthermore, you can now control the logging with ease, suspending logs for sections dealing with sensitive data in several different ways.
• New Robocorp Automation Libraries: While our rpaframework libraries are based on Python, we wanted to enhance the developer experience for those choosing to work on Python exclusively. The new robocorp automation libraries roll out focusing on common automation tasks (Excel, browser, APIs) and interacting with Robocorp Control Room (such as Vault, Asset Storage, Work Items).
• New Python Templates in VS Code and Portal: Easiest way to start using these new capabilities is through the new Python templates in VS Code. They are already available, for example have a look at Playwright Browser automation template.