What this category's data looks like
The materials for vocational college skills competition organization are based on the competition regulations, with registration forms and training plans as process records; the three must mutually corroborate in names, quantities, dates, and signatures. The regulations contain the event name, group, time nodes, and signature/seal fields; the registration form contains contestant names, student IDs, instructors, and acknowledgments; the training plan contains phase arrangements, attendance, and coach signatures. Materials enter in batches according to competition schedule nodes: before the competition, registration and regulations are updated; during the competition, training and attendance are updated; after the competition, they are archived for review. When entering this function, the regulations serve as the comparison baseline, the registration form and training plan serve as the objects to be verified, and the exception list and review conclusions are completed by subsequent nodes continuing execution along branches, and are handed to the responsible person for handling.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are completed by subsequent nodes continuing execution along branches. 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 |
|---|---|---|
| Competition regulations | Whether the event name, group, date, and signature/seal fields correspond item by item with the registration form and training plan, and whether the version number and effective date are consistent | Extract the regulation fields and compare them with the same-named fields in the registration form and training plan; check the options and branch connections one by one in the node, and use nodeId to locate the node |
| Registration form | Whether contestant names, student IDs, instructors, competition events, and acknowledgment signatures are complete, and whether the names, quantities, and dates of the same record match those in the regulations and training plan | Check the three materials item by item for each contestant, and mark records missing signatures or acknowledgments; reference variables in subsequent nodes and run a trial once |
| Training plan | Whether the phase arrangements, attendance dates, coach signatures, and regulation time nodes are synchronized; list separately any entries whose versions are not synchronized or whose dates do not match | Compare the date ranges of the training plan and regulations, and check the signatures in the attendance records; trigger a node once and view the node status in the run records |
Three common errors
- Phenomenon: the same contestant's name or competition event does not match between the registration form and training plan. Cause: the two materials were entered separately, and field-level comparison was not performed using the competition regulations as the baseline.
- Phenomenon: the regulations have been updated while the registration form and training plan still use the old version. Cause: versions were not synchronized, and cross-checking of version numbers and effective dates was lacking.
- Phenomenon: the review conclusion lacks the reviewer's signature or acknowledgment. Cause: the review step did not require signature traceability, so exception records cannot be traced back to the source materials.
How to verify the setup
This function's acceptance: run trials for each option one by one, check the branch directions and interaction states in the run records, confirm that the options correspond to the correct branches and that the process continues after interaction is completed, and check whether nodeId and variables can be referenced in subsequent nodes.
Business test: create an exception record and see whether it can be traced back to the source materials.
- Check the options and branch connections one by one in the node, and after triggering once, view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the branch direction is consistent with the interaction state record.