The documentation provided here describes how to use the Design Server.
A flow node invokes a sub flow within a flow. Sub-flows need not be wired to other nodes; it is valid to have a flow that is comprised of multiple sub-flows that each have listeners.
This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
This documentation describes Design Server projects.
An error terminal is used on a node for cases where the error can be caught with another node, preventing the flow from failing. An error terminal will only run a node if the node that has the error terminal is the initial cause of the error.
Log terminals, like Error and Success terminals, can be enabled on any node and are output terminals only.
A Flow that has a Map node as its first node, and uses a File adapter for an input, can enable that node's input to be a Watch.
Flow audits are a way to retrieve more verbose information about a flow instance.
Flow Variables are process data variables that go along with the flow execution, accessible to all nodes in the flow while it is being executed under flow executor/engine context.
How to use the HCL Link Design Server.
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.