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. The class filing record contains the institution name, training occupation, class start date, and filing number; the sign-in record contains the trainee name, sign-in date, and signature; the completion assessment form contains the trainee name, assessment score, completion date, and assessment signature. The materials come from training institutions and assessment institutions, and are updated in batches by class; the same class may produce multiple versions due to supplementary entries or corrections. After entering the workflow, the filing record assumes the role of defining the class and personnel scope, the sign-in record assumes the role of verifying attendance facts, and the completion assessment form assumes the role of verifying completion results; together, the three support the generation of the discrepancy list and subsequent review write-back.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The discrepancy list is 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 |
|---|---|---|
| Training class filing record | For the same class, the institution name, training occupation, and class start date in the filing record and sign-in record are consistent | In the node, check the options and branch connections one by one, compare the filing number and class identifier, and flag fields with inconsistent names or dates |
| Sign-in record | For the same trainee, the name, sign-in date, and signature in the sign-in record and completion assessment form are complete and consistent | Reference the selection result variable and run a trial once, check names and dates one by one, and mark records missing signatures or receipts |
| Completion assessment form | For the same trainee, the name, completion date, and assessment signature in the assessment form and filing record are consistent and the versions are synchronized | Trigger once to view the node status in the run record, compare the assessment form version with the filing record version, and flag fields that are not synchronized |
| User selection node | Each option corresponds to one branch, and the selection result variable has been passed to subsequent nodes | Reference variables in subsequent nodes and check the branch corresponding to nodeId, confirming that the process continues after the interaction is completed |
Three common errors
- Symptom: The name or date of the same trainee does not match between the sign-in record and the completion assessment form. Cause: The two materials are entered in different steps, and no field comparison for the same object was performed.
- Symptom: The filing record has been corrected, but the sign-in record is still the old version. Cause: The versions are not synchronized, the material update rhythms are inconsistent, and a version verification step is missing.
- Symptom: The completion assessment form is missing the assessment signature or receipt. Cause: The signature step is not closed-loop, and missing items were not flagged when the materials entered the workflow.
How to verify the setup
Feature acceptance: Run a trial for each option, check the branch direction and interaction state in the run record, confirm that each option follows the corresponding branch, that the process continues after the interaction is completed, and that the same session does not repeatedly enter the interaction; also check that the selection result variable has been passed to subsequent nodes, and verify the correspondence between variables and nodeId.
Business test: Use one real record to find fields inconsistent with the ledger, and verify the name, quantity, date, and signature of that record in the class filing record, sign-in record, and completion assessment form.
- In the node, check the options and branch connections one by one, trigger once to view the node status in the run record, and confirm that the interaction state is recorded.
- Reference
variablesin subsequent nodes and check the branch corresponding tonodeId, run a trial once to confirm that the selection result variable has been passed and the process continues.