- Notas relacionadas
- 2.2510.1
- 2.2510.0-patch2
- Antes de empezar
- Gestionar el acceso
- Primeros pasos
- Integraciones
- Trabajar con apps de proceso
- Trabajar con paneles y diagramas
- Trabajar con diagramas de proceso
- Trabajar con modelos de proceso Descubrir e Importar modelos BPMN
- Showing or hiding the menu
- Información del contexto
- Exportar
- Filtros
- Envío de ideas de automatización a UiPath® Automation Hub
- Etiquetas
- Fechas límite
- Comparar
- Comprobación de conformidad
- Análisis de causa raíz
- Simular el potencial de automatización
- Triggering an automation from a process app
- Ver datos del proceso
- Creación de aplicaciones
- Cargar datos
- Transforming data
- Structure of transformations
- Tips for writing SQL
- Exportar e importar transformaciones
- Ver los registros de ejecución de datos
- Combinar registros de eventos
- Configuración de etiquetas
- Configurar fechas de vencimiento
- Configurar campos para el potencial de automatización
- Configuración de actividad: definición del orden de actividad
- Hacer que las transformaciones estén disponibles en los paneles
- Modelos de datos
- Añadir y editar procesos
- Personalizar paneles
- Publicar paneles
- Plantillas de la aplicación
- Notificaciones
- Recursos adicionales
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.