What this category's data looks like
The materials for the establishment and annual reports of Chinese-foreign cooperative education institutions mainly include the establishment application, cooperation agreement, articles of association, as well as annual report filing and receipts. The establishment application provides the institution name, education level, programs, and enrollment scale; the cooperation agreement stipulates the rights and responsibilities of each party, the method of contribution, and the term; the articles of association state the governance structure, decision-making procedures, and signature pages. Materials are usually updated by academic year or approval batch, with fields concentrated on names, quantities, dates, signatures, and seals. When entering the authorized access and external services function, the establishment application and cooperation agreement provide the basis for identity and scope, the articles of association and receipts provide signing and version credentials, and the annual report data serves as the source of content visible by identity in external services.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The externally available entry point and authorization scope are parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. The HTTP node is only responsible for sending requests and returning results; it does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Whether the name, quantity, date, and signature are consistent with the cooperation agreement | Compare the two materials field by field; those missing signatures or receipts are marked as pending supplementation |
| Cooperation agreement | Whether the name, quantity, and date of the same record match the articles of association | Check the signature page and version number to confirm there is no unsynchronized old version |
| Articles of association | Whether the governance structure and decision-making procedure fields are consistent with the annual report criteria | Check the signature and seal pages, and verify whether the receipts are complete |
| HTTP request | Whether the request URL, request headers, and request body can be parsed as agreed | View the rendered complete URL in the request preview, and verify the sources of Authorization, variables, and responseData |
Three common errors
- Symptom: The same institution name is written differently in the establishment application and the cooperation agreement. Cause: The two materials are maintained separately, versions are not synchronized, and there is no unified field standard.
- Symptom: The enrollment quantity and date do not match between the annual report and the appendix to the articles of association. Cause: The update cadence is inconsistent, old versions are not invalidated, and receipts are not archived.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The authentication information and request body fields are not passed in according to the external interface agreement, and the variable sources have not been verified.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the variables panel, verify the source of each placeholder and confirm that
Authorizationandvariablescan be resolved into actual values. - Use one sample request to compare the response and check whether the
responseDatafields are consistent with the external interface agreement.