What this category's data looks like
This category's data mainly comes from establishment applications, cooperation agreements, articles of association, annual report receipts, and signature pages. The establishment application lists the institution name, education level, enrollment scale, and date; the cooperation agreement stipulates the names of both parties, the amount of capital contribution, the validity period, and the signature page; the articles of association set out the governance structure, signatures, and seal-use records. The annual report is updated annually, with fields including enrollment numbers, faculty numbers, financial data, and receipt number. When the materials enter the exception tracing and manual review workflow, the establishment application serves as the primary record source, the cooperation agreement and articles of association serve as cross-comparison sources, and the annual report receipt serves as the time-series update source; together, the three support the location of the original records for the exception list.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution according to the branches. After the user completes the selection, the node follows the corresponding option to continue execution along the branch, and the interaction state and selection result variables are recorded together.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | The institution name, enrollment scale, date, and signature fields must correspond item by item with the cooperation agreement and articles of association | In the node, check the options and branch connections, reference variables for a trial run, and view the run records |
| Cooperation agreement | The names of both parties, the amount of capital contribution, the validity period, and the signature page date must be consistent with the establishment application | Trigger an interaction state once, and check the node state corresponding to nodeId and the selection result variable |
| Articles of association | The governance structure, signatures, and seal-use records must be synchronized with the versions of the establishment application and cooperation agreement | In a subsequent node, reference the selection result variable for a trial run, and check whether the branch direction corresponds to the option |
| Annual report receipt | The enrollment numbers, faculty numbers, financial data, and receipt number must be consistent with the materials for the current year | Check the receipt number and date fields, and confirm whether the source can be traced when the version is not synchronized or signatures are missing |
Three common errors
- Phenomenon: The institution name, enrollment numbers, and dates for the same record do not match between the establishment application and the cooperation agreement. Cause: The two materials were entered separately without cross-comparison, and the exception list lacks a pointer to the original record.
- Phenomenon: The version of the articles of association is not synchronized, and the old signature page is still referenced. Cause: After the version update, the primary record was not written back, and the review was judged according to the old version's fields, breaking the exception tracing chain.
- Phenomenon: The cooperation agreement lacks a signature or the annual report lacks a receipt, yet the review conclusion is still signed off. Cause: The review node did not validate the signature and receipt fields, and the manual review became a mere formality.
How to verify the setup
This feature's acceptance: run each option one by one, check the branch direction and interaction state in the run records, and confirm that variables, nodeId, and the selection result variable are all recorded.
Business test: create an exception record, see whether the source material can be traced, and check whether the exception list has original record support and whether the reviewer has signed.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- In a subsequent node, reference the selection result variable and run a trial once, and check whether the process continues execution after the interaction is completed.