Novembre 2024

November 4, 2024

Migrating to the new permissions model

Starting with December 9, 2024, at the earliest, we will replace the current break inheritance model with the union of privileges permissions model on Community. The change will happen automatically, and no further action is required from your side.

The new model improves the access control across all users. As a result, each time you add or remove a privilege to or from a group, all users who are part of that group will start passing that privilege check.

This change impacts the following set of privileges:

• Paramètres du profil d’interface utilisateur (aucun accès à l’interface utilisateur, espace de travail personnel uniquement, interface standard)
• Mettre à jour les paramètres de politique
• Permettre à l'utilisateur d'exécuter des automatisations
• Créer des espaces de travail personnels pour cet utilisateur

Moreover, early in 2025, we will also enable the feature on Enterprise. For more details, check the Upcoming deprecations page.

Retention policy updates

We know that streamlining your database is as important to you as it is for us. This is why we are taking our retention policies up a notch by adding the option to delete or archive non-terminal state jobs and queue items.

This new option is integrated in the existing retention policy component at the process level for jobs, and at the queue level for queue items. It is available via a new set of fields dedicated to uncompleted jobs and queue items, respectively.

The default values for jobs and queue items are as follows:

• Terminé
  • The default duration is 30 days.
  • The maximum duration is 180 days.
• Uncompleted
  • The default duration is 180 days.
  • The maximum duration is 540 days.

Important: These defaults will be applied automatically starting in 4 months' time. Until then, you can change them as needed to suit your particular scenario.

You can find out more about this in Process data retention policy and Queue item retention policy.

HashiCorp Vault improvements

The HashiCorp Vault and HashiCorp Vault (read only) credential stores are now enhanced with the new and optional Authentication Mount Path field. This allows you to specify a custom mount path, and mount the same authentication method with two different configurations, on two distinct paths.

In addition, the HashiCorp Vault (read only) credential store now supports the LDAP secrets engine, which merges both Active Directory and OpenLDAP secrets engines.

Removing the password complexity sync to Identity

Password complexity settings are no longer syncronized between Orchestrator and Identity Server. To edit the settings, use the Identity Server APIs or the Admin Portal user interface.

Removing the ToggleOrganizationUnit endpoint

The POST/odata/Users({key})/UiPath.Server.Configuration.OData.ToggleOrganizationUnit endpoint, exclusively relevant in a classic folder context, is now removed.

Résolution de bogues

• An error message was displayed when you attempted to upload packages with large release notes.
• When you rapidly switched between tenants before the page fully loaded, the URL and page remained unsynchronized. This action caused Orchestrator to still display the initial tenant.