Remote agent updates - Review updates in the Remote agent versions such as new and enhanced features as well as fixes and limitations.

Automation 360

Review updates in the Remote agent versions such as new and enhanced features as well as fixes and limitations.

Versions summary

The following table lists the Remote agent versions.

Version Compatible with Recorder package version
3.5.2.2 2.11.5 and later versions
3.4.3 2.11.5 and later versions
3.2.0 2.11.5 and later versions
3.1.0 2.11.5 and later versions
3.0.0 2.11.5 and later versions
2.6.2 2.11.5 and later versions
2.3.3.29 2.11.5 and later versions

3.5.2.2

What's new
Remote agent installer - Remote Desktop (RDP) support
The Remote agent installer now supports RDP connections, enabling Recorder to capture object properties of web and Windows controls on machines and VMs connected via RDP.
Note:
  • Ensure that you use the Bot Agent (version 23.0.28 and later).
  • Multi-user RDP session is not supported

3.4.3

What's new
Enhanced Citrix XenApp automation with remote agent
You can now automate applications with window titles that have additional characters after \\Remote running on Citrix XenApp environments using the remote agent. Automation is now supported on non-English operating systems, with improved detection of window title text in non-English languages. Wildcard (*) support is now enabled for flexibility when specifying window titles.
Note:
  • Automations created with older versions of the package are fully compatible with the new remote agent. You can continue to run your existing automations without any changes required.
  • When using the new package with the old remote agent, your automations will function in the same way as they did with the previous remote agent version.

    This ensures compatibility between different package and remote agent versions, so you can update with confidence and maintain consistent automation performance.

3.2.0

What's new
Automate web apps that use the Shadow DOM standard

Recorder now supports object-based automations of modern applications that use the Shadow DOM standard enabling you to seamlessly automate such web applications. The introduction of CSS selector will further enhance the reliability of various web automation processes.

Automate web apps that use the shadow DOM standard
Fix

A360.RemoteAgent.exe process no longer crashes and now runs successfully when you use Recorder in your automations.

Service Cloud case ID: 02135681

3.1.0

What's new
Expanded automation coverage (Service Cloud case ID: 02094579, 02113994)
You can now successfully automate browser applications that are running on the same user session but requires varying application-level access within the same automation workflow. For example, non-admin users can perform record creation and validation, and admin users can now provide approvals within the same process automation.
Note:
  • This capability is supported for automation of web applications running on Google Chrome, Microsoft Edge, and Microsoft Edge with IE mode browsers.
  • This capability is supported through the Application tab only. Browser tab and Browser package is currently not supported.
  • This capability is supported with Recorder package (version 3.2.1-20240606-105427 and later) and Bot Agent (version 22.60.23 and later).
  • When your Bot Agent is updated, you must restart your browser application.

Recorder package

3.0.0

What's new
Improved automation reliability and performance in Java application

You can now reliably automate controls in Java applications, such as, Oracle EBS applications using the new properties, namely Frame name and Occurrence. This improves the performance and reliability of automations.

Recorder package

2.6.2

Fix

On a multi-user system, the Automation.bot.BrowserAgent.exe process now executes faster when you deploy your bot from the Google Chrome or Microsoft Edge browser.

2.3.3.29

Fix
You no longer encounter issues when you capture an object and run the bot in the Xen app environment.

Previously, when you captured an object, closed the application, and reran the same bot, it failed with an error.

Service Cloud case ID: 01981082