Business Association rules
Q: How to sort and execute business association rules and integration automation?
Currently, business association rules and integration automation are independent execution logic, andThey are executed in their own execution order, that is, the execution order is uncontrollable..
If mixed use, the same target form may be executed by the two task scheduling systems in the expected order, resulting in abnormal update results of business results, especially for complex business processing such as purchase, sale and deposit, etc.
Priority recommend be given to using YIDA integration automation for inter-business synchronization.
Q: How to sort and execute multiple Business Association rules on an integrated automation node?
Business Association rules currently support writing multiple rules, but due to product restrictions,The execution order cannot be selected between rules..
To solve the problem of sorting execution, you can use data nodes such as adding, updating, and deleting integrated automation instead. These nodes support scheduling order, you can also view execution records in run logs.
For more information, see the following screenshot:
Q: What is the limit on the amount of data processed by the business association rule formula?
Currently, YIDA business rule functions support the following usage:
Core function | Function | Usage limit |
The formula is mainly used to insert data from the current input table into the target table. |
| |
The formula is used to update qualified data in the target table. |
| |
Formulas are used to insert or update data into the target form. |
| |
The formula is used to delete data from the target table. |
|
Q: How can subforms be updated?
Scenario: data synchronization between subforms in the main table and subforms in another main table
Example:
Main condition:
EQ (target Table. Primary table field, current table. Primary table Field), locate a piece of data of the sub-table data to be updated in the target table
Sub-conditions:EQ (target Table. Subtable. Subtable field, current table. Subtable. Subtable field), then you need to locate the subdata to be updated in the subtable of the target table