Orchestrator release notes

DELIVERY:

Last updated May 21, 2025

May 2025

May 21, 2025

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 Manger.
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.

May 20, 2025

Bug fixes

QueueItem.transactionAbandoned webhook events occasionally had a wrong timestamp of 0001-01-01T00:00:00. We have fixed the issue.

May 15, 2025

Monitoring displayed as landing page in tenant context

When you navigate to Tenant in the user interface, Monitoring is now displayed as the landing page.

Process side panel improvements

To make process information easier to retrieve, we have grouped the process details into tabs:

Package Requirements: Provides a view of the package requirements for the process.
Jobs: Lists the job executions for the process. Extensive searching and filtering capabilities assist you in locating specific items.
Logs: Lists the logs for all jobs that executed the process. You can drill down to individual job logs or export aggregated logs for all jobs.

Job side panel improvements

We have enhanced the Job details tab to make the input and output move visible.

Additionally, the Runtime details section of the tab now provides more detailed information.

For more information, refer to Viewing job details.

Re-enabling entry point selection when starting a job

As we announced in Entry point selection when starting a job temporarily not possible, we temporarily disabled the feature due to a bug. We have now fixed the bug, and you can use the feature normally.

For more information, refer to Starting a job.

Running jobs as yourself with access inherited from groups

You can now start a job using the Run as Myself (Personal automation) option if your user inherits appropriate tenant-level and folder-level access configurations from a group that the user is part of. Previously, you could use the Run as Myself (Personal automation) option to start a job only if an administrator had assigned a specific access configuration to your user in that folder.

Improved experience when attempting to start a job with no suitable account

In the Start Job window, if the job cannot start because a suitable account is not assigned to the folder, you receive an error message explaining the issue. Also, the Assign an account to the folder button is highlighted.

Additionally, selecting Assign an account to the folder now allows you to create a new account on the fly and assign the appropriate roles to the account. You can then resume the Start job workflow.

For further information, refer to Starting a job.