maestro
latest
false
Guía del usuario de Maestro
- Introducción
- Primeros pasos
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Abrir el lienzo de modelado
- Modelar tu proceso
- Alinear y conectar elementos BPMN
- Autopilot para Maestro (vista previa)
- Repositorio de procesos
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Depuración
- Simular
- Escenarios de implementación comunes
- Building with Maestro Case
- Introducción a Maestro Case
- Maestro BPMN frente a Maestro Case: cuándo utilizar la gestión de casos
- El ciclo de vida de Maestro Case: del desencadenador de eventos a la experiencia de la aplicación
- Build your first case with Maestro Case
- Definir claves de caso (de sistema o externo)
- Establecer contratos de entrada/salida y de escritura diferida de tareas
- Reglas de salida y terminación temprana de etapas
- Modelar las etapas principal y secundaria
- Iniciar un caso desde Data Fabric
- Implementar perfiles y permisos a nivel de etapa
- Establecer SLA y reglas de escalado automatizadas
- Configurar un bucle de reprocesamiento (reingreso)
- Contrato de entrada y salida del gestor de casos
- Maestro Case component dictionary
- Building with Maestro Flow
- Integraciones
- Operating
- Supervisión
- Optimizing
- Información de referencia
Importante :
La localización de contenidos recién publicados puede tardar entre una y dos semanas en estar disponible.
How Maestro BPMN, Maestro Case, and Maestro Flow share one runtime, one deployment model, and one set of operating, monitoring, and optimization services.
One platform, three canvases
Maestro BPMN, Maestro Case, and Maestro Flow are three ways to build on the same orchestration platform, not three separate products. Whichever canvas you build with, your process shares the same deployment target, the same instance management surface, and the same monitoring and optimization tools.
The stack
| Capa | Lo que hace | Where each canvas fits |
|---|---|---|
| Authoring | Where you build the process definition. | Maestro BPMN, Maestro Case, and Maestro Flow each provide a visual canvas in Studio Web. Maestro Flow also builds in VS Code. |
| Execution engine | Runs process instances and evaluates transition logic. | Maestro BPMN and Maestro Flow run on the same Maestro engine. Maestro Case runs on the Case Manager, which evaluates CMMN-style rules and falls back to agent reasoning when no rule matches. |
| Implementación | Publishes a process definition so it can run. | All three publish to Orchestrator and are versioned the same way. |
| Runtime services | Cross-cutting services every running instance uses regardless of canvas. | Instance management, monitoring dashboards, alerts, and process optimization apply the same way to a BPMN process, a case, or a flow. |
| Business-user surface | Where non-technical users interact with running work. | BPMN and Flow surface through Action Center and Orchestrator; Case surfaces through the Case App. |
Por qué es importante
A process built with one canvas can call a process built with another: a case can invoke a BPMN process as a task, and a Flow can call a BPMN subprocess. Because they share the same runtime and deployment model, this composition doesn't require any translation layer.
Páginas relacionadas
- Choosing a Maestro canvas — which canvas fits your use case
- The Maestro Case lifecycle — a deeper look at how the Case Manager layer works
- Ways to build with Maestro — Studio Web, VS Code, and coding-agent support per canvas