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
Success Action

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
    - 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.

Success Action

The Success Action setting specifies the location of the source data when a map, a burst, or a card successfully completes. The availability of the Success Action setting is adapter-specific.

The Success Action setting works with the Transaction Scope setting, which defines when to apply the action specified with the Success Action setting.

Value: Description
Keep: The input data should not be removed from its source.
For example, if the input is a messaging adapter, and the map successfully completes, do not remove the messages from the message queue.
Keep Unless Empty: The input data should not be removed unless it has no content.
For example, if the input is a file, and the map completes successfully, but the input file had no data (it was empty), delete the input file. Otherwise, keep the input file.
Delete: Delete the input data or remove it from its source.
For example, if the map completes successfully, remove the messages from the message queue.