You can no longer license your Studios locally when using Automation Cloud Orchestrator services. In this respect, we removed the Stand-alone License checkbox from Orchestrator. Customers who licensed their Studio/StudioX/Studio Pro locally prior to this change are not impacted, however, they cannot use this feature for additional Studios.
We can enable this feature on demand. Contact us.
To streamline robot migration from classic folders to modern folders, we've made it possible to easily enable/disable robots residing in classic folders. This way, you are presented with a rollback option if a step errors out during migration. You can only disable robots in the following connection states: active, disconnected, unresponsive.
Disabling a robot impacts associated entities as follows:
- You cannot configure triggers to use disabled robots
- Disabled robots are removed from existing triggers that make use of that specific robot. If there is no other specific robot defined, the trigger throws errors as it cannot create jobs.
Assets per robot
- Disabled robots are removed from assets with per robot values
- If the asset only has one robot value and we disable the robot, the asset remains in an inconsistent state and cannot be modified.
Reenabling the robot renders all impacted entities usable.
The Processes page now displays the package name associated with each process.
- Disabling test automation did not disable any running test schedule.
Updated 12 days ago