2.2510.2

2.2510.2 release notes for Solutions Management in Automation Suite.

Date de publication : 15 avril 2026

Activation strategy option when deploying solutions

A new Activation strategy option is now available when deploying a solution. This lets you choose whether to activate the deployment immediately or at a later time:

• Now: The solution is automatically activated right after deployment.
• Later: You can review the solution and activate it yourself when ready.

Pour plus d'informations, consultez Déployer une solution.

Expérience de déploiement de solutions simplifiée

We redesigned the Solutions deployment experience to make the process clearer, more consistent, and easier to use. The previous modal-based deployment flow is replaced with a dedicated Deploy a solution page that offers improved navigation, better visibility of deployment options, and a more intuitive structure.

Pour plus d'informations, consultez Déployer une solution.

Nouveautés

Déploiements est désormais l’onglet par défaut

L’onglet Déploiements constitue désormais la vue d’arrivée par défaut dans la zone Solutions, ce qui facilite l’accès aux actions de déploiement et permet de suivre les déploiements existants.

Nouveau flux de déploiement de page

L'ancien modal de déploiement a été remplacé par une page dédiée, offrant plus d'espace, un regroupement des paramètres plus clair et un accès plus facile aux options de configuration avancées.

Points d’entrée de déploiement améliorés

You can now start a deployment from multiple surfaces:

• + Déployer dans l'onglet Déploiements .
• le bouton Déployer dans une ligne de package de l’onglet Packages .
• Plus d’actions → Déployer le menu pour n’importe quelle version du package.

Nouveaux comportements par défaut

• Activation strategy now defaults to Now: Deployments automatically activate the solution and its triggers unless you switch to Later.
• Deployment location now defaults to Install as root folder: The solution is installed as a new root folder under the tenant by default, simplifying organization and ensuring clean isolation of solution artifacts.

Workflow simplifié pour la configuration de l'activation

Nous avons amélioré l’expérience d’activation pour les déploiements de solutions en affinant la représentation et la validation des déploiements inactifs. Les déploiements inactifs sont désormais distincts en fonction de la disponibilité de l'activation :

• Inactive (Needs setup to activate): The deployment requires additional configuration before it can be activated, such as authenticating a packaged connection.
• Inactive (Ready to activate): The deployment meets all activation requirements and can be activated directly.

Activation validation is now evaluated closer to activation time, ensuring required steps are surfaced and enforced before activation can complete. This reduces manual trial-and-error during deployment activation.

For more information, see Checking the deployment status.

Barre latérale des packages pour les packages de solutions

A new Package sidebar is now available in the Solutions experience, making it easier to explore package details and manage deployments without leaving the Packages page.

When you select a solution package on the Packages tab, a contextual sidebar displays all published versions of the selected package and all deployments associated with that package. You can switch between the Versions and Deployments tabs, start a new deployment directly from the sidebar, and inspect package status, version history, and deployment state without navigating away.

For more information, see Navigating the Package sidebar.

Nettoyage automatique des déploiements de débogage de solution

Solution debug deployments are now automatically uninstalled after 30 days of inactivity. Automatic uninstallation removes all resources created by the deployment and the associated solution folder. This process is managed by Solutions and cannot be configured or disabled.

For more information, see Retention and automatic cleanup of solution debug deployments.

Expérience utilisateur améliorée dans l’onglet Déploiements

Nous avons simplifié l’expérience de déploiement afin de réduire l’encombrement visuel et rendre les actions courantes plus faciles à trouver.

Les principales modifications comprennent :

• A single Version column now replaces the previous Now version and Current version columns. If multiple versions apply, previous and current versions appear in the same column.
• The Status column now displays plain text values (for example, Successful, Draft, Failed).
• Les noms des colonnes ont été mis à jour pour plus de clarté : Dernière opération, Statut, Commencé et Terminé ont été renommés en Dernière opération, Statut de l'opération, Opération démarrée, et Opération terminée.
• Columns were reordered to better reflect their relationships. Activated and Version are now positioned closer to Name, while Operation status and Operation started follow Last operation.
• The Operation ended and Package name columns are hidden by default and can be enabled via the Visible Columns control.
• A new Location column shows the folder path where each solution is deployed.
• You can filter deployments by multiple status values simultaneously.
• When a new package version is available for a deployment, an Upgrade icon appears inline so you can upgrade directly from the table.
• Two new activation statuses are introduced: Inactive (Needs setup to activate) and Inactive (Ready to activate).
• For Draft deployments, the Actions menu now includes both the standard draft actions and the actions associated with the previous operation, making it easier to recover from failed or interrupted operations.
• You can now create a deployment from the folder context menu (Actions > Add > Solution Deployment) or by selecting Deploy on the Orchestrator homepage.

For more information, see Checking the deployment status.

Résolution de bogues

We fixed an issue where validation errors for Assets were not surfaced during solution deployment when required fields were missing. The system now correctly marks such cases with requiresConfiguration: true, ensuring the error is displayed and enabling field-level navigation to guide users to the missing configuration.