What this category's data looks like
The establishment and annual reports of Sino-Foreign cooperative education institutions involve three types of materials: the establishment application, the cooperation agreement, and the articles of association. The sources are the cooperating parties and the approval authorities. The update rhythm rolls forward with the application milestones and the annual report cycle. The field characteristics include institution name, program name, enrollment number, signing date, signature, and receipt. When entering workflow orchestration, the establishment application assumes the role of field baseline, the cooperation agreement provides the stipulations of both parties and the quantitative basis, and the articles of association fix the governance structure and translation naming rules; on the same record, the three types of materials must have mutually verifiable names, quantities, and dates, and the translated names must be able to refer back to the original text, forming a unified terminology list and a comparison draft.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "unified terminology list and comparison draft" is continued and completed by subsequent nodes according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow state. After the user completes the selection, the branch corresponding to the selected option is followed to continue execution.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Fields, dates, and signatures must be aligned item by item with the cooperation agreement and the articles of association | In the node, check the options and branch connections one by one, and compare the institution name, program name, quantity, and signing date |
| Cooperation agreement | The name, quantity, and date of the same record are consistent across the three materials | Reference variables and nodeId for a trial run, and check whether the fields of this agreement retrieve the same record in subsequent nodes according to the branch |
| Articles of association | The translated name can refer back to the original text and the wording is consistent throughout | Extract the terminology of the articles of association and compare it with the comparison draft, and check whether the branch corresponding to nodeId carries the same terminology variable |
| Unified terminology list and comparison draft | Terminology is consistent throughout and the translated name can refer back to the original text | In subsequent nodes, reference the selection result variable and run a trial once, and check whether the terminology wording is unified throughout |
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 each maintain their own fields, and values are not unified in the node branch.
- Phenomenon: The version of the articles of association is not synchronized, and the terminology list still uses the old translated name. Cause: The update rhythm does not advance with the material version, and the old record is retrieved when the branch continues execution.
- Phenomenon: Missing signatures or receipts still enter external release. Cause: The interaction state record does not verify the signature fields, and the branch direction does not intercept incomplete materials.
How to verify the setup
Acceptance of this function: Run trials option by option, check the branch directions and interaction states in the run records, and check whether variables and nodeId are passed to subsequent nodes with the selection result.
Business test: Sample three terms to check whether the wording is consistent throughout, and check whether the translated names can refer back to the original text.
- In the node, check the options and branch connections one by one, and confirm that each option corresponds to one branch.
- In subsequent nodes, reference the selection result variable and run a trial once, and check that the variable has been passed in.