Diseñar y modelar — Process Orchestrator

In development ·

How process steps, decisions, gateways, and connectors become explicit.

En desarrollo

This page describes Process Orchestrator product direction. Exact functionality may change before release.

Traducción en curso

La navegación y el resumen de la página están en español. El contenido técnico de esta página permanece temporalmente en inglés y se traducirá de forma gradual.

The modeler direction uses recognizable building blocks such as start, task, user task, decision, gateway, subprocess, end, and connector. The purpose is not to reproduce technical architecture diagrams. It is to show the process as the organization experiences it.

Intended value

business logic becomes visible instead of being hidden in scripts;
parallel work, decisions, and dependencies can be understood without reading code;
reusable components and validation help keep models consistent;
versions make controlled change possible;
integrations become part of the flow rather than separate technical projects.

A process should be understandable by business, operations, and IT while remaining precise enough for controlled execution.

View the current version in the wiki