maestro
latest
false
- Introduction
- Getting started
- Process modeling with BPMN
- Process modeling with Case Management
- Designing a persistent case entity schema
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Managing live case instances: pause, migrate, and retry
- Maestro case management component dictionary
- Process modeling with Flow
- Getting started
- Core concepts
- Node reference
- Build guides
- Best practices
- Reference
- Process implementation
- Debugging
- Simulating
- Publishing and upgrading agentic processes
- Common implementation scenarios
- Extracting and validating documents
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
A placeholder node with no behavior. Use it to sketch the shape of a flow before implementing the actual logic — it passes through execution without doing anything and produces no output.
When to use Mock
- Modeling: Rough out the structure of a complex flow before wiring in real nodes.
- Stubbing: Hold a position in the flow where a node will be added later without breaking the flow's structure.
The Mock node is not intended for output simulation. To return a fixed value during testing without calling an external service, use a Script node that returns a hardcoded value.
Configuration
The Mock node has no configuration fields.
Output
The Mock node produces no output. Downstream nodes cannot reference any output from a Mock node.
Notes
- A Mock node that is wired into the flow will execute (passing control to the next node) but does nothing.
- Mock nodes should be replaced before publishing a flow to production.