What this category's data looks like
The materials for vocational training subsidy applications typically include three types: training class filing forms, attendance records, and completion assessment forms. The sources are training institutions, instructors, and assessors, and the update cadence advances by class session, by daily attendance, and by completion batch. The class filing form provides the course name, class start date, student roster, and institutional seal; the attendance record provides the daily attendees, sign-in time, and proxy sign-in notes; the completion assessment form provides the assessment subjects, scores, assessment date, and assessor signature. When these three types of materials enter workflow orchestration, the filing form serves as the branch starting point that determines the direction of subsequent nodes, while the attendance record and assessment form serve as the basis for subsequent nodes to continue execution along the branch, each retaining fields, dates, and signature traces for item-by-item verification against the handover checklist.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters the interaction 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 |
|---|---|---|
| Training class filing form | Whether the name, quantity, date, and signature are consistent with the attendance record and completion assessment form | Compare course name, student count, class start date, and institutional seal item by item, check the options and branch connections one by one in the node, and use variables to reference the selection result and run a trial once |
| Attendance record | Whether the attendees, sign-in date, and proxy sign-in notes match the filing form and assessment form | Check the sign-in personnel against the filing roster by day, inspect for missing signatures or receipts, trigger once to view the node status in the run records, and confirm that nodeId corresponds to the branch direction |
| Completion assessment form | Whether the assessment subjects, scores, assessment date, and assessor signature are consistent with the filing form and attendance record | Check the assessment date and completion batch, inspect whether the name, quantity, and date of the same record are inconsistent across the two materials, reference variables in subsequent nodes, and run a trial once |
| Deployment state and operation records | Whether the version, connection, and task records are consistent | Check the version number, connection items, and task records item by item against the handover checklist, confirm that the process has not stalled after the interaction is completed, and that the same session has not repeatedly entered the interaction |
Three common errors
- Symptom: The same student's name, count, and date do not match between the filing form and the attendance record. Cause: The two materials were entered separately, and fields and signatures were not uniformly checked by class session.
- Symptom: The deployment version is not synchronized, and the node options and branch connections still follow the old version. Cause: The version number and connection items were not recorded during handover, and the run records are inconsistent with the current configuration.
- Symptom: The completion assessment form is missing the assessor's signature or the institutional receipt. Cause: Signatures were not fully collected during the material circulation stage, and the missing item was only discovered during the item-by-item check against the handover checklist.
How to verify the setup
Acceptance of this feature: Run a trial for each option, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and use variables and nodeId to locate records.
Business testing: Check once item by item against the handover checklist, see which record is missing, and compare the fields, dates, and signatures of the filing form, attendance record, and completion assessment form.
- Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and confirm that the interaction state is recorded.
- Reference the selection result variable in subsequent nodes and run a trial once, checking whether selecting a certain option still follows the default branch and whether the process stalls after the interaction is completed.