- Versionshinweise
- 2.2510.1
- 2.2510.0-patch2
- Bevor Sie beginnen
- Verwalten des Zugriffs
- Erste Schritte
- Integrationen
- Arbeiten mit Prozess-Apps
- Arbeiten mit Dashboards und Diagrammen
- Arbeiten mit Prozessdiagrammen
- Arbeiten mit Discover-Prozessmodellen und Import BPMN-Modellen
- Showing or hiding the menu
- Kontextinformationen
- Exportieren
- Filter
- Senden von Automatisierungsideen an den UiPath® Automation Hub
- Tags
- Fälligkeitsdaten
- Vergleichen
- Konformitätsprüfung
- Ursachenanalyse
- Simulation des Automatisierungspotenzials
- Auslösen einer Automatisierung über eine Prozess-App
- Anzeigen von Prozessdaten
- Erstellen von Apps
- Laden von Daten
- Transforming data
- Structure of transformations
- Tips for writing SQL
- Exportieren und Importieren von Transformationen
- Anzeigen der Datenausführungsprotokolle
- Zusammenführen von Ereignisprotokollen
- Konfigurieren von Tags
- Konfigurieren von Fälligkeitsdaten
- Konfigurieren von Feldern für das Automatisierungspotenzial
- Aktivitätskonfiguration: Definieren der Aktivitätsreihenfolge
- Verfügbarmachen der Transformationen in Dashboards
- Datenmodelle
- Hinzufügen und Bearbeiten von Prozessen
- Anpassen von Dashboards
- Dashboards veröffentlichen
- App-Vorlagen
- Benachrichtigungen
- Zusätzliche Ressourcen

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.