What this category's data looks like
In the off-campus training compliance filing and penalty response scenario, materials mainly come from three categories: school operating licenses, course filing materials, and fee disclosure. The school operating license provides the institution name, address, validity period, and issuance date; the course filing materials record the course name, class hours, start date, and signature; the fee disclosure corresponds to fee items, amounts, refund rules, and disclosure date. The three categories of materials are updated weekly or monthly, and their field characteristics are name, quantity, date, signature, and receipt. When the materials enter the progress records and statistical reconciliation function, the school operating license serves as the subject identity baseline, the course filing materials serve as the course progress and statistical object, and the fee disclosure serves as the source of fee scope and exception explanations. The HTTP module is responsible for initiating requests to external systems, passing the fields and dates from the three categories of materials as variables for subsequent nodes to parse the response and generate the progress table and statistical scope explanation.
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 "progress table and statistical scope explanation" is completed by subsequent nodes parsing the response, or by the external system handling it according to the agreement. The request URL, request headers, and request body can all use variables placeholders, and the variables come from global variables, system variables, or outputs from preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| School operating license | Whether the institution name, address, validity period, issuance date, and signature are consistent with the course filing materials | In the request preview, view the complete rendered address, and check the dates and signatures of the license fields against the corresponding fields in the course filing materials |
| Course filing materials | Whether the course name, class hours, start date, and signature match the name, quantity, and date in the fee disclosure | Use one sample request to compare the response, and check the fields, dates, and signatures of the course filing materials against the fee disclosure |
| Fee disclosure | Whether the fee items, amounts, refund rules, and disclosure date are synchronized with the version of the course filing materials | Check the request header names and value sources, and compare the versions and receipts of the fee disclosure and the course filing materials |
| HTTP request variables | Each placeholder can be traced to a specific source, and the sources of the Authorization and responseData fields are clear | In the variables panel, check the source of each placeholder, and confirm that the request header and request body fields are consistent with the external interface agreement |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the school operating license and the course filing materials. Cause: The two materials are maintained separately, and the field scope and date format were not unified before the request.
- Symptom: The fee disclosure and the course filing materials are not synchronized in version, and differences appear in the progress table and statistical counts. Cause: The variables referenced by the HTTP request come from the output of an old version node and were not updated to the latest materials.
- Symptom: The course filing materials lack a signature or receipt, and the validity of the record cannot be confirmed during statistical reconciliation. Cause: The material circulation step did not pass the signature and receipt as required fields into the request body.
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, and confirm that the Authorization and responseData fields conform to the agreement.
Business test: use one week of records to check the totals, see whether the scope and exceptions are clearly stated, and confirm that the record count and statistical count match and that the scope is written in the header.
- In the request preview, check the complete rendered address, request headers, and request body, and confirm that each placeholder variable can be resolved into an actual value.
- Use one sample request to compare the response, and check whether the fields, dates, and signatures of the school operating license, course filing materials, and fee disclosure are consistent.