What this category's data looks like
This page addresses the scenario of establishing Chinese-foreign cooperative education institutions and annual reporting. The materials mainly consist of establishment applications, cooperation agreements, and articles of association, supplemented by annual report filing records and receipts. The establishment application carries the institution name, education level, enrollment scale, and submission date; the cooperation agreement specifies the names of the Chinese and foreign parties, contribution amounts, signing date, and seals; the articles of association stipulate the governance structure, decision-making procedures, and effective clauses. Fields across the three types of materials intersect: the name, quantity, and date of the same record in two materials must be consistent, versions must be synchronized, and signatures and receipts must be complete. After materials enter the workflow, they branch according to user-selected nodes into the deployment, operations, and application handover stage, forming a handover-ready deployment state and operation records. The update cadence rolls with the annual reporting cycle and agreement revisions, and the field characteristics are judged based on the consistency of three elements: version number, connection relationships, and task records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "handover-ready deployment state and operation records" are completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state. 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 | Check the options and branch connections one by one in the node, compare the institution name, enrollment quantity, and signing date in the application and the agreement; reference variables to confirm that the selection result variable has been passed to subsequent nodes |
| Cooperation agreement | Signing date, seals, and receipts are complete, and the version is synchronized with the articles of association | Trigger a user selection node once, view the node status in the run record, check whether the agreement version number and the articles of association version number are consistent, and check whether the signature page and receipt are missing |
| Articles of association | Governance clauses are consistent with the name, quantity, and date in the application and agreement | Reference the variable corresponding to nodeId in a subsequent node and run a test once, and check whether the institution name and decision-making procedures in the articles of association match the agreement provisions |
| Deployment state and operation records | Version, connection, and task records are consistent | Check item by item once according to the handover checklist to see which record is missing; confirm that the branch direction and interaction state records have been written into the run record |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the application and the agreement. Cause: The two materials were revised separately, without cross-checking and version synchronization.
- Symptom: After selecting an option, the default branch is still followed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not correctly passed to subsequent nodes.
- Symptom: The process stops after the interaction is completed, or signatures and receipts are missing. Cause: The interaction state was not fully recorded, and the material signature pages and receipts were not archived together with the version.
How to verify the setup
This feature acceptance: run a test for each option one by one, check the branch direction and interaction state in the run record, and confirm that variables and nodeId can be referenced in subsequent nodes.
Business test: check item by item once according to the handover checklist to see which record is missing, and after confirming that version, connection, and task records are consistent, hand over to operations or the next shift.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a test once, and compare the name, quantity, date, and signature receipts of the establishment application, cooperation agreement, and articles of association.