What this category's data looks like
Materials for vocational training subsidy applications include training class filing records, attendance records, completion assessment forms, as well as intake records and the follow-up questions that complete them. Class filing records provide the institution name, training occupation, class start date, and approval signature; attendance records provide the trainee name, attendance date, and personal signature; completion assessment forms provide the assessment score, completion date, and assessor signature. When these materials enter the Q&A intake and missing-item follow-up function, each plays a different role: filing records are used to determine the applying entity and training scope, attendance records are used to check attendance and personnel correspondence, and completion assessment forms are used to confirm assessment results and completion time. Materials are updated by batch, and it is common for the name, quantity, or date of the same record to mismatch across two materials, for versions to be out of sync, or for signatures or receipts to be missing. Field characteristics are concentrated in date, quantity, name, and signature columns, and on this basis the intake step identifies missing items and generates follow-up questions.
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 records and the follow-up questions that complete them are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to finish the process. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Request address and path parameters | The placeholder variables can be resolved into actual values and are consistent with the external interface agreement | View the fully rendered address in the request preview, and check the value source of the path parameters |
| Request headers | Authentication information is passed in according to the external system's requirements, and the Authorization name and value source are traceable | Check the request header names and value sources, and confirm that the corresponding variables have been output by preceding nodes |
| Request body | The fields are consistent with the external interface agreement, and the intake record and follow-up question fields are complete | Compare the response using a sample request, and check the returned fields in responseData |
| Variable sources | Every placeholder can be traced to a specific origin, and the date and signature fields of the class filing records, attendance records, and completion assessment forms are not missing | Check the source of each placeholder in variables in the variable panel, and compare the material dates and signature columns |
Three common errors
- Symptom: the request returns 401. Cause: the request header authentication information was not passed in according to the external system's requirements, or the
Authorizationvalue source points to an unresolved variable. - Symptom: the external system receives empty fields. Cause: the same trainee name, quantity, or date mismatches between the class filing records and the attendance records, so the variable reference resolves to nothing.
- Symptom: the request times out. Cause: the completion assessment form version is out of sync, signatures or receipts are missing, and the external interface waits for confirmation and cannot return in time.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the intake record and follow-up question fields in responseData match the sample.
Business test: submit a question that is missing key information and see whether it asks a follow-up question before answering.
- Check the fields, dates, and signatures of the class filing records, attendance records, and completion assessment forms, and mark places where the name, quantity, or date of the same record is inconsistent across two materials.
- Check the source of each placeholder in
variablesin the variable panel, and confirm that the request headers, request body, and path parameters can all be resolved into actual values.