What this category's data looks like
This page is for school moral education and homeroom teacher work. The material sources are daily class affairs ledgers and handover forms, and the update cadence is synchronized by week and semester milestones. When the three types of materials—themed class meeting plans, student comprehensive quality records, and home visit records—enter workflow orchestration, their roles differ: themed class meeting plans serve as the basis for branch triggering, student comprehensive quality records serve as the carrier of fields to be checked, and home visit records serve as the verification object for signatures and receipts. All three types of materials contain the three characteristics of fields, dates, and signatures. After entering the user selection node, the conversation enters an interactive state, the workflow state is recorded, and after the user completes the selection, the branch is followed according to the corresponding option to continue execution. Subsequent nodes continue execution according to the branch, completing a handover-ready deployment state and operation records.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branches), outputting branch direction and interactive state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution according to the branch. When the node is triggered, the conversation enters an interactive state and the workflow state is recorded. After the user completes the selection, the branch is followed according to the corresponding option to continue execution.
| Object | Check | Verification action |
|---|---|---|
| User selection node | Each option corresponds to one branch, and options and branch connections correspond one by one | Check options and branch connections one by one in the node, and record nodeId and branch direction |
| Themed class meeting plan | Fields, dates, and signatures are complete, and the name, quantity, and date of the same record are consistent in the two materials | Check fields, dates, and signatures item by item according to the handover form; mark any missing signature or receipt |
| Student comprehensive quality record | Fields, dates, and signatures are complete, versions are synchronized, and quantities are consistent | Check the names and quantities in the two materials, and confirm items whose versions are not synchronized |
| Home visit record | Fields, dates, and signatures are complete, and receipts and signatures are not missing | Verify signatures and receipts, and check whether the dates of the same record in the two materials do not match |
Three common errors
- Phenomenon: after selecting an option, the default branch is still followed. Cause: options and branch connections were not checked one by one, and the branch direction is inconsistent with the interactive state record.
- Phenomenon: the name, quantity, and date of the same record do not match in the two materials. Cause: fields and dates were not checked item by item according to the handover form, and signatures or receipts are missing.
- Phenomenon: the process stops after the interaction is completed. Cause: the selection result variable was not passed to subsequent nodes, and subsequent nodes did not continue execution according to the branch.
How to verify the setup
This feature acceptance: test run each option one by one, check the branch direction and interactive state in the run record, and confirm that variables have been passed to subsequent nodes.
Business test: check once item by item according to the handover form, see which record is missing, and check the fields, dates, and signatures of the themed class meeting plan, student comprehensive quality record, and home visit record.
- Check options and branch connections one by one in the node, record
nodeIdand branch direction, and confirm that the interactive state is recorded. - Reference the selection result variable in subsequent nodes and test run once, check fields, dates, and signatures, and confirm version synchronization and complete receipts.