Home | Table of Contents | Success | CloverETL 4.6.1
--- | --- | ---
Prev | Job Control | Next

## Success

# Not available in Community Designer

Short Description
Ports
Success Attributes
Details
See also

### Short Description

Success is a successful endpoint in a jobflow

Component | Data output | Input ports | Output ports | Transformation | Transf. required | Java | CTL | Auto-propagated metadata
--- | --- | --- | --- | --- | --- | --- | --- | ---
Success | none | 0-1 | 0 |  |  |  |  |

### Abstract

Success is a successful endpoint in a jobflow. Tokens that flow into the component are not processed anymore - they are considered to be successfully processed within the jobflow. The component can serve as a visual marker of success in a jobflow.

The component can log a message and set contents of dictionary - it is similar to the Fail component.

### Icon

### Ports

Port type | Number | Required | Description | Metadata
--- | --- | --- | --- | ---
Input | 0-1 |  | For received tokens | Any

### Success Attributes

Attribute | Req | Description | Possible values
--- | --- | --- | ---
Basic
Message | no | Text message to log for each incoming token. | text
Mapping | no | Mapping is used for dynamical assembling of log message. Moreover, dictionary content can be changed as well. See Details. |

### Details

##### Mapping details

Mapping in Success component is generally used for two purposes:

- Assembling of log message from incoming record.

- Populating dictionary content from incoming record.

  | Note
  Only output dictionary entries can be changed.

Log message compiled by the mapping has the highest priority. If the mapping does not set 'message', the message from component attribute is used instead. If no message is set via attribute or mapping, nothing is logged.

### See also

Common Properties of Components
Specific Attribute Types
Common Properties of Job Control

Prev | Up | Next
Subgraph | Home | Table of Contents | TokenGather