Version a Robot
Creating a new version of a robot gives you the ability to fall back to an earlier version of the robot. Additionally, you can have multiple versions of a robot active in an environment.
Use Cases
The following scenarios illustrate the power of versioning:
-
Fall back to an earlier version of a robot
If you need to update a robot that's already been deployed to a higher environment, create a new version of the robot first. That way, if any issues occur with the new robot's version after deployment, you can always fall back to an earlier version of the robot.
-
Have two or more versions of a robot active at one time
Consider the following scenario: Robot Version 1 runs successfully on an application. The application recently released an update featuring significant changes to the user interface. The changes are available in a testing environment for a couple months and then will be available in production. You create Robot Version 2, update it for the changes to the user interface, and deploy the robot to production so that you can ensure the robot runs as expected. In this situation, Robot Version 1 and Robot Version 2 are active at the same time in production.
Version a Robot