What this category's data looks like
This page addresses the scheduling and class-hour deduction scenarios of training institutions. The materials come from three types of academic ledgers: class schedules, class-hour deduction records, and schedule change requests, updated weekly or per class session. Class schedules record the course name, class, teacher, classroom, class date, and time slot; class-hour deduction records record the student, class session, number of class hours consumed, and signature or receipt; schedule change requests record the original class session, target class session, application date, and approval signature. When the three types of materials enter the workflow, each plays a different role: the class schedule serves as the scheduling baseline, the class-hour deduction record serves as the consumption evidence, and the schedule change request serves as the basis for changes. Field characteristics are concentrated in four categories: name, quantity, date, and signature. For the same class session, the name, number of class hours, and date in the class schedule and the class-hour deduction record need to be aligned item by item, and version synchronization and signature receipts between schedule change requests and class schedules also need to be checked.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entry points and authorization scope" is completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Whether the course name, class, teacher, classroom, class date, and time slot are consistent with the class-hour deduction record | Compare the name, date, and signature in the class schedule and the class-hour deduction record item by item, and check the class session identifier in variables |
| Class-hour deduction record | Whether the student, class session, number of class hours consumed, and signature or receipt are complete | Check the node status corresponding to nodeId in the run records, and check whether the number of class hours and date are consistent with the schedule change request |
| Schedule change request | Whether the original class session, target class session, application date, and approval signature are synchronized with the class schedule version | Check the version synchronization between the schedule change request and the class schedule, and confirm that the signature or receipt is not missing |
| External entry point | Whether the visitor identity matches the visible scope, and whether unauthorized content is invisible | Trigger a user selection once with a restricted identity, and check the authorization scope and branch direction in variables |
Three common errors
- Symptom: The name, number of class hours, and date of the same class session in the class schedule and the class-hour deduction record do not match. Cause: The two materials are entered separately and are not checked uniformly by class session identifier.
- Symptom: The schedule change request and the class schedule version are not synchronized, and the old class session still appears at the external entry point. Cause: After the change, the user selection node was not re-triggered, and the branch still follows the default path.
- Symptom: The class-hour deduction record lacks a signature or receipt, but the external entry point still shows that the class session is completed. Cause: The interaction state was not recorded completely, and subsequent nodes continue execution according to the old branch.
How to verify the setup
Acceptance of this feature: Try running each option one by one, check the branch direction and interaction state in the run records, and confirm that the node status corresponding to nodeId is consistent with the option.
Business test: Access once with a restricted identity, and see whether the visible scope matches the setting and whether unauthorized content is invisible.
- In the user selection node, check the options and branch connections one by one, trigger it once, and then check the node status in the run records.
- Reference the selection result
variablesin a subsequent node and run it once to confirm that the branch direction is consistent with the interaction state record.