January 2023

If the Update Server module is disabled, the update service on the robot machine no longer checks for updates.

Testing Automation Cloud robots - serverless has never been easier. If you were previously worried about the cost implications of such a decision, fret no more as we have now introduced a more affordable option for testing or non-production environments. To put it briefly, we now charge fewer robot units (RUs)/minute for testing serverless jobs.

Note that you must be on the Enterprise, Pro, or Pro Trial licensing plan to benefit from the new testing RU consumption paradigm. If you are a Community user, you cannot use testing runtimes.

While the numbers you were used to continue to be applicable to production environments, test RU consumption has been reduced to half. For more details, see Machine sizes and costs.

Wondering how this is reflected in the Orchestrator UI? First of all, you will see that the runtime details are displayed for both production and testing when configuring the serverless robot machine. Aside from that, when executing the unattended automations, you now need to specify whether you want to use Cloud - Serverless or Cloud - Serverless Testing as a runtime license. You may also want to know that if you run a test case or test set from the Testing panel in Orchestrator, these job types now consume the testing RU amount by default.

Similarly to Serverless testing runtimes, now you can execute test cases on your Automation Cloud robots VMs at a lower cost, as we adjusted the robot unit (RU) consumption rate for testing environments. The cost of Automation Cloud test robots starts at 2,000 RUs per month, and increases with your VM size. Just make sure to select the Testing/NonProduction environment while configuring your Cloud robots - VM pool, and then, when you run a job, select the Cloud - VM Testing runtime.

You now have the option to add multiple VMs to your manually managed Automation Cloud robots - VM pools.

Learn how to add multiple machines after you create the manually managed VM pool.

The Create option for the Execution Media permission is now enabled by default within the tenant-level Automation User role.

The process version included in the Job Details window was incorrect, displaying the latest version uploaded to Orchestrator. Now, the Process Version field correctly renders the version used to run the job.

Orchestrator did not display the list of arguments for updated and republished Studio REF projects. This issue occured when adding new arguments on top of existing ones in Studio projects based on Robotic Enterprise Framework templates.

Orchestrator now offers the necessary infrastructure to add and manage your own secure credential stores. To that end, we have created the Orchestrator Credentials Proxy, which is deployed either through an .msi installer or through a Docker image, and which enables you to integrate third party plugins in the existing solution.

These third party plugins are made available to Orchestrator through credential proxies. Proxies are created at the Orchestrator tenant level, in the new Proxies page, which is available in the Credentials menu, and are linked to the Credentials Proxy through a public URL and a secret key.

To expose the credential stores, on the Stores page, which is also available in the Credentials menu at the tenant level, select the newly created proxy from the Proxy menu. This will display its underlying stores in the Type menu, allowing you to select and define the desired option.