Home
Projects
A project is a container for HCL Link artifacts.
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.

Projects
A project is a container for HCL Link artifacts.
- Flows
  This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
  - Nodes
  - Terminals
  - Flow terminals
    Flow terminals represent the inputs and outputs to a flow. Every node has input and/or ouptut terminals.
  - Scheduled flows
    This documentation describes the options for defining the flow schedule.
  - 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.
  - Create a flow
    Steps required to create a flow.
  - Running flows in the Designer
    When you develop a flow in the Flow Designer you can run the flow directly from the Designer either in Link, or on a different runtime environment.
- Maps
  Maps define input and output specifications and mapping rules for data transformation.
- Schemas
  Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
- Connections and Actions
  This documentation describes connections and actions.
- Files
  Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.

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.