I. Conversion Rule Use Cases

• A single conversion relationship supports multiple conversion rules for multi-channel push operations.
• Conversion rules can be duplicated for rapid configuration.
• Track and write back to the Primary Object, associate with the Primary Object to meet data synchronization requirements.
• Map Record Types between objects to enable data conversion for specific business scenarios.
• Automatically match target fields for faster and more convenient configuration.
• Configure split-and-merge strategies for scenarios involving child object data consolidation (Coming Soon).
• Set up write-back field configurations and source document closure policies to synchronize source objects when processing target objects.

II. Business Scenario Examples

Purchase Requisition to Purchase Order Conversion

Company A has established procurement workflows where commonly used materials (pre-negotiated with Suppliers at the beginning of the year) follow this process:
- The requesting Dept. submits a Purchase Requisition → Upon approval → The system automatically generates a formal Purchase Order.
- For example, if Material A is purchased from Supplier X and Material B from Supplier Y, a single approved Purchase Requisition will split into two separate Purchase Orders—one for each Supplier.

Purchase Order Creation Referencing Purchase Requisitions

Company B adopts centralized procurement for MRO materials or office supplies. At month-end:
- The centralized procurement Dept. aggregates multiple pending Purchase Requisitions from various Departments.
- Requisitions with the same material category and required delivery date are merged into a single Purchase Order for bulk quotation and procurement.