What this category's data looks like
Vocational college skills competition organization materials fall into three categories: competition regulations, registration forms, and training plans. The regulations provide the project name, group, date, and signature field; the registration forms provide contestants, instructors, team counts, and receipts; the training plans list weeks, class hours, venues, and coach signatures. The three types of materials are updated according to the rhythm of pre-competition registration, weekly training, and post-competition summary, with fields structured around names, quantities, dates, and signatures. When entering workflow orchestration, the regulations are the source of definitions, the registration forms are the source of records, and the training plans are the source of process, and together the three support progress records and statistical verification, ultimately forming a progress table and statistical definition notes, which enter the weekly or monthly report.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "progress table and statistical definition notes" are 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 | Whether the name, date, and signature are consistent with the registration forms and training plans | Check item by item the project name, group, date, and signature field, verify the options and branch connections one by one in the node, and use nodeId to locate the node |
| Registration forms | Whether the contestants, team counts, and receipts match the training plans | Check the quantities and receipt signatures, reference variables in subsequent nodes and run a trial once, and see whether the selection result variable has been passed to the subsequent nodes |
| Training plans | Whether the weeks, class hours, venues, and coach signatures match the dates in the regulations | Check class hours and venues week by week, trigger an interaction state once, and view the node status in the run records |
| Progress table and statistical definition notes | Whether the header clearly states the definitions and exceptions, and whether the record counts and statistical counts match | Use one week of records to check the totals, see whether the definitions and exceptions are clearly stated, and check the branch directions |
Three common errors
- Symptom: the same contestant's name and quantity do not match between the registration form and the training plan. Cause: the two materials are filled out separately, without unifying the definitions according to the regulation fields.
- Symptom: after the regulations are updated, the registration form and training plan still use the old version. Cause: the versions are not synchronized, and the node branch does not follow the latest option.
- Symptom: the training plan lacks a coach signature or the registration form lacks a receipt. Cause: the materials are not returned, and after the interaction is completed the process stops and does not continue execution.
How to verify the setup
Feature acceptance: run trials option by option, check the branch directions and interaction states in the run records, confirm that each option corresponds to one branch, and use nodeId and variables to check that the selection result variable has been passed to the subsequent nodes.
Business test: use one week of records to check the totals, and see whether the definitions and exceptions are clearly stated.
- In the node, verify the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Reference
variablesin subsequent nodes and run a trial once, and confirm that the selection result variable has been passed to the subsequent nodes.