What this category's data looks like
The material on this page comes from the course scheduling and course consumption scenario of training institutions, and includes three types: class schedules, course consumption records, and schedule change requests. Class schedules are updated weekly or monthly, and their fields include course, class, teacher, classroom, time slot, and date; course consumption records are generated per session, and their fields include student, course, number of class hours, date, and signature; schedule change requests are submitted as needed, and their fields include original time slot, target time slot, applicant, and receipt. When the material enters workflow orchestration, the class schedule serves as the baseline scheduling object, the course consumption record serves as the consumption verification object, and the schedule change request serves as the change trigger object. The dates, names, and quantities of the three must be consistent, versions must be synchronized with scheduling adjustments, and signatures or receipts serve as handover credentials. The update rhythm is periodic updates for class schedules, per-session recording for course consumption, and immediate requests for schedule changes; at handover, consistency is determined by the alignment of versions, connections, and task records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The handover-ready deployment status and operation records are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters the 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 |
|---|---|---|
| Class schedule | The class schedule fields, dates, and signatures must be aligned item by item with the course consumption records and schedule change requests | Check the options and branch connections one by one in the node, reference variables, and run a trial once |
| Course consumption record | The name, quantity, and date of the course consumption record must be consistent with the class schedule and schedule change requests | Reference this variable in subsequent nodes and run a trial, then check the node status in the run records |
| Schedule change request | The original time slot, target time slot, applicant, and receipt of the schedule change request must be synchronized with the class schedule version | Trigger a user selection once, and check the branch direction and interaction status record corresponding to nodeId |
| User selection node | Each option corresponds to one branch, and the interaction status and selection result variable must be recorded | Trigger once, and check the node status and branch direction in the run records |
Three common errors
- Symptom: The name, quantity, and date of the same course consumption record do not match between the class schedule and the schedule change request. Cause: The materials are updated separately, and fields and signatures are not checked against a unified version.
- Symptom: The class schedule has already been adjusted, but the course consumption record is still executed according to the old version. Cause: The version was not synchronized, and the consistency of connections and task records was not checked at handover.
- Symptom: The schedule change request lacks the applicant's signature or receipt, and the handover form is missing items. Cause: The signature and receipt fields were not checked item by item when the material entered the workflow.
How to verify the setup
Acceptance of this feature: run a trial for each option one by one, and check the branch direction and interaction status in the run records; check whether variables and nodeId are correctly referenced by subsequent nodes.
Business test: check item by item once according to the handover form to see which record is missing; check whether the fields, dates, and signatures of the class schedule, course consumption records, and schedule change requests are consistent.
- Check the options and branch connections one by one in the node, trigger a user selection once, and check the node status and branch direction in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, check whether
variablesandnodeIdare passed in, and check missing records item by item according to the handover form.