What this category's data looks like
This page addresses authorized access and external services for primary and secondary school timetables and after-school service scheduling. The materials include the master timetable, the teacher assignment table, and the after-school service project table. The master timetable comes from the academic affairs office, is published at the start of each semester, and is updated with intra-week adjustments; its fields include class, period, course name, assigned teacher, venue, and date. The teacher assignment table comes from the grade group, is checked weekly, and its fields include teacher, class, subject, weekly class hours, and a signature column. The after-school service project table comes from the moral education office, is summarized monthly, and its fields include project name, participating students, supervising teacher, start and end dates, and receipt. When these three types of materials enter workflow orchestration, the master timetable serves as the draft of the visible scope for the external entry point, the teacher assignment table serves as the basis for verifying identity and authorization scope, and the after-school service project table serves as supplementary content visible to parents or superiors. Field characteristics are mainly dates, quantities, signatures, and receipts, and must be compared item by item.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "The externally available entry point and authorization scope" is then completed by subsequent nodes continuing execution along the branches. When a 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 |
|---|---|---|
| Master timetable | Whether class, period, course name, assigned teacher, venue, and date are consistent item by item with the teacher assignment table, and whether the signature column is complete | Check the options and branch connections one by one in the user selection node, run a test and then view the node status in the run records, and reference variables and nodeId in subsequent nodes to confirm that the selection result variable has been passed |
| Teacher assignment table | Whether teacher, class, subject, weekly class hours, and date match the master timetable, whether versions are synchronized, and whether missing signatures or receipts have been completed | Access once with a restricted identity, compare whether the visible scope matches the identity, and confirm that unauthorized content is not visible |
| After-school service project table | Whether project name, number of participating students, supervising teacher, and start and end dates are consistent with the master timetable and teacher assignment table, and whether receipts are retained | Trigger a user selection node once, view the interaction state records, confirm that the same session does not repeatedly enter interaction, and confirm that the process continues downward after interaction is completed |
Three common errors
- Symptom: The name, quantity, and date of the same after-school service project do not match across the two materials. Cause: The master timetable and the after-school service project table are maintained separately by the academic affairs office and the moral education office, their update rhythms differ, and no item-by-item comparison was performed.
- Symptom: The teacher assignment table version is not synchronized and still shows old weekly class hours. Cause: After adjustments by the grade group, the changes were not sent back to the academic affairs office, and the workflow branch referenced old records when continuing execution.
- Symptom: The master timetable lacks signatures or the after-school service project table lacks receipts. Cause: Before authorized access and external services, the materials were not fully collected, and the visible scope did not match the settings during restricted-identity access.
How to verify the setup
Feature acceptance: Run tests option by option, check the branch directions and interaction states in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and verify variables, nodeId, and the option branch connections.
Business testing: Access once with a restricted identity, see whether the visible scope matches the settings, and confirm that unauthorized content is not visible.
- Check the options and branch connections one by one in the user selection node, and after running a test, view the node status and interaction state in the run records.
- Access once with a restricted identity, compare the dates, quantities, signatures, and receipts of the master timetable, teacher assignment table, and after-school service project table, and confirm that the visible scope matches the identity.