maestro
latest
false
Maestro Orchestrate user guide
- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- 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)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Mock
The Mock node is a placeholder that passes the run on without doing anything while a workflow is being sketched.
A placeholder node with no behavior. Use it to sketch the shape of a workflow before implementing the actual logic. It passes the run on to the next node without doing anything, and produces no output.
When to use Mock
- Modeling: rough out the structure of a complex workflow before connecting real nodes.
- Stubbing: hold a position in the workflow where a node will be added later without breaking the structure of the workflow.
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. The nodes after a Mock node cannot reference any output from it.
Notes
- A Mock node that is wired into the workflow will execute (passing control to the next node) but does nothing.
- Replace Mock nodes before you deploy a workflow.
Next steps
- Output mocking: returning a fixed output from a real node during a debug run.
- Script: returning a hardcoded value.