Home
Design Server
The documentation provided here describes how to use the Design Server.
Flows
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.
Flows
This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
Listener
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.

Design Server
The documentation provided here describes how to use the Design Server.
- Projects
  This documentation describes Design Server projects.
- Schemas
- Maps
- Flows
  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.
  - Flows
    This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
    - Nodes
    - Terminals
    - Flow terminals
    - Scheduled flows
    - Listener
      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.
      - Listener example
        The Listener example provides a demonstration of usage and behavior of the Listener as used in a flow.
    - Flow audits
      Flow audits are a way to retrieve more verbose information about a flow instance.
    - Flow variables
      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.
- Using Design Server
  How to use the HCL Link Design Server.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
- Schema designer
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.

Listener

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.

When a package is deployed with a flow that has a Watch, the Flow Engine's File Listener is started to monitor for files that match the map's input file definition.

You can use wildcards in the file adapter's filename so the File Listener will start a flow instance with each file that matches the pattern defined for the filename.

After it is deployed, the flow will run an instance when a file that matches the configured pattern of the filename appears in the trigger directory. The trigger is the directory defined for the map's input.

If a wildcard is used in the definition of the filename, the system flow variable "_WILDCARD_" will be assigned the value of the wildcard for that flow instance. The value can then be retrieved throughout the flow instance. For a complete demonstration, see the Listener example.

See the Listener example for a demonstration of how to use the Listener. The Listener example contains a readme file that contains detailed instructions about how to run the example.