What this category's data looks like
Vocational training subsidy application materials mainly consist of training class filing records, attendance records, and completion assessment forms, with fields including trainee name, ID number, training trade, class hours, assessment score, date, and signature. The class filing record determines the personnel scope and subsidy standard, the attendance records reflect attendance and class hours, and the completion assessment form gives the score and completion conclusion. The material sources are institutional declarations and competent department review receipts, and the update rhythm advances through the three stages of class declaration, review, and disbursement. When entering this function, the HTTP node is responsible for retrieving version information from the external system, while the materials themselves are parsed by subsequent nodes and then written into the version ledger; old versions are retained and traceable, and references are synchronized to the knowledge base or external documents.
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 completed by subsequent nodes parsing the response, or by the external system handling it as agreed. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Training class filing record | Whether the fields, date, and signature are consistent with the current version | Check the trainee name, ID number, training trade, class hours, and class start date in the filing form, inspect the institution seal and handler signature, and compare the version number |
| Attendance records | Whether the names, quantities, and dates in the same record match across the two materials | Check the attendance date and trainee name day by day, count the attendance quantity, inspect absence remarks and trainee signatures, and compare with the class filing roster |
| Completion assessment form | Whether the assessment score, completion conclusion, and signature receipt are complete | Check the assessment score, completion conclusion, and assessment date, inspect the assessor signature and institution receipt, and compare with the class hours in the attendance records |
| Request URL and path parameters | Whether the placeholder variables can be resolved into actual values | View the rendered full URL in the request preview, and check the source and values of variables |
Three common errors
- Symptom: the same trainee name is written differently in the class filing record and the attendance records. Cause: the material versions are not synchronized, the old roster was not updated with the change, and the reference still points to the old version.
- Symptom: the completion assessment form lacks the assessor signature or institution receipt. Cause: the material circulation step did not return it, the version ledger did not record this omission, and subsequent nodes cannot parse the signature field.
- 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 request body fields are inconsistent with the interface agreement.
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 one sample to confirm that the version number and references in responseData are updated synchronously.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- In the variables panel, check the source of each placeholder, confirm whether it comes from a global variable, system variable, or the output of a preceding node, and check the value source of the
Authorizationrequest header. - Use one sample request to compare the returned fields, check that the request body fields are consistent with the external interface agreement, and record the array length and the tokens budget of the reference text.