What this category's data looks like
Scheduling and class-consumption in training institutions involves three types of materials: class schedules, class-consumption records, and schedule-change applications. Sources are academic affairs system exports and offline signed receipts. The update cadence is triggered weekly or per class session. Fields include course name, class date, number of class hours, teacher signature, student confirmation, and reason for schedule change. The class schedule is the scheduling baseline, the class-consumption record is the actual consumption voucher, and the schedule-change application is the basis for changes. When the three enter the workflow, the class schedule serves as master data, the class-consumption record serves as the object to be checked, and the schedule-change application serves as the change trigger source. The version ledger must record the current version number, the archive location of old versions, and the knowledge base or external document entries that reference that version. If the name, quantity, or date of the same record do not match across two materials, or if versions are not synchronized, or if signed receipts are missing, the ledger and change records will be distorted. When the materials enter the user selection node, each serves as the basis for branch judgment and does not directly produce a finished product.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. 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 |
|---|---|---|
| Class schedule | Whether the course name, class date, number of class hours, and teacher signature are consistent with the class-consumption record | Check the fields, dates, and signatures of the class schedule and class-consumption record; verify options and branch connections one by one in the node; confirm that options and branches correspond one-to-one |
| Class-consumption record | Whether the name, quantity, and date of the same record match across the two materials | Trigger a user selection node once, view the node status in the run record, and confirm that the interaction state is recorded and the selection result variable has been passed to subsequent nodes |
| Schedule-change application | Whether the reason for schedule change, date, and student confirmation receipt are complete, and whether the version is synchronized | Reference this variable in a subsequent node and run a trial once; check whether the schedule-change application triggers a version update and whether the old version is traceable |
| Version ledger | Whether the current version is unique, the old version is traceable, and reference synchronization holds | Check whether the version number and knowledge base or external document reference entries are updated synchronously, and confirm that no version is unsynchronized |
Three common errors
- Symptom: The course name, number of class hours, and class date of the same record do not match between the class schedule and the class-consumption record. Cause: The two materials are maintained separately, and fields and signatures are not uniformly checked at the user selection node.
- Symptom: A schedule-change application has been submitted, but the version ledger still shows the old version, and the knowledge base reference is not synchronized. Cause: The version update did not go through branch continuation, the old version was not archived, and the reference entries were not linked.
- Symptom: The class-consumption record lacks student confirmation or a teacher-signed receipt. Cause: After the interaction state is recorded, receipt completeness is not checked according to the branch, and subsequent nodes directly use unsigned materials.
How to verify the setup
Acceptance for this feature: run a trial for each option, 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 variables and nodeId are queryable in the run record.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and confirm that the current version is unique, the old version is traceable, and references are synchronized.
- In the node, check options and branch connections one by one, confirm that each option corresponds to one branch, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once; check whether the version ledger and change records are completed by subsequent nodes continuing execution according to the branch.