Published at: 2025-10-30
How to Configure Conversion Rules
I. Key Procedures
Step 1: Manage the conversion rule list
| Primary Buttons | Description |
|---|---|
| New | Create a blank new rule |
| Delete | Enabled rules cannot be deleted; disable them first |
| Enable/Disable | Enabled rules take effect immediately; disabled rules become inactive |
| Copy | Duplicate the source rule as an independent new rule. Subsequent changes to the source rule will not affect the copied rule |
Step 2: Maintain basic information
- Enabled: New rules are enabled by default.
| Key Configuration Items | Description |
|---|---|
| Rule Name | Must be unique among conversion rules |
| Enabled | New rules are enabled by default; only enabled rules are executed |
| Remarks | Add a description for the rule |
Step 3: Configure conversion relationships
In this phase, the target object and source object must have a lookup relationship. Configure lookup fields to support subsequent business tracking and write-back.
| Key Configuration Items | Description |
|---|---|
| Source Object/Target Object | 1. Conversion rules cannot be configured without a lookup relationship. 2. If both objects have Sub-objects, Sub-object mapping is available. To enable tracking/write-back for Sub-objects, establish a lookup relationship between them. Otherwise, conversion is not allowed. |
| Record Type Configuration | Map different record types to corresponding target objects. |
| Data Scope Configuration | Define the data scope for rule execution. |
Step 4: Maintain field mappings for object conversion
Configure field mappings between Primary Objects and Sub-objects. At least one mapping is required.
Field mappings include the following configurable items:
- Value Assignment: Define how target fields derive values from source fields.
| Configuration Item | Key Configuration | Description |
|---|---|---|
| Value Assignment | Source Field | Directly use the source field value. Field types must match. |
Step 5: Configure write-back rules (optional)
- Write-back Timing: Defaults to “Upon submission.”
- Write-back Fields: Use calculated or aggregated fields as source fields for write-back.
II. Use Case Examples
2.1 Example Scenario
- Dept. A requests 3 laptops, creating a purchase requisition with purchase details as Sub-objects.
- The procurement team receives the purchase order, where the order details specify the products. Initially, only 2 laptops are procured; the remaining 1 is procured later.
-
Mapping: Purchase Requisition → Purchase Order Purchase Requisition Details → Purchase Order Details.
Key fields for tracking:
- Procured: Total laptops procured.
- Remaining: Calculated as Target Quantity - Procured Quantity.
First Procurement:
- Target: 3 | Procured: 2 | Remaining: 1.
Second Procurement:
- Target: 3 | Procured: 3 | Remaining: 0.
Here, Procured, Target Quantity, and Remaining are write-back fields configured in the field list.
2.2 Close Logic Configuration
Continuing the scenario:
- If Remaining ≤ 0, the requisition is complete and should be closed to prevent further procurement.
- Create a close flag field (e.g., Procurement Complete with options: Yes/No). When set to Yes, the system closes the record.
Example:
- Close Field: Procurement Complete.
- When Remaining ≤ 0, update the field from No to Yes.
III. Primary Object Close Strategies
- Close Primary Object After All Sub-objects Are Closed:
- Example: If Dept. A also requests 4 monitors, the purchase order closes only after all monitors and laptops are procured.
- Close Primary Object Immediately After Conversion:
- Applicable if no Sub-object mapping exists.
IV. Overrun Check
Scenario: If the second procurement exceeds the target (e.g., 4 laptops for a target of 3):
- Configure strict overrun control to block invalid transactions.
- Use formulas (e.g., Target Quantity - Procured Quantity < 0) to trigger errors before write-back/closure.
V. Frontend Usage of Conversion Rules
After configuration, a Convert button appears on the source record:
- Multiple Rules: A popup lets users select the target object.
- Single Rule: Auto-matched.
- Record Type Mapping: Auto-redirects to the corresponding creation page.
Reference-Based Creation:
In the target object, select Create from Reference to auto-match conversion rules.
