What this category's data looks like
This page addresses the scenario of school moral education and homeroom teacher work. The material sources are daily class management, home-school communication, and comprehensive quality evaluation, and the update rhythm follows the semester stages and special activities. When three types of materials—themed class meeting plans, student comprehensive quality records, and home visit records—enter the workflow, each plays a different role: the themed class meeting plan serves as the basis for pre-activity design and approval, the student comprehensive quality record serves as the evidence for periodic evaluation and archiving, and the home visit record serves as the evidence for home-school contact and responsibility handover. The field characteristics of the three types of materials center on time, place, participants, matter description, responsible person signature, and receipt. Dates must be synchronized with the version, and signatures and receipts are indispensable. After the materials enter the function, the user selects a node to trigger interaction, and according to the option branch, the process enters the subsequent drafting and handover steps, ensuring that fields are complete, the responsible person is clear, the version and date are consistent, and the next step signs for receipt.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction status records. The material drafts and handover records that can be issued are completed by subsequent nodes continuing execution according to the branch. When the node is triggered, the conversation enters the interaction state and records the workflow status. After the user completes the selection, the process continues along the branch corresponding to the selected option, and subsequent nodes reference the selection result variable to continue drafting and handover.
| Object | Check | Verification action |
|---|---|---|
| Themed class meeting plan | Check whether the fields, date, and signature of the themed class meeting plan are complete, and whether the responsible person is clear | Check the options and branch connections one by one in the node, trigger once to view the node status in the run record, and reference the selection result variable in a subsequent node for a trial run |
| Student comprehensive quality record | Check whether the fields, date, and signature of the student comprehensive quality record are complete, and whether the name, quantity, and date of the same record match in the two materials | Check the options and branch connections one by one in the node, check whether the version is synchronized, and whether missing signatures or receipts are blocked |
| Home visit record | Check whether the fields, date, and signature of the home visit record are complete, and whether the receipt is complete | Check the options and branch connections one by one in the node, trigger once to view the node status in the run record, and confirm that the selection result variable has been passed to subsequent nodes |
| User selection node | Check that each option corresponds to one branch, the interaction status is recorded, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger once to view the node status in the run record, and reference this variable in a subsequent node and run it once |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match in the two materials. Cause: The field sources were not unified during material drafting, the version was not synchronized, and items were not checked one by one before handover.
- Phenomenon: The version is not synchronized, and an old draft is used as the basis for issuance. Cause: The update rhythm is disconnected from the handover record, and the responsible person and date are not refreshed with the version.
- Phenomenon: Signatures or receipts are missing, and the material cannot be handed over to the next step for receipt. Cause: The field completeness determination did not block missing items, the responsible person was not clear, and the receipt did not flow with the material.
How to verify the setup
Acceptance of this function: run a trial for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and check whether the references to variables and nodeId in subsequent nodes take effect.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, trigger once to view the node status in the run record, and confirm that the process continues downward after the interaction is completed.
- Reference the selection result variable in a subsequent node and run it once, check that the variable has been passed in, and check the reference positions of
variablesandnodeId.