What this category's data looks like
In the scheduling and class-hour deduction scenario of training institutions, materials usually include three types: class schedules, class-hour deduction records, and schedule change requests. Class schedules are generated on a weekly or monthly cycle, with fields including class, teacher, time slot, and classroom; class-hour deduction records are registered per session, with fields including student, course, date, number of class hours, and signature; schedule change requests are generated per event, with fields including original time slot, new time slot, approver, and receipt. The three types of materials have different update rhythms: class schedules are reissued as scheduling adjustments occur, class-hour deduction records are entered immediately after class, and schedule change requests are archived after approval. After entering the workflow, the class schedule assumes the role of baseline scheduling, the class-hour deduction record assumes the role of actual occurrence, and the schedule change request assumes the role of change basis. Business basis queries require that each conclusion can be traced back to the original text location of the specific material, and that the material is confirmed to be the current version.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. Basis items that can be traced back to the original text must be continued by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Whether the fields include class, teacher, time slot, and classroom; whether the date is consistent with the current version; whether there is a signature from the scheduling person in charge | Compare the class schedule fields with the new time slot in the schedule change request one by one, and check the date and signature column; reference variables and nodeId in a subsequent node and run a trial |
| Class-hour deduction record | Whether the fields include student, course, date, and number of class hours; whether the signature or receipt is complete; whether the quantity can match the class size in the class schedule | Check the class, date, and number of class hours in the class-hour deduction record against the class schedule one by one; mark items missing a signature or receipt separately |
| Schedule change request | Whether the original time slot, new time slot, approver, and receipt are complete; whether the name, quantity, and date of the same record are consistent across the two materials | Compare the schedule change request with the class schedule and class-hour deduction record, checking the three places: name, quantity, and date; for versions not synchronized, the current version shall prevail |
| User selection node | Whether each option corresponds to one branch; whether the interaction state is recorded when triggered; whether the selection result variable is passed to subsequent nodes | Run a trial for each option and check the branch direction and interaction state in the run record; reference variables and nodeId in a subsequent node to verify |
Three common errors
- Symptom: The number of class hours for the same class-hour deduction record does not match between the class schedule and the class-hour deduction record. Cause: The two materials were entered separately, without cross-checking by the same date and class.
- Symptom: The schedule change request has been archived, but the class schedule still shows the old time slot. Cause: The versions were not synchronized, the current version did not overwrite the old version, and an expired item was retrieved when referenced.
- Symptom: A class-hour deduction record missing a signature or receipt is still referenced as a basis. Cause: The signature column and receipt field were not checked when the material was archived, and the completeness of the item was not confirmed.
How to verify the setup
Acceptance of this feature: run a trial for each option and check the branch direction and interaction state in the run record; reference variables and nodeId in a subsequent node to confirm that the selection result variable has been passed.
Business test: ask a cross-material basis question and see whether the answer gives a traceable source, and check that the source comes from the institution’s materials, that the version is the current one, and that the item matches the original text.
- Compare the fields, dates, and signatures of the class schedule, class-hour deduction record, and schedule change request one by one, and mark inconsistent items.
- Run a trial for each option in the user selection node, check the branch direction and interaction state records, and confirm that subsequent nodes have referenced
variablesandnodeId.