Home
Projects
A project is a container for HCL Link artifacts.
Maps
Maps define input and output specifications and mapping rules for data transformation.
Card settings
Input card settings
Transaction Scope
Fetch As and Scope actions

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.
- Maps
  Maps define input and output specifications and mapping rules for data transformation.
  - Using Maps
  - Create maps to specify sources and targets
  - Maps and map source files
    Basic tasks involved in creating and managing maps.
  - Input and output cards
  - Card settings
    - Schema
    - Input card settings
      - Input data retrieval
      - WorkArea
      - Fetch Unit
      - Connection
      - Command Line
      - Action properties
        Each adapter defines a set of properties that are configured to specify the source of the data for the input card.
      - Transaction settings
      - Success Action
      - Failure Action
      - Transaction Scope
        Fetch As and Scope actions
    - Output card settings
    - Input and output card settings
    - Effects of modifying a schema
    - Changing a type that is used for a card
    - SyntaxCard
      The SyntaxCard setting defines the output card as a syntax card.
    - Editing a card
  - Map rules
  - Formulating map rules
  - Functional map basics
  - Map settings
  - Configuring bursts
  - Building maps
  - Running a map
  - Managing invalid data
  - Map audit overview
  - Troubleshooting
  - Error and warning messages
- 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.

Fetch As and Scope actions

The Fetch As setting and the Scope setting affect when a Success Action or Failure Action occurs.

If an input Fetch As setting is Integral, any failure action causes the entire map to fail.

Table 1. Effect of Scope setting when Fetch As setting is Integral
A two-column table. Column 1 is the Scope setting. Column 2 explains when the OnSuccess or OnFailure action occurs.
Scope	Action specified by Success Action or Failure Action setting occurs:
Map	After all bursts
Burst	After each burst
Card	After input validation for that input for each burst

Table 2. Effect of Scope setting when Fetch As setting is Burst
A two-column table. Column 1 is the Scope setting. Column 2 explains when the OnSuccess or OnFailure action occurs.
Scope	Action specified by Success Action or Failure Action setting occurs:
Map	After all bursts
Burst	After the first burst
Card	After input validation for that input for the first burst