Skip to main content

June 2025

June 23, 2025​

Granting solution permissions to custom tenant roles​

When creating a custom tenant role, you can now grant Solution deployments and Solution packages permissions to the role.

Uploading multiple files to a storage bucket​

You can now select and upload multiple files to a storage bucket at once.

High density view always enabled​

High density view is now enabled permanently, and the option to configure the setting is no longer available.

Displaying audit data in the side panel​

On the Audit and Test Automation Audit pages, selecting View Details for an item now displays the audit information in the Audit Data panel.

June 13, 2025​

Migration of mixed roles​

As previously announced in our Deprecation timeline, this week, we are starting the migration of mixed roles across all Community tenants.

The migration involves the following changes:

  • We are retiring the Administrator role and replacing all existing assignments to the role with assignments to the following roles:
    • The Orchestrator Administrator role, at tenant level.
    • The Folder Administrator role, at folder level.
  • We are splitting custom mixed roles into two separate roles:
    • A role containing all previous tenant-level permissions.
    • A role containing all previous folder-level permissions.
      note

      The new roles retain the name of the original role, followed by the appropriate suffix, as follows:

      • The -TenantScopedOnly suffix, for tenant-scoped roles.
      • The -FolderScopedOnly suffix, for folder-scoped roles. We will transition all existing assignments from the original mixed role to the appropriate new roles.
  • Since the Robot role functions as a custom mixed role, we are splitting it into Robot-TenantScopedOnly and Robot-FolderScopedOnly roles.

Improved audit logs for automatically disabled triggers​

The audit log now specifies the reason for automatically disabling a trigger in the following scenarios:

  • The trigger was disabled upon exceeding the values defined in the tenant-level settings for Triggers - Disable when job creation fail count and Triggers - Grace period when job creation keeps failing count (days).
  • The trigger was disabled due to the trigger-level Set execution-based trigger disabled toggle being enabled and the values for Disable when consecutive job execution fail count and Grace period on disabling the trigger (days) being exceeded.

Testing module deactivation for new tenants​

Starting with this update, the majority of the Testing module in Orchestrator is deactivated for any newly created tenant. This change involves certain limitations on the Testing tab in Orchestrator, as follows:

  • The Test Schedules and Test Data Queues tabs are not available anymore. However, you can still create test schedules in Test Manager, and existing test data queues on existing tenants continue to work. For more information, visit Scheduling executions in Test Manager.
  • The Test Executions tab now displays the Status column, instead of the Result column. The Status column indicates the current status of the Orchestrator test execution, such as: Pending, Running, Cancelled, and Finished. Test results are visible only in Test Manager.
  • You cannot execute individual test cases anymore. However, you can still execute Orchestrator test sets but only using APIs (including CI/CD integrations).

For all your test data management efforts, use Test Manager.

Bug fixes​

The tenant-level Overview page and the folder-level Home page only displayed job statistics for RPA jobs. The pages now display statistics for all job types.