- Notes de publication
- 2.2510.1
- 2.2510.0-patch2
- Avant de commencer
- Gestion de l’accès
- Démarrage
- Intégrations
- Travailler avec des applications de processus
- Travailler avec des tableaux de bord et des graphiques
- Travailler avec des graphiques de processus
- Travailler avec des modèles de processus Découvrir et importer des modèles BPMN
- Showing or hiding the menu
- Informations contextuelles
- Exporter (Export)
- Filtres
- Envoi d’idées d’automatisation au Automation Hub d’UiPath®
- Balises
- Dates d’échéance
- Comparer
- Vérification de la conformité
- Analyse des causes profondes
- Simulation du potentiel d’automatisation
- Triggering an automation from a process app
- Afficher les données de processus
- Création d'applications
- Chargement des données
- Transforming data
- Structure of transformations
- Tips for writing SQL
- Exportation et importation de transformations
- Afficher les journaux d'exécution des données
- Fusion des journaux d'événements
- Configuration des balises
- Configuration des dates d'échéance
- Configuration des champs pour le potentiel d'automatisation
- Configuration des activités : Définition de l'ordre des activités
- Rendre les transformations disponibles dans les tableaux de bord
- Modèles de données
- Ajouter et modifier des processus
- Personnaliser les tableaux de bord
- Publication des tableaux de bord
- Modèles d'applications
- Notifications
- Ressources supplémentaires
Process Mining
Release date: March 16, 2026
This patch resolves issues affecting data loading and application editing in Process Mining deployments with large datasets.
Uploading data failed for applications with a large number of columns. During data operations, Process Mining queries the database to retrieve column names and data types. For applications with many columns, the resulting output exceeded the 8,000-character limit in Microsoft SQL Server, which caused the upload to fail with a SQL error. Process Mining now handles large column sets correctly and data uploads succeed as expected.
Applications with more than 500 fields could no longer be edited. Process Mining enforces a 500-field limit per application. During the initial run, the system automatically added newly discovered fields. Incorrect field counting allowed the total to exceed the limit, after which the application could not be saved or edited. Field counting now works correctly, and applications remain editable within the defined limit.
Data refreshes after the initial CDATA ingestion did not load new data into the ELT editor or dashboards, with no error reported. When the data mapping was unchanged between ingestions, an incorrect check bypassed the mapping execution step for CDATA tables, which write directly to the database rather than through blob storage. As a result, subsequent ingestions appeared to complete successfully but continued to display data from the initial ingestion. The check is now corrected, and CDATA data refreshes load updated data as expected.