I. Functional Overview

In business systems, there are numerous scenarios involving data conversion between different objects, all of which essentially transform one object into another. To address this, we have developed a metadata model-based object conversion engine to provide this service and facilitate the automated transfer and generation of object data. The primary function of object conversion rules is to enable users to define conversion relationships between various business object data, automatically or batch-converting source object data into target object data, significantly reducing the workload for business personnel. Additionally, workflow post-actions can be configured to automate the push timing.

Key features include:
- Establishing and maintaining associations;
- Conversion paths and rules;
- Write-back rules and source document closure.

II. Basic Configuration Steps

• Step 1: Configure conversion rules in the backend
  • Basic information → Conversion relationship configuration → Conversion field configuration → Split/merge rule configuration (not available in this release) → Write-back settings → Closure logic settings → Over-limit checks

• Step 2: Click the Convert button on the source document. The source document can automatically push field data to the target document based on predefined rules while in a saved state.

• Step 3: After saving the target document post-conversion, the target document writes back data to specific fields of the source document under predefined conditions, completing the source document’s data update.

III. Terminology

• Source Document: The object from which fields are converted. For example, when a Purchase Requisition is converted into a Purchase Order, the Purchase Requisition is the source document.
• Target Document: The object being mapped. For example, when a Purchase Requisition is converted into a Purchase Order, the Purchase Order is the target document.

IV. Key Benefits

• Automated Data Transfer: Once rules are configured, data transfer between documents is automated, eliminating redundant data entry and improving efficiency.
• User-Friendly Configuration: Rules are developed with clarity and simplicity, featuring a step-by-step, guided configuration process.
• Flexible Control: Rich control functionalities allow for customizable trigger conditions, data transfer methods, and post-transfer document validation.