Rule Details

1. Duplicate Detection Basic Rules

1.1 Enterprise Type Detection Rules

Production Environment

• Primary Attribute: Case-insensitive
• Regular Text: Case-sensitive
• Lookup Relationship: Case-insensitive

Sandbox Environment

• Primary Attribute:
  • Exact match: Case-sensitive
  • Fuzzy match: Case-insensitive
• Regular Text:
  • Exact match: Case-sensitive
  • Fuzzy match: Case-insensitive
• Lookup Relationship:
  • Exact match: Case-sensitive

1.2 Special Character Handling

• Primary Attribute Detection: Filters all special symbols including: ~!@#$%^&*()+=|{}':;',[].<>/?~！@#￥%……&*（）——+|{}【】《》「」'；：""'。，、？
• Punctuation: Cannot be used as distinguishing criteria in primary attributes

1.3 Mobile Number Processing Rules

• Parentheses in phone numbers are converted to spaces
• The system splits numbers into segments using spaces as delimiters
• A match in any segment will be flagged as duplicate
• Recommended Solution: Use hyphens “-“ instead of parentheses

2. Duplicate Detection Configuration

2.1 Data Scope Settings

• Supports custom data ranges for detection (default includes invalidated data)
• Users can configure the scope to exclude invalidated data from detection
• Only existing data meeting the criteria will participate in detection
• Non-qualifying data won’t be flagged as duplicates even if matched

2.2 Trigger Conditions

• Supports multiple detection rules
• Detection only triggers when new/modified fields meet preset conditions
• Operations not meeting trigger conditions won’t initiate detection

2.3 Detection Blocking Rules

• System won’t enforce blocking when rules include fuzzy matching
• Users can choose whether to ignore detection results and proceed with saving

3. Special Detection Scenarios

3.1 Combined Detection

• Conditions are fixed configurations (non-customizable)
• Field mapping relationships are visible via UI prompts
• Requires valid detection rules to take effect
• Operates independently with dedicated rules unaffected by general settings
• Uses exact matching with OR logic (any condition match flags as duplicate)

3.2 Fuzzy Detection Rules

Matching rules vary by keyword length: 1. <6 characters: - 100% match based on ES tokenization 2. 6-9 characters: - Allows up to 25% token mismatch via ES tokenization 3. >9 characters: - Requires 75% token match via ES tokenization

3.3 Null Value Handling

Three configuration options: 1. Match Nulls: Empty new data fields match existing null values as duplicates 2. Ignore Nulls: Empty new data fields don’t match existing null values 3. Exclude Nulls: Empty fields don’t participate in detection

4. Common Issue Resolution

4.1 Rule Activation Time

• Rules don’t take effect immediately after configuration
• Requires backend data refresh into ES
• Activation time depends on data volume
• Rule modifications are prohibited during data refresh

4.2 Special Scenario Notes

• Lead Conversion: No detection validation (controlled separately in Admin Console)
• Master-Sub-object Creation: Sub-object doesn’t support detection
• Simultaneous Account & Contact Creation: Detection rules don’t apply

4.3 Quick Detection Tool Usage

• Single input box matches all backend-configured detection rules
• Pure numeric inputs only match phone/telephone fields
• Non-numeric inputs match text/URL/email fields