What this category's data looks like
The progress records and statistical verification for vocational college program setup filing draw on program setup filing forms, talent demand justification, and faculty and equipment lists. The filing form records the program name, code, program length, and planned enrollment numbers, and includes signature and receipt sections; the justification materials provide industry talent demand and job correspondence, with the justification date and expert signatures attached; the faculty and equipment list sets out the number of teachers, title structure, equipment units and sets, and site area, including the filing date and the signature of the person in charge. The three types of materials are updated by academic year or batch, and the names, quantities, and dates of the same program across different materials must be mutually traceable. When entering this function, the filing form serves as the main record, while the justification and list serve as attachment fields or external system indexes; the HTTP interface is responsible for sending the records and statistical criteria to the external system and retrieving the receipt or status.
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 criteria description are parsed from the response by subsequent nodes, or the external system handles them according to the agreement and then completes the process. The HTTP node does not replace the external system in writing to the database or approving; it only sends requests and receives responses according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| Program setup filing form | The program name, code, program length, planned enrollment numbers, and signature and receipt dates must be consistent with the justification and list | In the request preview, view the rendered address and request body, and check whether the filing form fields enter the request body according to the agreement |
| Talent demand justification | The justification date, expert signatures, and job correspondence must match the same program in the filing form | Check the request header names and value sources, and confirm that the reference path of the justification materials as attachment fields can be traced to the specific source |
| Faculty and equipment list | The number of teachers, title structure, equipment units and sets, filing date, and signature of the person in charge must be consistent with the filing form criteria | Use one sample request to compare the response, and see whether the list fields are accepted by the external interface and have no empty fields |
| Statistical criteria description | The record count and statistical count must match, the criteria must be written in the header, and exceptions must be listed separately | In the variables panel, check the source of each placeholder, and confirm that the statistical criteria are sent along with the request body or request headers |
Three common errors
- Symptom: The name or code of the same program does not match between the filing form and the justification materials. Cause: The two materials were entered separately, and field mapping was not based on the filing form as the main record.
- Symptom: The quantities or dates in the faculty and equipment list are inconsistent with the filing form. Cause: The versions were not synchronized, and the old list is still referenced in the request body.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information was not passed in according to the external system's requirements, or the placeholder variables were not resolved into actual values.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, and then compare the result against one sample; confirm that the Authorization request header, the variables placeholder sources, and the responseData returned fields all conform to the agreement.
Business test: use one week of records to verify the totals, and see whether the criteria and exceptions are clearly written; if a reference limit is involved, check the tokens of the referenced text, record the array count separately, and do not compare it for equality with quoteMaxToken.
- In the request preview, view the complete rendered address, and check whether the path parameters and request body fields are consistent with the external interface agreement.
- In the variables panel, check the source of each placeholder, and confirm that global variables, system variables, or outputs from preceding nodes can be traced to the specific source.