What this category's data looks like
This category's data covers three types of materials involved in vocational college skills competition organization: competition regulations, registration forms, and training plans. The sources are the competition event executive committee and the college's academic affairs and training management departments, and the update cadence changes as the competition schedule advances and rules are fine-tuned. Competition regulations contain the event name, group, date, signature fields, and attachment references; registration forms contain competitor names, ID numbers, competition events, supervising instructors, and receipts; training plans contain phases, class hours, venues, and responsible person signatures. When these three types of materials enter workflow orchestration, the competition regulations serve as the primary basis driving branches, while registration forms and training plans serve as supporting materials that flow with the branches to the corresponding nodes. Fields and dates are passed between nodes, and signatures and receipts are collected at subsequent nodes.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The version ledger and change records are completed next by subsequent nodes continuing execution along the branches.
| Object | Check | Verification action |
|---|---|---|
| Competition regulations | Whether fields, dates, and signatures are consistent with the registration form and training plan | Check options and branch connections one by one in the nodes, trigger one run to view node status in the run records, and reference variables in subsequent nodes for a trial run |
| Registration form | Whether the name, quantity, and date of the same record match across the two materials | Check the direction records of the branch corresponding to nodeId, and confirm that the selection result variable has been passed to subsequent nodes |
| Training plan | Whether versions are out of sync, or signatures or receipts are missing | Compare against the three items of unique current version, traceable old versions, and synchronized references, and check branch directions and interaction state records one by one |
Three common errors
- Symptom: the same competitor name is written differently in the registration form and the training plan. Cause: the two materials are entered separately, and no field comparison is done on the node branches.
- Symptom: after the competition regulation date is changed, the registration form still shows the old date. Cause: the version is not synchronized, the old version is not marked, and references are not updated with the branch.
- Symptom: the training plan lacks the responsible person's signature or receipt. Cause: the signature field is not included in node checks, and it is not backfilled after interaction is completed.
How to verify the setup
Feature acceptance: run trial runs for each option one by one, check the branch directions and interaction states in the run records, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- Check options and branch connections one by one in the nodes, and trigger one run to view node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial run once to confirm that the branch directions are consistent with the interaction state records.