April 2024

April 26, 2024

Reverting name fields prepopulation

A week ago, we announced that the name fields for processes and triggers would be prepopulated with the name of the package and of the process, respectively.

We have since discovered a small hiccup, so we are rolling back this feature while we work on fixing the issue. We'll keep you posted on the reenablement as soon as it happens.

Storing Orchestrator and Automation Cloud Robots data in new regions: UK and India

As part of our commitment to empowering organizations with control over their data, we are providing complete data sovereignty for the United Kingdom and India regions. We use replication capabilities to securely store data in multiple availability zones within the region.

To learn more about the available tenant regions and the services offered in each region, explore our resources on Data residency.

April 24, 2024

Large data fields usage optimization changes

We have listened to your feedback and have made the decision to revert the change that was announced in mid-March, namely the removal of specific large data fields from the Get All - QueueItems endpoint. This means that the SpecificContent/SpecificData, OutputData/Output , and AnalyticsData/Analytics fields are no longer removed. The implementation had been rolled out for Community and Canary tenants, and has now been rolled back.

We still want to ensure thorough system performance, so, as a result of this reversal, we are making a series of changes to select fields of the GET/odata/QueueItems endpoint to help with just that. These are the data limits that you can expect over the next few months:

Field	Limit	Rollout to Community tenants	Rollout to Enterprise tenants	Notes
Progress	1,048,576 characters	Today	May 2024	Starting with September 2024, this will be changed to 102,400 characters for Community and Enterprise tenants.
AnalyticsData	10 KB	June 2024	September 2024	-
Output	100 KB	June 2024	September 2024	-
SpecificData	500 KB	June 2024	September 2024	-
ProcessingException - Reason	102,400 characters	June 2024	September 2024	-
ProcessingException - Details	102,400 characters	June 2024	September 2024	-
The $top filter	> If you do not use the $top filter, you receive 100 records by default. > If you use the $top filter, you receive a maximum of 100 records. Anything exceeding 100 triggers a 400 Bad Request error message.	June 2024	September 2024	Prior to applying this change, the behavior was as follows: > If you did not use the $top filter, you received 1,000 records by default. > If you used the $top filter, you received a maximum of 1,000 records. Anything exceeding 1,000 triggered a 400 Bad Request error message.

You can find out more about these changes in Queue items fields.

April 16, 2024

Removing classic folders

As announced in the deprecation timeline, and detailed in Classic folders removal, we are now fully disabling classic folder access.

API audit enhancements

The API audit monitoring tab has been enhanced with a few pieces of helpful information:

• The tab header now includes a description of what you can expect to find in the graphs, along with a link to our documentation pages, which provide detailed information.

• Each graph contains a View API button taking you to the corresponding endpoint in the Orchestrator Swagger file.

Changing information density in Orchestrator grids

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.

This is a comparison of the two density views:

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

• The spacing between table rows is smaller. The information is still perfectly visible, as we have simply removed blank spaces.

• The number of rows that can fit on a single page has significantly increased, thus making more information available at a glance.

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.

Manage Access split

To better manage your objects (i.e. groups, users, robot accounts, external apps) and make use of all available types of identities, we have split the groups, users, robot accounts, and external apps into separate pages. You can find these under dedicated tabs, on the Manage Access page.

As an overview of the tabs, the All tab includes all objects that have been assigned access at the tenant level. The Groups, Users, Robot accounts, and External apps tabs include the local and directory groups, local and directory users, robot accounts, and external apps that have been assigned access at the tenant level.

Viewing spike details

The API audit monitoring tab has been enhanced with even more information on your API usage: you can now click the spike corresponding to the desired minute to display its details in an expandable side panel.

The information that is available to you includes the process name, the folder where the process resides, the host name, the number of calls performed to that endpoint during the selected minute, the status code, and the user agent. On top of that, clicking the eye icon (1) for a process opens the details of the associated job, while clicking the expand icon (2) opens the side panel in a full-sized window.

The selected spike details section in both view modes: collapsed and expanded

Collapsed filter logic change

To optimize the view for you when working in Orchestrator, we have improved the collapsed filter logic. If there are more than five filters on the page, these are collapsed under an icon, regardless of the grid view that is used.

Prepopulating name fields for processes and triggers

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.

April 1, 2024

Support for API keys ending in March 2025

In our continual efforts to maintain the highest levels of security and user experience, we have decided to phase out API Keys authentication in March 2025.

We recommend using External Applications and Personal Access Tokens (PATs) as the primary method of authentication.

Expiry of API tokens

Current API Tokens will undergo no immediate changes – they will be supported until March 2025. Please note that after this date, API Keys will be removed from our authentication method offerings.

Migration to new authentication methods

Users currently using API Keys are strongly encouraged to transition to using External Applications or PATs as soon as possible. This shift not only aligns with best practices for OAuth 2.0 but also ensures a much securer and manageable authentication process.

Check out Migrating from API Keys to PATs for step-by-step instructions on the switch.

Local groups renaming

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.

Milliseconds in exports and archives

You can now benefit from an extra level of detail through the addition of milliseconds to time columns in the following instances:

• Exported reports for all available objects, i.e. audit logs, queue transactions, logs, and jobs (details...)

• Queue items archive output (details...)

Removing BypassBasicAuthRestriction

The BypassBasicAuthRestriction parameter in Users endpoints is now removed, as announced in the deprecation timeline.

Folder tree no longer collapsed

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.

Removing icons from menus

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.

New columns in queue transactions exports

Queue transaction exports now include two new columns: Analytics Data and Created (absolute). On top of that, transactions can now also be filtered by CreationTime via the API before performing the export.

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

When can I see these changes?

The date when a change is first announced in the release notes is the date when it first becomes available.

If you don't see the change yet, you can expect to see it soon, after we roll out changes to all the regions.

More information

Deprecation timeline

We recommend that you regularly check the deprecation timeline for any updates regarding features that will be deprecated and removed.