What this category's data looks like
This category's data is organized around three main lines of materials: student registration forms, teaching plans, and skills training records. Student registration forms carry fields for student identity, class, and registration date; teaching plans carry fields for course name, week number, and teaching progress; skills training records carry fields for training item, quantity, date, and signed receipt. Materials are submitted weekly or monthly by academic affairs and the training workshop, with an update cadence synchronized to the teaching weeks; signatures and receipts are a precondition for validity. When entering workflow orchestration, student registration forms provide the personnel and class baseline, teaching plans provide the progress reference, and skills training records provide the actual completed quantity; together the three support the generation and verification of the progress table and statistical scope description.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The progress table and statistical scope description are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | Whether name, class, registration date, and signature are consistent with the teaching plan | Compare name and class fields one by one, verify registration date and signature, and use variables to record discrepancies |
| Teaching plan | Whether course name, week number, and teaching progress match the skills training records | Verify course name and progress by week number, check whether versions are synchronized, and use nodeId to locate the branch |
| Skills training record | Whether training item, quantity, date, and receipt are complete and match the plan | Verify quantity and date, check signature and receipt, and reference variables in subsequent nodes for a trial run |
| Progress table and statistical scope description | Whether record counts and statistical counts match, and whether the scope is written in the header | Use one week of records to verify the totals, check whether exceptions are clearly written, and verify the scope fields in the header |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the student registration form and the skills training record. Cause: The two materials are entered separately without field mapping and cross-checking.
- Symptom: The teaching plan version is not synchronized, and old week numbers are still referenced. Cause: The update cadence is not unified, and the branch direction is not reconfirmed when the version changes.
- Symptom: Skills training records lack a signature or receipt but are still counted in the totals during statistics. Cause: The material validity conditions are not checked in advance within the verification actions.
How to verify the setup
Feature acceptance: Try each option one by one, verify the branch direction and interaction state in the run records, confirm that the selection result variable variables has been passed to subsequent nodes, and use nodeId to locate the branch connections.
Business test: Use one week of records to verify the totals, see whether the scope and exceptions are clearly written, and confirm that record counts and statistical counts match.
- In the node, verify the options and branch connections one by one, and confirm that each option corresponds to one branch.
- Trigger a user selection node once, and check the node state and interaction state in the run records.