What this category's data looks like
This category's data primarily consists of student registration forms, teaching plans, and skills training records. Student registration forms record student identity and enrollment status, teaching plans specify course and class-hour arrangements, and skills training records document training items and assessment results. The three types of materials are updated by semester and academic year, with fields including name, quantity, date, and signature. When entering workflow orchestration, student registration forms are used to identify the visitor's identity and class affiliation, teaching plans are used to determine the scope of visible courses, and skills training records are used to limit the level of access to training data. Material versions must be synchronized, and signatures and receipts must be complete; otherwise, the authorization scope and external entry points may be mismatched.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The externally accessible entry points and authorization scope 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 status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | The identity fields and class affiliation must be consistent with the class name and date in the teaching plan, and signatures and receipts must be complete | After the user selection node, reference variables and nodeId, run a trial with a restricted identity, and check the branch direction corresponding to this material in the run record |
| Teaching plan | Course names, quantities, and dates must correspond item by item with the skills training records, and versions must be synchronized | Run trials for each option one by one, and check in the run record whether the interaction state and selection result variables of the teaching plan-related branch are passed to subsequent nodes |
| Skills training record | Training item names, quantities, and dates must match the class information in the student registration form; if signatures or receipts are missing, it is not visible | Reference variables in subsequent nodes and run a trial, check whether the visible scope of the training record matches the settings, and that unauthorized access is not visible |
| User selection node | Each option corresponds to one branch, and the options and branch connections must be checked one by one | Trigger once, view the node status and branch direction in the run record, and confirm that no default branch is mistakenly taken |
Three common errors
- Symptom: The same student's name or date does not match between the student registration form and the skills training record. Cause: The two materials are entered separately, without field-level verification and receipt confirmation.
- Symptom: The teaching plan has been updated, but the skills training record is still the old version. Cause: Versions are not synchronized, and subsequent nodes continue execution along the old branch.
- Symptom: When accessing with a restricted identity, training records beyond the authorized scope are visible. Cause: Options and branch connections are mismatched, or the selection result variable is not correctly passed to subsequent nodes.
How to verify the setup
This feature acceptance: Run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that no default branch is mistakenly taken.
Business test: Access once with a restricted identity, check whether the visible scope matches the settings, and that unauthorized access is not visible.
- In the user selection node, check the options and branch connections one by one, and after triggering once, view the node status in the run record.
- Reference
variablesandnodeIdin subsequent nodes and run a trial, check whether the fields, dates, and signatures of the student registration form, teaching plan, and skills training record are consistent.