A project is a container for HCL Link artifacts.
This documentation describes how Flows can be run from REST API, listeners, or they can be scheduled.
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 report the node log in json format. Information about node terminals and the data size is provided for all nodes.
Flow terminals represent the inputs and outputs to a flow. Every node has input and/or ouptut terminals.
This documentation describes the options for defining the flow schedule.
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.
Steps required to create a flow.
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 define input and output specifications and mapping rules for data transformation.
Use the schema designer to define, modify, and view schemas. A schema describes the syntax, structure, and semantics of your data.
This documentation describes connections and actions.
Files are used in various places within HCL Link. HCL Link allows files to be uploaded to the HCL Linkserver.
Have feedback?Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.