Welcome
Administration
Learn about how to configure, manage, and maintain HCL Detect environments. It includes details on system setup, user management, and permissions, ensuring seamless operation and efficient deployment of your continuous delivery processes.
Feed Parser Mapping
Use CLI commands to define and maintain feed parser mappings between incoming feed fields and Detect target attributes.
Feed Parsers for CDP and Custom Kafka Feeds
Feed parsers prepare incoming Kafka data for processing by Detect.

Getting Started
Welcome to the documentation for HCL Detect, where you can find information about how to install, maintain, and use this service.
Installation
Learn more about HCL Detect installation and deploying core components of the product.
Administration
Learn about how to configure, manage, and maintain HCL Detect environments. It includes details on system setup, user management, and permissions, ensuring seamless operation and efficient deployment of your continuous delivery processes.
- Introduction
  Use this guide to administer HCL Detect, including user and role access, CLI-based configuration and management tasks, DEL reference topics, and support resources.
- User & Role Management
  This page explains how to manage roles and permission in HCL Detect.
- Configuration Management
  Use CLI commands to query and validate the infrastructure settings required for Detect operations.
- Metadata Management
  Use CLI commands to discover data sources, search tables, and retrieve column metadata for Detect integrations.
- Profile Management
  Manage profile definitions and attributes through the HCL Detect UI or CLI.
- Feed Application
  Create and manage feed applications through the HCL Detect UI or CLI.
- About derived attribute functions
  Derived attribute functions enable you to offload complex calculations involving multiple tuple attributes to custom Python scripts.
- Feed Parser Mapping
  Use CLI commands to define and maintain feed parser mappings between incoming feed fields and Detect target attributes.
  - Checklist
  - Feed Parsers for CDP and Custom Kafka Feeds
    Feed parsers prepare incoming Kafka data for processing by Detect.
  - Engine Notification
  - FeedParserMappingDto overview
  - Important mapping rules
  - Supported targetAttributeType values
  - Supported commands
  - Command examples
  - Controller vs CLI notes
  - Troubleshooting
- Destination Management
  Use CLI commands to configure, validate, and manage destination endpoints for Detect event delivery.
- Crypto Management
  Use CLI crypto utilities to encrypt and decrypt sensitive values used in Detect configuration workflows.
- Troubleshooting & Common Errors
- Detect Expression Language
- Detect Expression Language Built-in Functions
Working with the System
The section provides comprehensive instructions for creating, configuring, and managing marketing events. It covers topics such as defining audience conditions, setting up triggers, deploying events, and tracking their performance. Additionally, this section includes explanations of key terminology and offers advanced options to optimize event management.
System Data Model
This section provides detailed information about the internal tables used within the Detect module. It includes descriptions of each table's structure, purpose, and relationships, aiding administrators and developers in understanding and managing the underlying database schema effectively.

Feed Parsers for CDP and Custom Kafka Feeds

Feed parsers prepare incoming Kafka data for processing by Detect.

Custom Parser Mapping

Custom Parser: Use customer-specific .jar files to automatically map Kafka stream attributes.
Parser Location: Place the custom parser .jar file in:
```
<DETECT_HOME>/plugins/feed-parsers
```
Automatic Mapping: Detect loads the parser and applies the defined attribute mappings during feed processing.

CDP Parser

Internal Custom Parser: Parses attributes received from CDP over Kafka.
Attribute Mapping: Maps incoming CDP data to Detect attributes.
Data Filtering: Omits unnecessary initial data before processing in Detect.
Purpose: Ensures clean and relevant CDP data is available for Detect processing.