What this category's data looks like
Vocational training subsidy application materials cover three categories: training class filing records, attendance records, and completion assessment forms. Class filing records include institution name, course name, class start date, student roster, and approval signature; attendance records include daily attendance date, student name, attendance status, and supervising staff signature; completion assessment forms include assessment date, student scores, assessment conclusion, and assessor signature. Materials are organized by training institutions by class and submitted period by period, with the update cadence synchronized with class start batches. When the three material types enter workflow orchestration, their roles differ: class filing records determine the range of classes eligible for application, attendance records support verification of attendance authenticity, and completion assessment forms correspond to subsidy disbursement conditions. Field comparison focuses on names, quantities, dates, and signature receipts. The same record often appears in two materials with inconsistent name spellings, mismatched headcounts or class hours, dates misaligned across months, unsynchronized versions, or missing signatures or receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The externally available entry points and authorization scope are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| User selection node | Each option corresponds to one branch; options and branch connections correspond one-to-one | In the node, check each option and branch connection one by one; after a trial run, review the node status and branch direction in the run records to confirm that the selection result variable has been passed to subsequent nodes |
| Class filing records | Institution name, course name, class start date, student roster, and approval signature are consistent item by item with attendance records and completion assessment forms | Compare names, quantities, dates, and signatures for the same class across the three materials; return for correction any missing signatures or receipts |
| Attendance records | Daily attendance date, student name, attendance status, and supervising staff signature are verifiable | Check attendance dates and student roster day by day by class; inspect records with unsynchronized versions or mismatched dates |
| Completion assessment forms | Assessment date, student scores, assessment conclusion, and assessor signature are verifiable | Check the date chain of the assessment date against class filing records and attendance records; confirm that signatures and receipts are complete |
Three common errors
- Phenomenon: The student headcount for the same class does not match between class filing records and attendance records. Cause: The roster version was not synchronized, and subsequently added personnel were updated in only one material.
- Phenomenon: The assessment date on the completion assessment form is misaligned with the last-day date in attendance records. Cause: The two materials were organized by different batches, and the date fields were not checked uniformly.
- Phenomenon: Class filing records or completion assessment forms lack approval signatures or receipts. Cause: Signature documents were not collected during material circulation, and completeness checks were not performed during archiving.
How to verify the setup
This feature acceptance: run a trial for each option, check the branch direction and interaction state in the run records, confirm that options and branches correspond one-to-one, and that the selection result variable has been passed to subsequent nodes, where it can be referenced using variables and nodeId and a trial run performed once.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the user selection node, check each option and branch connection one by one; after a trial run, review the node status and branch direction in the run records.
- Reference the selection result variable in subsequent nodes, locate the source using
variablesandnodeId, and perform a trial run once to confirm that the branch continues execution.