What this category's data looks like
The materials for the vocational training subsidy claim category mainly fall into three types: training class opening filings, attendance records, and completion assessment forms. Opening filings come from the filing information submitted by training institutions before the class starts, including the course name, start and end dates, student roster, and the signature of the person in charge; attendance records are generated daily, recording students' attendance dates and sign-in handwriting; completion assessment forms are formed after the assessment ends, including assessment scores, assessment dates, and the signature of the assessor. The three types of materials update at different rhythms: filings are submitted once before the class starts, attendance records accumulate day by day, and assessment forms are completed at the time of completion. When entering the exception tracing and manual review function, filings serve as the baseline source, while attendance records and assessment forms serve as comparison sources, used to check whether the name, quantity, and date of the same record are consistent across the two materials, and to check whether signatures or receipts are complete.
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 "exception list and review conclusion" is completed by subsequent nodes parsing the response, or by an external system handling it as agreed. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Training class opening filing | The course name, start and end dates, student roster, and signature of the person in charge in the filing must correspond item by item with the attendance records and completion assessment forms | In the request preview, view the full rendered address, and check whether the filing fields are consistent with the name, quantity, and date in the other two materials |
| Attendance records | The sign-in dates and attendance handwriting should fall within the start and end dates of the filing, and match the number of students on the roster | Check the request header names and the sources of their values, confirm that the authentication information is passed in as required by the external system, and then compare the sign-in dates with the filing dates |
| Completion assessment form | The assessment scores, assessment dates, and assessor signatures should be complete, and match the names and quantities in the filing and attendance records | Use a sample request to compare the response, check whether the assessment form fields are consistent with the agreement of the external interface, and confirm that signatures or receipts are not missing |
| Variable sources | Every placeholder in the request address, request headers, and request body can be traced to a specific origin | In the variables panel, check the source of each placeholder, and confirm that variables, Authorization, and responseData can all be resolved into actual values |
Three common errors
- Symptom: The same student's name is written differently in the filing and the attendance records, and the quantities do not match. Cause: The two materials are entered in different stages, and field alignment and version synchronization were not performed.
- Symptom: The completion assessment form lacks the assessor's signature or receipt. Cause: The signature was not completed in time after the assessment ended, and no completeness check was performed when archiving the materials.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The request header authentication information was not passed in as required by the external system, or the request body fields are inconsistent with the interface agreement.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the value sources of responseData and Authorization are correct.
Business test: create an exception record, see whether it can be traced back to the source material, and check whether the exception list and review conclusion are supported by original records and the reviewer's signature.
- In the request preview, check the full rendered address, request headers, and request body, and confirm that all
variablesplaceholders can be resolved into actual values. - Use a sample request to compare the returned fields, and check whether the names, quantities, and dates in the exception list can correspond to the filing, attendance records, and completion assessment form.