What this category's data looks like
Compulsory education dropout prevention and control materials mainly consist of dropout risk ledgers, return-to-school persuasion records, and home visit records. Their sources are schools, townships, and education authorities. The update cadence is summarized weekly or monthly. Field characteristics include student name, student status number, risk level, persuasion date, home visit date, signature, and receipt. When materials enter this function, the dropout risk ledger serves as the primary data source and provides student basics and risk identifiers; return-to-school persuasion records and home visit records serve as process materials and respectively provide persuasion count, persuasion result, and home visit time and home visit personnel. During deployment, operations, and application handover, these three types of materials need to complete user selection and branching through workflow nodes, forming a handover-ready deployment state and operation records, and ensuring consistency among version, connection, and task records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution according to the branch. 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 |
|---|---|---|
| Dropout risk ledger | Whether fields, dates, and signatures are consistent with return-to-school persuasion records and home visit records | Check options and branch connections one by one in the node, and reference variables to see whether ledger fields are passed to subsequent nodes |
| Return-to-school persuasion records | Whether the name, quantity, and date of the same record do not match across the two materials | Trigger a user selection node once, check the node status in the run records, and verify whether the persuasion date and signature are complete |
| Home visit records | Version not synchronized or missing signature and receipt | Reference the selection result variable in a subsequent node and run a trial once, and check whether the dates and quantities in the home visit records and the ledger are consistent |
| Deployment state and operation records | Whether version, connection, and task records are consistent | Check item by item once according to the handover form, and inspect whether the node status corresponding to nodeId and the branch direction records are complete |
Three common errors
- Phenomenon: The name, quantity, and date of the same return-to-school persuasion record do not match between the ledger and the home visit materials. Cause: The materials are entered separately, not checked against unified fields, and signatures or receipts are missing.
- Phenomenon: The version is not synchronized, and the task records in the deployment state and operation records are inconsistent. Cause: During handover, the version and connection were not checked, and the branch direction of workflow nodes was not fully recorded.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and 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 records, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: check item by item once according to the handover form, see which record is missing, and verify whether the fields, dates, and signatures of the dropout risk ledger, return-to-school persuasion records, and home visit records are complete.
- Check options and branch connections one by one in the node, trigger a user selection node once, and view the node status in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, and check item by item according to the handover form whether version, connection, and task records are consistent.