What this category's data looks like
In off-campus training compliance filing and penalty response, materials are mainly of three types: school operating licenses, course filing materials, and fee disclosure. Sources are approval authority receipts, institution's own archives, and public disclosure pages. The school operating license contains the license number, school address, validity period, and signature of the issuing authority; course filing materials contain the course name, class hours, textbook version, filing date, and handler's signature; fee disclosure contains fee items, standards, refund rules, disclosure date, and receipt. The update rhythm is triggered by license renewal, course adjustments, and fee changes, and old versions must be archived and traceable. When entering the HTTP interface, the three types of materials respectively serve as the value sources for request body fields, path parameters, and request header authentication information, mapped by variable placeholders to fields agreed upon by the external system.
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 "version ledger and change records" are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| School operating license | The name, license number, validity period, and signature of the issuing authority are consistent across the three materials, and it is the current sole version | Compare the request body fields with the original license, and verify the source of each placeholder in the variable panel |
| Course filing materials | The course name, class hours, textbook version, filing date, and handler's signature match between the ledger and the filing receipt | Use a sample request to compare the response, and check the course fields and filing date in responseData |
| Fee disclosure | Fee items, standards, refund rules, disclosure date, and receipt are complete, and old versions are traceable | Check whether the request header Authorization is consistent with the external system agreement, and archive the receipt separately |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are updated synchronously | After changing one piece of content, resend the request and check whether the variables values and returned fields are synchronized |
Three common errors
- Symptom: The name, class hours, and filing date of the same course do not match between two materials. Cause: Field sources are not unified, and the request body values are taken from an old version of the ledger.
- Symptom: After license renewal, the old version of the license is still referenced. Cause: The version is not synchronized, and the path parameters and request header authentication information are not updated with the ledger.
- Symptom: The fee disclosure lacks a signature or receipt. Cause: The signature and receipt fields were not verified before the materials entered the interface, and the returned fields are empty.
How to verify the setup
Preview the rendered request, check the status code and returned fields, and then compare the result against a sample.
Business test: Change one piece of content and see whether the version number and references are updated synchronously.
- In the variable panel, verify the source of each placeholder, and confirm that the path parameters, request body, and request header values come from the current version ledger.
- Use a sample request to compare the returned fields, and check whether
responseDataandAuthorizationconform to the external system agreement.