What this category's data looks like
Vocational training subsidy application materials mainly consist of training class filing records, sign-in records, and completion assessment forms. They come from training institutions and assessment units, and are updated in stages along with class opening, daily sign-in, and completion assessment. Class filing records include the class name, start and end dates, student roster, and institutional seal; sign-in records include the date, name, sign-in signature, and supplementary sign-in explanation; completion assessment forms include the assessment date, score, assessor signature, and institutional receipt. When entering workflow orchestration, the class filing record serves as the class baseline for the progress table, the sign-in records serve as the daily basis for attendance statistics, and the completion assessment form serves as the closing material for the completion criteria and signature verification. Together, the three support progress records and statistical verification.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress table and statistical criteria description" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training class filing record | Whether the class name, start and end dates, student roster, and institutional seal align item by item with the sign-in records and completion assessment form | In the node, check the options and branch connections one by one, reference nodeId to see which branch this class enters, and compare the names and dates in the three materials |
| Sign-in records | Whether the daily sign-in date, name, signature, and supplementary sign-in explanation are consistent with the class filing roster and the number of people in the completion assessment form | In subsequent nodes, reference variables to read the selection result variable and run a trial once, checking the names, quantities, and dates in the sign-in records and filing roster |
| Completion assessment form | Whether the assessment date, score, assessor signature, and institutional receipt are complete, and whether they correspond to the attendance criteria in the sign-in records | Trigger a user selection node once, check the node status in the run record, and verify whether the assessment form signature and receipt are consistent with the sign-in attendance criteria |
Three common errors
- Phenomenon: The same student's name, quantity, and date do not match between the class filing record and the sign-in records. Cause: The two materials were entered separately, without item-by-item alignment by class and date.
- Phenomenon: The version of the completion assessment form was not synchronized and still references the old class roster. Cause: After the material was updated, the workflow node was not re-entered to trigger the branch, and subsequent nodes continued to use the old variables.
- Phenomenon: Sign-in records lack signatures or the completion assessment form lacks a receipt. Cause: After the interaction is completed, the process stops and does not continue along the corresponding branch, and the materials enter the weekly or monthly report before being closed out.
How to verify the setup
This feature acceptance: Run trials for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that the same session does not repeatedly enter the interaction.
Business test: Use one week of records to check the totals, see whether the criteria and exceptions are clearly stated, and confirm that the record count and statistical count match and that the criteria are written in the header.
- In the node, check the options and branch connections one by one, trigger a user selection node once, and view the node status and branch direction in the run record.
- In subsequent nodes, reference
variablesto read the selection result variable and run a trial once, checking whether the one-week record totals are consistent with the statistical criteria description.