What this category's data looks like
The materials for the establishment and annual reports of Chinese-foreign cooperative education institutions center on the establishment application, the cooperation agreement, and the articles of association. Their sources are the filing system and offline submission, and their update cadence advances with the establishment approval and annual report cycles. The establishment application carries the institution name, education level, program offerings, and signature page; the cooperation agreement stipulates the names of the parties, the contribution amounts, the signing date, and the receipt; the articles of association specify the governance structure, decision-making procedures, and version number. When these three types of materials enter the exception tracing and manual review function, each serves as an independent comparison source: the application and the agreement are cross-checked for names and amounts, the agreement and the articles are cross-checked for dates and signatures, and the articles version and the receipt are checked for synchronization status. The field characteristics are concentrated in the institution name, number of programs, signing date, version number, and signature field; any missing item or mismatch in any one of them forms a pending-review clue.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the follow-up. The HTTP node does not replace the external system in writing to the database or approving; it is only responsible for delivering the tracing request and receiving the result as agreed.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | The institution name, number of programs, and signing date must be consistent with the cooperation agreement, and the signature field must not be empty | Check the name, amount, and date fields in the application and the agreement, and compare the signature page and the receipt item by item |
| Cooperation agreement | The names of the parties, contribution amounts, and signing date must be consistent with the articles of association, and the version number must be synchronized | Check the name, amount, and date fields in the agreement and the articles, and check whether the version number and the receipt are synchronized |
| Articles of association | The governance structure, decision-making procedures, and version number must be consistent with the agreement and the receipt; a missing signature is an exception | Check the version number and signing date of the articles, and check whether the signature field and the receipt are complete |
| HTTP request | The placeholder variables in the request URL, request headers, and request body must be resolvable into actual values | View the fully rendered URL in the request preview, check the Authorization request header and the request body fields, and confirm that the source of variables is traceable |
Three common errors
- Symptom: the same institution name is written differently in the establishment application and the cooperation agreement. Cause: the two materials were filed separately without cross-checking, and the name field was not unified.
- Symptom: the number of programs does not match between the cooperation agreement and the articles of association. Cause: the version was not synchronized, the articles still used the old draft, and the amount field was not updated with the agreement.
- Symptom: the signing date is missing or the signature field is empty, and the receipt is not attached. Cause: a signature was missed in the material circulation step, the receipt was not collected as agreed, and the signature or receipt is missing.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the returned fields in responseData are consistent with the agreement, and that every placeholder in variables can be traced to its source.
Business test: create one exception record and see whether it can be traced back to the source material; check that the exception is supported by the original record and the reviewer's signature, then hand it to the responsible person for handling.
- In the variables panel, check the source of each placeholder and confirm that the variables in the request URL, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare the response, check whether the external system receives empty fields, and check whether the returned fields are consistent with the agreement.