List of components compatible with latest version

Learn about the list of components that are executed in their latest versions in the RPA Desktop Design Studio and robots, irrespective of the version they were used during the automation design.

Backward compatibility of plugins overview

Robotic Process Automation (RPA) solution is built with backward compatibility of plugins.

An automation built using the earlier plugin versions are compatible with a latest version. For example, if an automation is built using an earlier version of a plugin, 1.0, the RPA Desktop Design Studio, Attended Robot, and Unattended Robot applications run the automation by loading the plugin version 1.0.

If any newer version of a component is no longer compatible with its older versions, they’re documented in the release notes. For more information, see RPA Hub release notes and RPA Plugin Bundle release notes.

Additionally, any automation component interacting with RPA Hub APIs are only compatible with its own RPA Hub version. For example, if the component is released as part of Utah 4.1, then it’s compatible only for that version.

During the infrastructure upgrade for every family or store release (Vancouver, for example), use the MSI packages corresponding to the respective releases.

The following table lists the matrix defining the backward compatibility. In this table, N depicts the latest release version of the software and N-2 depicts two versions prior to it.

Few fundamental components that are essential to build the automation logic are excepted as these components are part of the RPA Desktop Design Studio.

List of components

The following list of components are executed in their latest versions in the RPA Desktop Design Studio and robots, irrespective of the version they were used during the automation design.

Parent Topic:Automation components