What this category's data looks like
This category's data covers three types of materials: the establishment application, the cooperation agreement, and the articles of association. The establishment application contains the institution name, education level, program offerings, and signature fields; the cooperation agreement contains the names of both the Chinese and foreign parties, the contribution amount, the effective date, and the signature page; the articles of association contain the governance structure, rules of procedure, and the signature of the legal representative. When the materials enter the HTTP interface function, each serves as a request body field source or attachment reference object: the application fields are used by external systems to create records, while the cooperation agreement and articles of association serve as the basis for version comparison and receipt verification. The update cadence advances according to approval milestones; each revision generates a new version number and retains a traceability path to the old version. Field characteristics center on four categories: names, quantities, dates, and signatures, and field names must be agreed with the external system to stay consistent.
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 "version ledger and change records" are completed by subsequent nodes parsing the response, or by the external system handling it as agreed.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | The institution name, education level, number of programs, and signature date must be consistent between the application and the cooperation agreement | In the request preview, check the fully rendered address and request body fields, and confirm that the value sources for the name, quantity, date, and signature fields are traceable |
| Cooperation agreement | The names of both the Chinese and foreign parties, the contribution amount, the effective date, and the signature page must be consistent with the corresponding records in the articles of association and the application | Check the request header names and value sources, confirm that the authentication information is passed in as required by the external system, and compare the dates and signatures in the cooperation agreement and the articles of association |
| Articles of association | The governance structure, rules of procedure, and signature of the legal representative must be synchronized with the references in the application and the cooperation agreement | Use one sample request to compare the response, confirm that the articles of association fields are consistent with the external interface agreement, and check whether the old version is traceable |
| Request headers and variable sources | Each placeholder variable can be resolved into an actual value and traced to a specific origin | In the variables panel, check the sources of variables, Authorization, and responseData, and confirm there are no empty fields |
Three common errors
- Symptom: the same institution name is written differently in the application and the cooperation agreement. Cause: the two materials were revised separately, without field-level comparison and version synchronization.
- Symptom: the contribution amount in the cooperation agreement does not match the record in the articles of association. Cause: after revision, only one material was updated, the old version was not marked invalid, and references were not synchronized.
- Symptom: the external system receives empty fields or returns 401. Cause: the request body fields are inconsistent with the interface agreement, or the authentication information was not passed in as required by the external system.
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 to confirm that responseData and Authorization are passed correctly.
Business test: change one piece of content and see whether the version number and references are updated in sync
- In the variables panel, check each placeholder source of
variables,Authorization, andresponseData, and confirm it can be traced to a global variable, a system variable, or the output of an upstream node - Use one sample request to compare the returned fields with the external interface agreement, and check whether the four field categories—name, quantity, date, and signature—are consistent