What this category's data looks like
The materials for progress records and statistical reconciliation of primary and secondary school enrollment organizations come from three places: the enrollment plan, the application materials checklist, and the admission list. The enrollment plan defines the schedule and batches, the application materials checklist lists documents and receipts, and the admission list carries students and signatures. The materials are updated weekly, and the fields include name, quantity, date, and signature status. When entering the HTTP interface and external system feature, the enrollment plan serves as the basis for request path parameters and the request body, the application materials checklist provides request header authentication and field validation, and the admission list serves as the comparison source for fields returned in the response body. The statistical scope description is written in the header of the progress table, and the record count and statistical count are reconciled week by week.
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 description" are parsed by subsequent nodes from the response, or handled by the external system according to the agreement to complete the next step. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Enrollment plan | Fields, dates, and signatures must be aligned item by item with the application materials checklist and the admission list | In the request preview, view the complete rendered address and check whether the path parameters and request body fields are taken from the plan |
| Application materials checklist | Name, quantity, date, and receipt must be consistent with the admission list | Check the request header names and the source of their values, and compare the returned fields with a sample request |
| Admission list | Signatures and dates are consistent between the list and the header scope of the progress table | In the variable panel, check the source of each placeholder and confirm that variables can be traced to the admission list fields |
| HTTP node | Only outputs the response body, status code, and returned fields; does not write to the database or approve | Check the responseData fields and the Authorization request header, then compare the result against a sample |
Three common errors
- Symptom: The name and quantity of the same record do not match between the application materials checklist and the admission list. Cause: The field sources in the two places are not unified, and the mapping between request body and response body fields is misaligned.
- Symptom: The enrollment plan version is not synchronized, and the progress table is still counted according to the old batch. Cause: The request path parameters reference outdated variables and were not updated with the plan.
- Symptom: The admission list lacks a signature or receipt, but the statistical total still includes it. Cause: The request header authentication passes, but the returned fields do not include signature status, and subsequent nodes do not validate exceptions.
How to verify the setup
This feature acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; check whether responseData and Authorization are parsed according to the agreement.
Business test: use one week of records to check the total and see whether the scope and exceptions are clearly written; record the number of quotes and quoteMaxToken separately, and check the tokens of the quoted text.
- In the request preview, view the complete rendered address and check whether the path parameters and request body fields are consistent with the enrollment plan and the application materials checklist.
- In the variable panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or outputs from preceding nodes.