What this category's data looks like
In the scenario of establishment and annual reports of Chinese-Foreign cooperative education institutions, the materials entering the acceptance stage usually include the establishment application, cooperation agreement, articles of association, as well as the annual operation situation, financial and faculty ledgers on which the annual report is based. The sources are mostly submissions from the declaration system and offline stamped scanned copies. The update rhythm rolls with acceptance batches, correction rounds, and annual report cycles. Field characteristics are concentrated in institution name, number of majors and courses, enrollment scale, signing date, signature, and receipt number. The establishment application assumes the declaration role for subject information and educational arrangements. The cooperation agreement assumes the proof role for the rights and obligations, term, and signing role of both Chinese and foreign parties. The articles of association assume the normative role for governance structure, decision-making procedures, and signature/seal roles. After the three types of materials enter the same acceptance flow, fields often show inconsistencies in names, quantities, and dates for the same record across different materials, versions not synchronized, and missing signatures or receipts.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Acceptance records and supplementary question items" are continued and completed by subsequent nodes according to the branch. When a 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 | Whether institution name, number of majors and courses, enrollment scale, signing date, signature, and receipt are aligned item by item with the cooperation agreement and articles of association | In the node, check the options and branch connections one by one, trigger once to view the node status in the run record, and reference the selection result variable in subsequent nodes for a trial run |
| Cooperation agreement | Whether the names of both Chinese and foreign parties, cooperation term, quantities, and dates are consistent with the establishment application and articles of association, and whether the signature page and receipt are complete | Check the options and branch connections, inspect the interaction status record, reference the selection result variable in subsequent nodes, and run a trial once |
| Articles of association | Whether the governance structure, decision-making procedures, and signature/seal roles are consistent with the establishment application and cooperation agreement, and whether versions are synchronized | Check the branch direction and interaction status, check whether the selection result variable has been passed to subsequent nodes, and when items are missing, ask follow-up questions first before answering |
| Annual report materials | Whether the names, quantities, and dates of the annual operation situation, financial and faculty ledgers match the establishment application, cooperation agreement, and articles of association | Check the branch corresponding to the options, view the node status record, and reference the selection result variable in subsequent nodes for a trial run |
Three common errors
- Phenomenon: 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 maintained separately, and no field-level comparison was performed during acceptance.
- Phenomenon: The version of the articles of association is not synchronized, and the old signature/seal page is still submitted with the documents. Cause: After the version update, no receipt confirmation was made, and the material package was not re-signed by batch.
- Phenomenon: The cooperation agreement lacks a signature or receipt, and after follow-up questions, it still continues along the default branch. Cause: The options and branch connections were not checked one by one, and the interaction status record was not reviewed.
How to verify the setup
Acceptance of this function: run trials option by option, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and check whether variables and nodeId take effect after being referenced in subsequent nodes.
Business test: submit a question that lacks key information and see whether it asks follow-up questions first before answering; if the missing item is identified and followed up, and the answer has a material basis, then transfer it to the handler.
- In the node, check the options and branch connections one by one, trigger once to view the node status in the run record, and confirm that the process continues downward after the interaction is completed.
- Reference the selection result variable in subsequent nodes and run a trial once, check the reference positions of
variablesandnodeId, and confirm that missing items are identified and followed up before transferring to the handler.