What this category's data looks like
Establishment and annual report materials for Chinese-foreign cooperative education institutions, including establishment applications, cooperation agreements, and articles of association, with fields covering institution name, education level, enrollment scale, signature date, and receipt. The materials come from two rhythms: application and annual report. In the establishment stage, the application and cooperation agreement enter in the same batch; in the annual report stage, the articles of association and receipt are updated annually. When entering the user selection and branching function, the establishment application serves as the main file for the entry authorization scope, the cooperation agreement and articles of association serve for field comparison and signature verification, and the receipt serves for timeliness confirmation. The field characteristic is that the same record must be consistent across multiple materials in name, quantity, and date, versions must be synchronized, and signatures and receipts must appear in pairs.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" are then completed by subsequent nodes continuing execution according to the branch. When the 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, and subsequent nodes reference the selection result variable to continue advancing.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Institution name, education level, enrollment scale are consistent item by item with the cooperation agreement and articles of association, and the signature date is within the validity period | Check the options and branch connections one by one in the node, run a trial and then inspect the node status in the run record, and reference variables and nodeId in a subsequent node for one trial run |
| Cooperation agreement | The name, quantity, and date of the same record match the establishment application, the version is the latest, and signatures are complete | Trigger one interaction, inspect the node status in the run record, and check the correspondence between the cooperation agreement fields and the establishment application fields |
| Articles of association | The articles of association clauses are consistent with the establishment application and cooperation agreement in name and date, and are not released when signatures or receipts are missing | Reference the selection result variable in a subsequent node and run a trial once, and check the correspondence between the articles of association fields and the receipt |
| Receipt | The receipt is paired with the dates and signatures of the articles of association and cooperation agreement, and is marked pending supplementation when the version is not synchronized | Trigger once, inspect the node status in the run record, and check whether the receipt date and signature are paired |
Three common errors
- Phenomenon: the same institution name is written differently in the establishment application and the cooperation agreement. Cause: the two materials were entered separately, without field comparison and version synchronization.
- Phenomenon: the enrollment scale quantity does not match between the articles of association and the establishment application. Cause: the annual report update only changed one material, and the other was not synchronized.
- Phenomenon: branching continues even when signatures or receipts are missing. Cause: the options and branch connections were not checked one by one, and the interaction status was not reviewed.
How to verify the setup
Acceptance of this function: run trials for each option one by one, check the branch directions and interaction status in the run record, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and ensure unauthorized content is not visible.
- Check the options and branch connections one by one in the node, and after triggering once, inspect the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, and check the fields and dates of the establishment application, cooperation agreement, articles of association, and receipt.