"1. Source System Component"

1.1 Polling Frequency Settings

When selecting the “Query” method to periodically fetch third-party data, you need to configure the polling frequency for “Batch Queries.”

picture coming soon:

Method 1: Basic Configuration

For simple polling scenarios, use the point-and-select configuration:

1. Daily polling every 10 minutes between 7:00 AM and 11:00 PM:
   picture coming soon:
   Execution times: 7:00, 7:10, 7:20… up to 22:50 daily.
   Note: Similar logic applies to hourly queries (e.g., every 2 hours).

2. Single daily query at 11:00 PM:
   picture coming soon:

3. Weekly query every Monday at 11:00 PM:
   picture coming soon:
   Supports multi-select for days (Monday–Sunday).

4. Monthly query on the 2nd day at 11:00 PM:
   picture coming soon:
   Supports multi-select for days (1st–31st).

Method 2: Advanced Cron Expressions

For custom polling frequencies, use Cron expressions:
picture coming soon:

Cron Syntax

A Cron expression is a string separated by spaces, structured as:
Minutes Hours Day Month DayOfWeek

Constraints:
- The Integration Platform restricts polling to minute-level granularity (no seconds) and annual maximums (no year field).
- Validation: Minute values cannot exceed 10 enumerations.

Special Characters:

1. *: Matches any value (e.g., * in Hours = hourly triggers).
2. ?: Unspecified value (required for either DayofMonth or DayofWeek).
3. -: Range (e.g., 5-20 in Hours = triggers hourly from 5 AM–8 PM).
4. /: Fixed intervals (e.g., 1/5 in DayofMonth = every 5 days starting on the 1st).
5. ,: Enumeration (e.g., 5,20 in Hours = triggers at 5 AM and 8 PM).
6. L: Last occurrence (e.g., 5L in DayofWeek = last Thursday of the month).
7. W: Nearest weekday (e.g., 5W in DayofMonth = triggers on the closest weekday to the 5th).
8. #: Nth occurrence of a weekday (e.g., 4#2 = second Wednesday of the month).

Examples:

• "59 11 * * 1,2" → Weekly on Monday and Tuesday at 11:59 AM.
• "0 10,14,16 * * ?" → Daily at 10 AM, 2 PM, and 4 PM.
• "15 10 L * ?" → Last day of the month at 10:15 AM.
• "15 10 ? * 6L" → Last Friday of the month at 10:15 AM.
• "15 10 ? * 6#3" → Third Friday of the month at 10:15 AM.

1.2 Trigger Event Mapping Logic

Single-Object Workflow

picture coming soon:

CRM → Third-Party System

picture coming soon:

1. Default Behavior:
   • The CRM automatically notifies the Integration Platform of all object events (create, edit, void). No manual trigger configuration is needed.
2. New CRM Data:
   • If “Create” is enabled for the target system, the Integration Platform executes a “Create” operation (if within sync scope).
   • If disabled, no action is taken.
3. Edited CRM Data:
   • No ID Mapping: Treated as new data → “Create” operation (if enabled).
   • ID Mapping Exists: Treated as existing data → “Edit” operation (if enabled).

Best Practice:
- Use timestamp filters (e.g., creation date) to sync only post-cutoff data.
- Ensure ID mappings exist for historical data in the intermediate table.

Third-Party System → CRM

The same logic applies in reverse. Always validate execution actions against intermediate table mappings.

1.3 Push Actions

1. Real-Time Push: Supported via API.
2. Return Fields: Configure specific target object fields to include in the data response.
   picture coming soon:

1.4 CRM Source Component

Sync Trigger for Imported CRM Data

Configuration Path: Integration Flow > Edit > CRM Source Component
Note: This is an object-level setting affecting all related flows.
picture coming soon:

Field-Level Sync Triggers

Configuration Path: Integration Flow > Edit > CRM Source Component
- Default: Syncs when mapped fields (in scope or field mapping) are edited.
- Custom: Syncs only when selected fields change.
picture coming soon: