- Introducción
- Primeros pasos
- Modelado de procesos con BPMN
- Comprender el modelado del proceso
- Abrir el lienzo de modelado
- Modelar tu proceso
- Alinear y conectar elementos BPMN
- Autopilot para Maestro (vista previa)
- Repositorio de procesos
- Modelado de procesos con Gestión de casos
- Diseñar un esquema de entidad de caso persistente
- Definición de claves de caso (sistema frente a externo)
- Establecimiento de contratos de E/S de tareas y reescritura
- Reglas de salida y terminación temprana
- Modelado de etapas primarias y secundarias
- Desencadenar un caso desde Data Fabric
- Implementar personas y permisos a nivel de etapa
- Establecer SLA y reglas de escalada automatizadas
- Configurar un bucle de revisión (reingreso)
- Gestionar instancias de casos activos: pausar, migrar y reintentar
- Diccionario de componentes de gestión de casos de Maestro
- Process modeling with Flow
- Primeros pasos
- Conceptos básicos
- Node reference
- Build guides
- Mejores prácticas
- Referencia
- Implementación del proceso
- Depuración
- Simular
- Publicar y actualizar procesos de agente
- Escenarios de implementación comunes
- Extracción y validación de documentos
- Operaciones de proceso
- Supervisión de procesos
- Optimización de procesos
- Información de referencia
Guía del usuario de Maestro
Transforms data using a variety of operations. The Data Transform node and its individual operation nodes (Filter, Map, Group By) are available as separate selectable nodes in the node palette.
When to use Data Transform vs Script
Use Data Transform operations when the transformation is a field-level operation on a collection. The available operations cover:
- Filtrar
- Asignación
- Agrupación
Use Script when the transformation requires conditional logic, arithmetic, or string manipulation, or when no dedicated operation covers the case. Both can be combined: a Data Transform operation can filter or reshape a collection, then pass the result to a Script node.
Salida
All Data Transform operation nodes output their result as output, accessible downstream as $vars.<nodeName>.output.
Filtro
Keeps only the entries in a collection that match your conditions.
Configuración
| Campo | Obligatorio | Descripción |
|---|---|---|
| Entrada | Sí | The collection (array) to filter. Reference as $vars.<nodeName>.output. |
| Condiciones | Sí | One or more conditions. An entry is kept only if all conditions are met. |
Ejemplo
Keep only orders with a status of "completed":
- Entrada:
$vars.fetchOrders1.output.body - Condition:
statusequalscompleted
Output available as $vars.filter1.output.
Mapa
Transforms each entry in a collection by modifying or reshaping its fields.
Configuración
| Campo | Obligatorio | Descripción |
|---|---|---|
| Entrada | Sí | The collection (array) to transform. |
| Field mappings | Sí | For each target field, define the name and the source field or expression. |
Ejemplo
Rename firstName and lastName fields to first and last:
| Target field | Source mapping |
|---|---|
first | firstName |
last | lastName |
Output available as $vars.map1.output.
Group By
Groups a collection by a shared field and aggregates values like totals, averages, or counts.
Configuración
| Campo | Obligatorio | Descripción |
|---|---|---|
| Entrada | Sí | The collection (array) to group. |
| Group by field | Sí | The field whose value determines the group. |
| Aggregations | No | Additional computed fields per group (count, sum, average, min, max, first, last, collect). |
Ejemplo
Group a list of orders by region and count the number of orders per region:
- Entrada:
$vars.fetchOrders1.output.body - Group by:
region - Aggregation:
orderCount= count
Output available as $vars.groupBy1.output.
Problemas comunes
| Incidencia | Resolución |
|---|---|
| Output is empty after Filter | The conditions don't match any entries. Inspect the input collection in the execution trace to verify the field names and values. |
Map output has undefined fields | The source field path doesn't exist in the input entries. Use the execution trace to confirm the input structure. |