What this category's data looks like
The establishment and annual reports of Chinese-foreign cooperative education institutions involve three types of materials: the establishment application, the cooperation agreement, and the articles of association. The establishment application contains the institution name, education level, enrollment scale, and signature date; the cooperation agreement contains the Chinese and foreign party names, contribution amounts, validity period, and signature page; the articles of association contain the governance structure, procedural rules, and change clauses. The materials come from approval receipts, exchanges of letters between both parties, and annual report filings. The update cadence is divided into one-time submission during the establishment phase and annual rolling submission for annual reports. When the materials enter the workflow, the establishment application serves as the master record, while the cooperation agreement and articles of association serve as cross-reference sources for comparing names, quantities, dates, and signatures.
Configuration and implementation checks
This step is executed by workflow nodes (user selections and branches), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branches. When triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Whether the fields, dates, and signatures are consistent with the cooperation agreement and articles of association | Check item by item the institution name, enrollment quantity, and signature date; verify the options and branch connections one by one in the node, and record nodeId |
| Cooperation agreement | Whether the name, quantity, and date of the same record do not match the application | Check the Chinese and foreign party names, contribution amounts, validity period, and signature page; reference variables in subsequent nodes and run a trial once |
| Articles of association | Whether the version is synchronized and whether signatures or receipts are missing | Check the governance structure, change clauses, and signed receipts; trigger once to view the node status in the run records |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and record the branch direction and interaction state |
Three common errors
- Symptom: The same institution name is written differently in the establishment application and the cooperation agreement. Cause: The two materials were drafted separately and entered the version ledger without cross-comparison.
- Symptom: The enrollment quantity or signature date does not match between the two materials. Cause: After revision, only one was updated, while the other remained the old version and was not marked as changed.
- Symptom: The articles of association lack signatures or receipts, and the version number is not synchronized. Cause: After changes, the ledger was not written back, and subsequent nodes still referenced the old version content.
How to verify the setup
Acceptance for this feature: run trials option by option, and check the branch direction and interaction state in the run records.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in subsequent nodes and run a trial once to confirm that it has been passed to the subsequent nodes.