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 provides fields such as the institution name, education level, programs, and enrollment scale; the cooperation agreement states the names of both parties, the cooperation term, the signing date, and signatures/seals; the articles of association stipulate the governance structure, decision-making mechanism, and annual report responsibilities. The materials come from the application system, partner texts, and internal archives, and are updated weekly or monthly. When entering the workflow, the establishment application serves as the primary record source, while the cooperation agreement and articles of association serve as sources for field and date verification. The name, quantity, and date of the same record in the three materials must be alignable, and versions and signed receipts must be traceable. The progress table and statistical scope description are completed by subsequent nodes continuing execution along branches, and the material roles determine branch selection and verification order.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "progress table and statistical scope description" is completed by subsequent nodes continuing execution along branches. When the user selection node is 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 | Name, quantity, and date align item by item with the cooperation agreement and articles of association; signatures and receipts are complete | Verify fields and dates, check signature pages and receipts; check options and branch connections one by one in the node |
| Cooperation agreement | The names of both parties, cooperation term, and signing date are consistent with the establishment application, and the version is the latest | Compare names and dates, check version numbers and signatures/seals; reference variables in subsequent nodes and run a trial once |
| Articles of association | Governance structure, decision-making mechanism, and annual report responsibility fields are consistent with the establishment application and cooperation agreement | Verify clauses and dates, check version synchronization; trigger once to view node status in the run records |
| Progress table and statistical scope description | Record counts match statistical counts, the scope is written in the header, and exceptions are clearly stated | Use one week of records to verify totals, check header scope and exceptions; verify the status corresponding to nodeId in the run records |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the establishment application and the cooperation agreement. Cause: The two materials are updated separately, without field-level comparison and version synchronization.
- Symptom: The version of the articles of association is not synchronized, and the annual report references old clauses. Cause: The version number and effective date were not updated together with changes to the cooperation agreement, and archiving did not overwrite the old version.
- Symptom: Signatures or receipts are missing, but the record still enters statistics. Cause: Verification only looked at fields and not signature pages and receipts, and exceptions were not marked in the header scope.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch directions and interaction status in the run records, and confirm that variables has been passed to subsequent nodes.
Business test: use one week of records to verify totals, and see whether the scope and exceptions are clearly stated; check that the status corresponding to nodeId is consistent with the branch direction.
- Check options and branch connections one by one in the node, and trigger once to view node status in the run records.
- Reference
variablesin subsequent nodes and run a trial once to confirm that the selection result variable has been passed and the branch is correct.