2020.10.1

This shift comes with a host of improvements for those already familiar with modern folders: you can now easily move folders in or between hierarchies, delete folders and all their associated entities, and modify the associated permissions for the default folder roles.

To get you even closer to a ready-to-automate place, new tenants have personal workspaces enabled by default and the five out-of-the-box roles created automatically. Hand-in-hand with the switch to a modern-only approach, the associated permissions of the default modern folder roles have been updated.

The Administrator user comes with the following roles at the tenant level: Tenant Administrator, Allow to be Folder Administrator, Allow to be Automation User, and Administrator.

To offer a clearer separation between a folder admin's attributions and those of a tenant admin, we removed robot management privileges from folder-focused roles (Allow to be Folder Administrator and Allow to be Automation User). As a best practice, we recommend creating a separate role consisting of Robots permissions and assign it to users who need it in a controlled manner.

Keep an eye on all workspaces from a centralized location and give a helping hand to developers in their daily activities by exploring the contents of their workspaces at a glance.

Keeping Orchestrator clean of unused data is now a breeze. You can quickly identify all workspaces with little or no activity, or those which have been orphaned upon employees leaving the organization. The clean-up strategy is at your discretion and is pretty much hassle-free, as you can either delete or convert the workspace into a folder from the convenience of the dedicated Personal Workspaces page.

Enabling personal workspaces for numerous users is now a seamless process with a new feature allowing you to enable workspaces for multiple users at once. The Personal Workspaces section on the Settings page is the dedicated place for that. Here, an administrator can enable personal workspaces for all users in a tenant that use a particular attended licensing profile and don't yet have a workspace to call home.

To help you identify and differentiate processes from one another, they now inherit the associated package description set at design time in Studio. This happens regardless of whether they are deployed manually or automatically in a personal workspace. You can also add a description to your processes or edit the existing one as you wish, no restrictions imposed. Learn here how to add a process to Orchestrator.

Updating processes across multiple folders to the latest available package version just became easy-breezy with a new bulk update feature, which enables you to upgrade all processes associated with a package. Simply select the target packages, and Orchestrator does the job for you by searching for and displaying all associated processes that do not use the latest available package version. Choose the processes to be updated to the latest available package version, and you’re done.

You can now preview any changes made to the header color and logo such that you can adjust them accordingly before saving your changes.

You can now assign users, user groups, and machine templates directly at the folder level by navigating to the Settings page in a folder context.

Assigning machine templates to folders has been made easier than ever with the addition of new capabilities previously only available on the Machines page. As a result, you can now copy a machine’s key and edit its runtimes directly from the Folders page. Bear in mind, machine templates need runtimes in order to be fit for execution, so make sure you assign some when assigning the machine to a folder.

To have a better, ready-to-hand overview of your Orchestrator statistics, you can now navigate from the job counters on the Home page to the corresponding Jobs page, which is filtered accordingly. For example, if you click the section corresponding to running jobs, the displayed page has the Running state filter applied.

The Processes page now displays the package name associated with each process.

You can now easily update the default roles with any additionally required permissions.

We've taken your feedback into account and renamed some of the predefined roles available on the Settings page. Click here to see the new names and the corresponding permissions for each role.

We improved the migration experience for upgrading to Identity Server-enabled Orchestrator in Azure deployments and added a rollback in case of failed migrations.

Publishing test automations with test cases automatically creates a process if it is not already in place.

Test Schedule creates a new test execution only if the previous run has finished.

Execution Media is now supported for your test executions so that you can view any screenshots taken from failed executions.

Create test sets directly on the Test Cases page.

Test sets created through external tools are now visible only through API and will not be shown on the Test Sets page.

We now perform a couple of additional validations upon uploading test automation packages. In order to successfully upload such a package or package version, make sure the following:

We improved performance for release version filtering and test set creation.

You can now choose from all available versions when selecting packages for test set creation.

You can now filter logs by the name of the host machine they have been generated on by using the Machine filter on the Logs page. The new filter works retroactively for logs stored in ElasticSearch, while for logs stored in the database, it only works for new log entries.

To keep you notified about everything going on in Orchestrator, we've implemented alerts for Folders and Personal Workspaces. Learn about alerts.