What this category's data looks like
Materials for course scheduling and lesson consumption in training institutions mainly consist of class schedules, lesson consumption records, and schedule change requests. Sources include academic affairs system exports, instructor backfills, and campus supervisor-signed documents. The update cadence rolls forward by week, with schedule changes taking effect immediately. Class schedules carry fields for class, time slot, classroom, and teacher; lesson consumption records carry student, number of lesson hours, consumption date, and signature; schedule change requests carry the original time slot, target time slot, approver, and receipt. When these three types of materials enter workflow orchestration, the class schedule serves as the baseline source, lesson consumption records serve as consumption evidence, and schedule change requests serve as the basis for changes. Together they support the generation of a unified terminology glossary and a comparison draft, and expose field differences in branch routing and interaction state records, so that subsequent nodes can continue execution along the branches.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch routing and interaction state records. The unified terminology glossary and comparison draft are completed by subsequent nodes continuing execution along the branches. When the user selection 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 |
|---|---|---|
| Class schedule | The class, time slot, classroom, and teacher in the class schedule fields must be checked item by item against the lesson consumption records and schedule change requests. The name, quantity, and date of the same record must be traceable back to the source text. | In the node, check the options and branch connections one by one, use nodeId to locate the class schedule branch, and after a trial run, view the node status in the run records. |
| Lesson consumption record | The student, number of lesson hours, consumption date, and signature in the lesson consumption record must be consistent with the class schedule and schedule change request. A missing signature or receipt is regarded as not closed-loop. | In subsequent nodes, reference variables and run a trial once. Check whether the selection result variable has been passed to subsequent nodes, and confirm that the consumption quantity and date match. |
| Schedule change request | The original time slot, target time slot, approver, and receipt in the schedule change request must be synchronized with the class schedule version. If the version is not synchronized or the dates do not match, it is judged inconsistent. | Trigger a user selection node once, view the node status in the run records, and check whether the schedule change branch routing and interaction state records correspond to the options. |
Three common errors
- Symptom: The number of lesson hours and dates for the same lesson consumption record do not match between the class schedule and the schedule change request. Cause: The two materials are updated separately and are not checked against the same version as the baseline.
- Symptom: The schedule change request has already overridden the class schedule, but the lesson consumption record is still settled according to the old time slot. Cause: The version is not synchronized, and the branch still follows the default path.
- Symptom: A lesson consumption record missing a signature or receipt still proceeds to external release. Cause: After the interaction is completed, the receipt field is not checked, and the process stalls without being discovered.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, check the branch routing and interaction state in the run records, and confirm that nodeId, variables, and option branches correspond one to one.
Business test: sample three terms and check whether their usage is consistent throughout the entire document. The same term must be consistent throughout the entire document, and the translated name must be traceable back to the source text.
- In the node, check the options and branch connections one by one, trigger a user selection node once, and view the node status in the run records.
- In subsequent nodes, reference the selection result variable and run a trial once. Check whether
variableshas been passed to subsequent nodes, and confirm the branch routing and interaction state records.