What this category's data looks like
Vocational training subsidy claim materials mainly consist of training class filing forms, attendance records, and completion assessment forms. They come from training institution declarations and competent department archives, are updated by class session, and the fields include student name, ID number, training program, class start date, completion date, class hours, signature, and receipt. The class filing form determines the subsidy recipients and program scope, the attendance records reflect attendance and class hours, and the completion assessment form confirms the assessment results and completion eligibility. After these three types of materials enter the workflow, the node first triggers user selection, then flows by branch to the exception tracing and manual review step, and the exception list and review conclusion are completed by subsequent nodes continuing execution by branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branch), outputting the branch direction and interaction status record. The "exception list and review conclusion" is then completed by subsequent nodes continuing execution by branch. When the user selection node is triggered, the conversation enters the interaction 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 form | Check the student name, ID number, training program, class start date, and institution signature, and determine whether they are consistent with the attendance records and completion assessment form | In the node, check the options and branch connections one by one, reference variables to compare the fields of the filing form and attendance records, and view the run record corresponding to nodeId |
| Attendance record | Check the student name, attendance date, number of class hours, and personal signature, and determine whether the name, quantity, and date match those in the class filing form and completion assessment form | Trigger one user selection, view the node status in the run record, and check the dates and quantities in the attendance record and completion assessment form |
| Completion assessment form | Check the student name, assessment result, completion date, and assessor signature, and determine whether it is version-synchronized with the class filing form and attendance records and whether the receipt is complete | In a subsequent node, reference the selection result variable and run a trial, and check the names, dates, and signatures in the completion assessment form and class filing form |
Three common errors
- Phenomenon: The same student's name, quantity, and date do not match across two materials. Cause: Field definitions were not unified at declaration, and no cross-comparison was performed after entry.
- Phenomenon: The class filing form and completion assessment form are not version-synchronized, and the old version is still in circulation. Cause: After the materials were updated, the node selection was not triggered again, and the branch still followed the old path.
- Phenomenon: The attendance record lacks a signature or receipt, and the review conclusion has no signature support. Cause: After the interaction is completed, the process stops, and subsequent nodes do not continue execution.
How to verify the setup
Acceptance of this function: 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 run a trial once referencing that variable in a subsequent node.
Business test: Create one exception record, see whether it can be traced back to the source material, and check the name, quantity, date, and signature of that exception in the class filing form, attendance record, and completion assessment form.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and avoid still following the default branch after selecting an option.
- Trigger one user selection, view the node status and
nodeIdin the run record, check thevariablesreferences, and confirm that the process continues execution after the interaction is completed.