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.
Profile Management
Use CLI commands to create, update, query, and delete profile definitions used by Detect.
Important Profile Rules

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
  Use CLI commands to create, update, query, and delete profile definitions used by Detect.
- Feed Application
  Use CLI commands to create and manage feed applications, including filtering and troubleshooting scenarios.
- Feed Parser Mapping
  Use CLI commands to define and maintain feed parser mappings between incoming feed fields and Detect target attributes.
- 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
- Support & Contact Information
- 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.

Important Profile Rules

The following rules are enforced during profile create/update operations:

The very first profile in the system must be a master profile only.
- If no master profile exists yet, the first profile must be created with:
```
"isMasterProfile": true
```
If no master profile has been created, you cannot create any other profiles at all.
- Detect rejects creation of any non-master profile until a master profile exists.
Each profile must have exactly one profile table in the current implementation.
- Multiple profile tables are not supported in the current release.
Each profile must have one master table.
- Since only one profile table is currently supported, that table must be master table. Use following configuration:
```
"isMasterTable": true
```
Each profile table must have attribute-column mappings.
- attributeColumnMappings must not be empty.
Each profile table must have exactly one key attribute mapping.
- Exactly one entry in attributeColumnMappings must have:
```
"isKeyAttribute": true
```
Master profile update restrictions apply.
- If the existing profile is already the master profile:
- isMasterProfile cannot be changed from true to false
- the profile table cannot be removed
- dataSourceName cannot be changed
- dbTableName cannot be changed
- existing master-table attribute mappings cannot be removed or altered incompatibly