What this category's data looks like
This page focuses on off-campus training compliance filing and penalty response, connecting three types of materials—school operating licenses, course filing materials, and fee disclosure—into the Q&A intake and missing-item follow-up process. The school operating license is used to verify the name, license number, validity period, and signature; the course filing materials are used to verify the course name, number of class hours, filing date, and seal; the fee disclosure is used to verify the fee items, amounts, disclosure date, and receipt. The material sources are scanned copies submitted by institutions and structured fields pushed by external systems, and the update cadence is triggered by filing changes and penalty notices. When materials enter this feature, the license and filing materials serve as the basis for the question items, and the fee disclosure serves as the consistency comparison baseline. The HTTP interface sends the question and material fields to the external system, which returns the missing items and follow-up question list.
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 "intake record and items to be completed" are parsed from the response by subsequent nodes, or handled and completed by the external system according to the agreement. The request URL, path parameters, request headers, and placeholder variables in the request body come from global variables, system variables, or the output of preceding nodes, and the rendered full URL and value sources can be checked in the request preview.
| Object | Check | Verification action |
|---|---|---|
| School operating license | Whether the name, license number, validity period, and signature are consistent with the filing record | Compare the license fields with the fields returned by the external system in the request body sample, and check the value source of the Authorization request header |
| Course filing materials | Whether the course name, number of class hours, filing date, and seal match | Use a sample request to compare the response, and check whether the quantity and date of the same record are consistent across the two materials |
| Fee disclosure | Whether the fee items, amounts, disclosure date, and receipt are complete | Check the request header names and value sources, and confirm that the disclosure fields are consistent with the external interface agreement |
| HTTP node output | Whether the response body, status code, and returned fields can be parsed by subsequent nodes | Check the source of each placeholder in the variables panel, and use variables and responseData to trace where the fields come from |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match across the two filing materials. Cause: The material versions were not synchronized, and the old version's fields were passed into the request body as the current values.
- Symptom: The external system receives empty fields or returns an authentication failure. Cause: The request header value sources were not checked, and
Authorizationwas not passed in as required by the external system. - Symptom: The fee disclosure is missing a signature or receipt, but the follow-up question list is still released. Cause: Missing-item identification does not cover the signature and receipt fields, and no re-comparison was performed after the version update.
How to verify the setup
This feature's acceptance check: view the rendered full URL in the request preview, check the status code and returned fields, then compare the result against a sample request to confirm the values and sources of Authorization, variables, and responseData.
Business test: submit a question that is missing key information, see whether it asks follow-up questions before answering, and check whether the follow-up items correspond to the missing items in the school operating license, course filing materials, or fee disclosure.
- Check the source of each placeholder in the variables panel, and confirm that the variables in the request URL, path parameters, request headers, and request body can all be resolved into actual values.
- Use a sample request to compare the returned fields with the external interface agreement, and check whether the name, quantity, and date of the same record are consistent across the two materials.