What this category's data looks like
The establishment and annual reporting of Chinese-foreign cooperative education institutions is a category in which three materials—the establishment application, the cooperation agreement, and the articles of association—enter circulation simultaneously. The establishment application carries the institution name, education level, enrollment scale, and signature fields; the cooperation agreement carries the names of both parties, contribution amounts, validity period, and signing date; the articles of association carry the governance structure, rules of procedure, and effective date. The three materials come from the cooperating parties and the foreign institution, with update rhythms divided into one-time submission during the establishment phase and backfilling by academic year during the annual reporting phase. Field characteristics are concentrated in the same record across four categories: name, quantity, date, and signature; any inconsistency in any one of them will be exposed during subsequent receipt. After entering the workflow, the three materials are each treated as independent objects and checked item by item; completeness of fields and version synchronization determine whether they can proceed to the next stage.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. "Signable material drafts and handover records" are completed by subsequent nodes continuing execution according to the branch. When triggered, the conversation enters an interactive state and records the workflow status; after the selection is completed, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Fields are complete, responsible person is clear, version and date are consistent; the signature fields correspond to the signing date of the cooperation agreement | Check options and branch connections one by one, reference variables and nodeId to confirm field sources, and record missing items |
| Cooperation agreement | The name, quantity, and date of the same record match across the two materials; the validity period does not conflict with the effective date of the articles of association | Reference the selection result variable in subsequent nodes and run a trial once, comparing the three places: name, quantity, and date |
| Articles of association | Signatures or receipts are not missing; version and date are synchronized, and unsynchronized versions are blocked | Trigger a user selection node once, check the node status in the run record, and confirm that the process continues after the interaction is completed |
| Handover record | Responsible person is clear, receipt fields are complete, version and date are consistent | Draft one according to the template and complete one handover, check whether missing items are blocked, and record the branch direction |
Three common errors
- Phenomenon: The name and quantity of the same record do not match between the establishment application and the cooperation agreement. Cause: The two materials were drafted separately, and the fields were not compared at the same node.
- Phenomenon: The version of the articles of association is not synchronized, and the annual report continues to use the old version date. Cause: The version and date were not passed to subsequent nodes together with the selection result variable.
- Phenomenon: The cooperation agreement lacks a signature or receipt, but the handover record is still released. Cause: The signature fields were not included in the branch judgment, and missing items were not blocked.
How to verify the setup
Acceptance of this feature: Run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and reference variables and nodeId to locate field sources.
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check options and branch connections one by one in the node, confirm that each option corresponds to one branch, and avoid still taking the default branch after selecting a certain option.
- Trigger a user selection node once, check the node status in the run record, confirm that the process continues after the interaction is completed, and that the same session does not repeatedly enter the interaction.