Object Conversion Rules Product Overview

1. Feature Overview

Many business scenarios require transforming data between different object types—essentially converting one object into another. To support these scenarios, we developed an object transformation engine based on a metadata model. The engine enables automatic creation and propagation of object data. The primary purpose of Transformation Rules is to let users define mapping relationships between various business objects and automatically (or in batch) convert source object data into target object data, significantly reducing manual effort. You can also configure timing via workflow post-actions to enable automatic push-downs.

Key capabilities include: - Establishing and maintaining relationships (associations); - Defining transformation routes and mapping rules; - Configuring write-back rules and source-record closing logic.

2. Basic Configuration Steps

• Step 1: Configure transformation rules in the admin console
  Basic Info → Relationship Configuration → Field Mapping → Split/Merge Rules Configuration (not available in this release) → Write-Back Settings → Close Logic → Overrun Check
• Step 2: Click the Transform button on the source record. While the source record is in a saved state, the system can automatically push fields according to configured rules.
• Step 3: After creating and saving the target record, the system will—when configured conditions are met—write back certain fields to the source record to complete the source record update.

3. Definitions

• Source Record: The object being transformed. Example: when a Purchase Requisition is converted to a Purchase Order, the Purchase Requisition is the Source Record.
• Target Record: The mapped object. Example: when a Purchase Requisition is converted to a Purchase Order, the Purchase Order is the Target Record.

4. Key Benefits

• Once rules are configured, data transfer between documents is automated—eliminating duplicate entry and reducing costs while improving efficiency.
• Rule configuration is clear and easy to understand, with a guided step-by-step setup.
• Rules offer rich control features, allowing flexible customization of trigger conditions, data transfer methods, and post-transfer validations.