What this category's data looks like
The material verification and discrepancy localization for vocational college skills competition organization revolves around three types of materials: competition regulations, registration forms, and training plans. The competition regulations are published by the organizer before the competition, containing the event name, group, date, and signature field; the registration form is submitted by the participating institution, containing contestant names, number of participants, ID numbers, and instructor signature; the training plan is updated weekly by the instructor, containing training subjects, class hours, phase dates, and review signature. The three types of materials have different update rhythms: regulations are revised with notices, registration forms are returned multiple times before the registration deadline, and training plans roll forward according to training cycles. After entering the workflow, the competition regulations serve as the baseline ledger, while the registration form and training plan serve as materials to be verified. Fields such as names, quantities, dates, and signature receipts are compared field by field to locate the discrepancy fields of the same record in the two materials, forming a discrepancy list to be confirmed by the reviewer and written 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 a node is triggered, the conversation enters an 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 |
|---|---|---|
| Competition regulations | Event name, group, date, and signature field are consistent between the regulations and the registration form | Compare the regulations and registration form field by field, check whether the variables reference points to the same record, and record discrepancy fields |
| Registration form | Contestant names, number of participants, instructor signature, and receipt are complete | Check options and branch connections one by one in the node, check the branch direction corresponding to nodeId, and mark items missing signature or receipt |
| Training plan | Training subjects, class hours, phase dates, and review signature are synchronized with the ledger | Trigger one interaction, view the node status in the run record, check whether variables have been passed to subsequent nodes, and run a trial once |
| Version record | The version number and revision date of the same record in the two materials match | Compare version numbers and revision dates, mark items whose versions are not synchronized, and write them into the discrepancy list pending review |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the regulations and the registration form. Cause: The two materials are filled in by different roles at different times, lacking unified field mapping and field-by-field comparison.
- Phenomenon: The training plan has been updated, but the registration form still references the old date and class hours. Cause: The version is not synchronized; after the material is returned, re-verification is not triggered, and old fields continue to participate in the comparison.
- Phenomenon: The registration form lacks the instructor signature or receipt, but the discrepancy list is still submitted. Cause: The signature and receipt fields are not included in the verification scope, and the reviewer cannot locate the missing items.
How to verify the setup
Acceptance of this function: run trials option by option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and check the reference relationship between nodeId and variables.
Business test: use one real record to find fields inconsistent with the ledger, compare names, quantities, dates, and signatures in the competition regulations, registration form, and training plan, and write them into the discrepancy list.
- Check options and branch connections one by one in the node, trigger one interaction, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the discrepancy list continues execution according to the branch and writes back the reviewer's confirmation result.