2024.10

If you know and love our live streaming and remote control feature, then you will already be aware that it is supported by a VNC server. Up until now, this has been TightVNC, but, with the advent of the Robot 2023.12 release, we are moving to RealVNC.

RealVNC is included in your Studio installation package, and requires no configuration whatsoever. Nothing changes on your part - if anything, things should be smoother from now on. However, this means that we will no longer be offering support for TightVNC.

For details, see the Live streaming and remote control via RealVNC section in our user guide.

We have changed our retention policy for recorded videos. Now, when you choose to record a job execution from the settings of its underlying process, the video is stored in Orchestrator as follows:

You can now see the folders where the processes associated to a certain package are included. This is done at the tenant level, by clicking the See processes option in the contextual menu of the desired package or package version. The resulting window displays the folders where that particular process is used. However, please note that only folders that you have view and edit access to are listed.

For details, see Viewing package processes.

The Machines, Processes, and Queues sections featured in the Monitoring page, at both the folder and the tenant level, are now split up in two tabs:

The Historical (Insights) tab provides a series of features that we are certain will be very useful to you. These include:

For optimal resource utilization and smoother workflows, we have improved our queue triggering system with a new option: After completing jobs, reassess conditions and trigger new jobs if possible. In addition, this prevents idle robots and stagnant queue items. For more details, refer to Queue triggers.

We are happy to announce that you can now manually delete In Progress queue items from the Transactions window. This option comes highly requested, and we are confident that it will make your automation lives easier. All you need to do is select the desired queue items, then click Remove, just like you would for items with other statuses.

A new credential store is now integrated with Orchestrator: CyberArk® Conjur Cloud. This integration aims to provide a more secure and efficient way to handle credentials within Orchestrator, thus enhancing your automation capabilities.

The severity level of the User started exploring your personal workspace. alert has been increased from Info to Error. This ensures that you are notified via email whenever an administrator starts exploring your personal workspace.

When it comes to your libraries, you have a choice to use host feeds, tenant feeds, or both. Based on what you choose, the Libraries page of the tenant's Packages menu is populated with your feed list. Up until now, though, this view was limited if you chose to use both host and tenant feeds. Now, when you select said option, the Libraries page is split into Tenant and Host, with each section displaying its corresponding feeds.

We have split the auto-retry mechanism into two options, as follows:

For more details, refer to Managing queues in Orchestrator.

We are adding the following queue item fields:

The objective is to complete the traceability of queue item retries. All existing fields will remain in place, and will be used for automatic retries.

Our mission of optimizing the access control framework continues with a significant improvement to the roles and permissions check window.

For any questions regarding supported fields, you can check out the new Fields supported for queue transactions exports page.

The Personal automations setup tab featured in the role assignment window has undergone a few important changes:

The Audit Data window for the Sessions component now includes the Maintenance field, which displays the status of the Maintenance option for unattended machines. 1 marks the enabled status of the machine maintenance mode, and 0 marks its disabled status.

The configuration of processes and triggers has been improved by prefilling their name fields based on the previously selected package or process.

For processes, the Display Name field displays the name of the selected package in the format <PackageName>.

As far as triggers are concerned, the Name field displays the name of the process, followed by the trigger type in the format <ProcessName>_<TriggerType>. It is also worth mentioning that this change applies to time, queue, and API triggers, and that the Name and Process Name fields have switched positions to follow the logical flow.

The character limit for searching in the tenant Audit window has been increased to 64.

You can now rename your robot account after creating it.

Any and all name changes made to local groups at the organization level are now propagated to Orchestrator.

Please note, however, that renaming a group several times in a short timeframe means that only the last renaming event is captured in the Orchestrator audit logs. The organization-level audit includes all such events.

Now, any changes made to your directory users in the Admin portal - including updates or deletions - are reflected within your Orchestrator's user list and audit logs across all tenants.

When a directory user is deleted:

Please note, a delay may be experienced whilst synchronizing these updates to Orchestrator.

External feeds used for libraries can now also be secured through basic authentication credentials, as is already the case for packages.

We removed SMB storage from Automation Suite, and therefore, we recommend using external storage instead.

As part of our ongoing optimization efforts, we have removed the following feature flags and enabled them by default. Therefore, you can no longer configure any feature flags per tenant at the host level:

If your database supports a read-only replica, Orchestrator will use it by default to improve performance and scalability. For more details, refer to the Orchestrator read-only replica.

In December 2023, we launched an option to see the folders where the processes associated to a certain package were included. At the time, only folders that you had both view and edit access to were listed in the Processes of package window. We have now removed the need to have edit access, which means that all folders that you have view access to are listed. The edit option is, however, only enabled for folders that you also have edit access to.

User experience best practices, as guided by your suggestions and use cases, are always top-of-mind for the Orchestrator team. In trying to align our product design to these practices, we are improving the display density of grid information. This means that you will now see tables in a compact mode, which allows for more items to be displayed, ultimately taking better advantage of screen real-estate.

We are confident that the high-density view will provide you with an overall better experience:

You do, however, have the option to go back to a low-density view, by deselecting High density view from the General > Application settings section of your tenant-level settings.

During the first iteration of the jobs side panel implementation, the folder tree was automatically collapsed when the panel was expanded to a full-sized window. Now, the folder tree is persisted even while the job details window is in full-sized mode.

As part of our constant effort to provide you with the best user experience, we have decided to remove icons from menus. This means that our user interface is now cleaner, more streamlined, more readable, and more accessible. We are confident that this change will allow you to focus on explicit information without distractions and the need for interpretation.

Orchestrator now supports multiple selection across various filters, allowing you to manipulate data more quickly and have a more streamlined workflow.

You can select multiple options for the following filters:

When you try to disable a webhook, its name is now displayed in the Confirm action window. Previously, it was identified by its URL.

The Type list of the Search in tenant window now also includes an App entry, allowing you to search for specific apps within a tenant.

The Processes page now includes two new options: View Logs and View Jobs. The options allow you to easily access the logs and jobs associated to a specific process.

You can now easily copy a folder's path by using the Copy folder path option in the desired folder's contextual menu.

To simplify the logs, we have removed the CreationTime field from the Audit logs.

When searching for resources within your tenant, the Type column now displays the resource category, such as:

To enhance operational efficiency, we have hidden the Check Folders and Permissions option for orphaned robots, where the owner no longer exists as a user in Orchestrator.

We have improved the following:

The Source filter on the Jobs page now includes Apps, Studio, and API trigger, allowing you to further filter the job to display.

Reports endpoints available for audit logs, robot logs, and queue definitions are now removed. As such, we advise against using the following:

If you would like to retrieve such reports, we recommend these steps:

This release brings security updates and patches to address Common Vulnerabilities and Exposures (CVEs).