What this category's data looks like
School moral education and homeroom teacher work materials include themed class meeting plans, student comprehensive quality records, and home visit records. A themed class meeting plan contains the class meeting theme, time, location, host, activity process, and signature; a student comprehensive quality record contains fields such as ideological and moral character, academic level, physical and mental health, artistic literacy, and social practice, the evaluation date, and the homeroom teacher's signature; a home visit record contains the home visit target, time, location, purpose, process, parent receipt, and teacher signature. The material sources are daily reporting by homeroom teachers, aggregation by grade groups, and archiving by the moral education office, and the update rhythm is once a week for class meetings, once per semester for comprehensive quality records, and on demand for home visit records. When entering the workflow orchestration function, the three types of materials respectively serve as authorized external content: themed class meeting plans open some fields to parents, student comprehensive quality records open summary fields to superiors, and home visit records open receipt and conclusion fields to parents.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The externally available entry points and authorization scope must be continued by subsequent nodes according to 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 |
|---|---|---|
| Themed class meeting plan | The name, date, and signature of the themed class meeting plan are consistent across the three materials, and the signature and receipt are complete | Check the options and branch connections one by one in the node, confirm that when the plan fields enter the external entry point they follow the corresponding branch, and reference variables to view the selection result |
| Student comprehensive quality record | The quantity, date, and signature of the student comprehensive quality record match the home visit record and class meeting plan, and the version has been synchronized | Trigger a user selection node once, view the node status in the run record, and confirm that the comprehensive quality record fields enter the external scope according to the branch direction |
| Home visit record | The parent receipt and teacher signature of the home visit record are complete, and the date does not conflict with the evaluation date in the comprehensive quality record | Reference variables and nodeId in subsequent nodes and run a trial once, confirming that the home visit record receipt fields follow the corresponding branch according to the selection result |
| Externally available entry points and authorization scope | The visitor identity matches the visible scope, and unauthorized access is not visible | Access once with a restricted identity, and check whether the branch direction and interaction state record are consistent with the settings |
Three common errors
- Phenomenon: The name and date of the same home visit record do not match between the parent side and the superior side. Cause: The material version was not synchronized, and the branch direction continued to execute according to the old version.
- Phenomenon: The student comprehensive quality record lacks the homeroom teacher's signature or the parent receipt. Cause: The interaction state record did not cover the signature field, and subsequent nodes executed according to the default branch.
- Phenomenon: After selecting an option, the default branch is still followed, and the external entry point and authorization scope do not change according to the selection result. Cause: The selection result variable was not correctly passed to subsequent nodes.
How to verify the setup
This function's acceptance: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and reference variables and nodeId in subsequent nodes to check whether the selection result is passed.
Business test: access once with a restricted identity, see whether the visible scope matches the settings, and check whether the fields and signatures of the themed class meeting plan, student comprehensive quality record, and home visit record are not visible due to unauthorized access.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and record the interaction state.
- Reference
variablesandnodeIdin subsequent nodes and run a trial once, confirming that the selection result has been passed to subsequent nodes.