What this category's data looks like
This category's data for compulsory education dropout prevention and control includes three types of materials: dropout risk ledgers, return-to-school persuasion records, and home visit records. The ledger is updated weekly, with fields including student name, student status number, risk level, responsible person, date, and signature; persuasion records are generated per instance, including persuasion time, method, participants, receipt, and signature; home visit records are generated per instance, including home visit date, teacher, parent signature, and image or text description. When these three types of materials enter this function, their roles differ: the ledger provides abnormal candidates and responsible-person clues, while persuasion records and home visit records serve as supporting original records, used to trace whether the same student's name, quantity, and date are consistent across different materials, and whether signatures or receipts are complete. The update rhythm is weekly, with immediate supplementary entry upon persuasion or home visits, forming a traceable abnormal list and the source of review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "abnormal list and review conclusions" are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Fields include student name, student status number, risk level, responsible person, date, and signature; determine whether the original record support for abnormal tracing is present | Check whether the ledger fields and signature are complete, verify options and branch connections one by one in the node, and reference variables and nodeId to run a trial once |
| Persuasion records | Fields include persuasion time, method, participants, receipt, and signature; determine whether the name, date, and quantity match the same student in the ledger | Check whether the name, quantity, and date in the persuasion records and the ledger are consistent; if signature or receipt is missing, mark as pending review |
| Home visit records | Fields include home visit date, teacher, parent signature, and image or text description; determine whether the version is synchronized with the persuasion records | Check whether the versions of home visit records and persuasion records are synchronized, trigger an interaction status once, and view the node status in the run records |
| Review conclusion | Determine whether it is signed by the reviewer and handed over to the responsible person for handling, and whether the abnormality has original record support | Check the review conclusion signature and original record support, reference the selection result variable in subsequent nodes, and run a trial once |
Three common errors
- Phenomenon: The same student's name, quantity, and date do not match between the ledger and persuasion records. Cause: The two materials are entered separately without field-level comparison, and versions are not synchronized.
- Phenomenon: Home visit records lack a parent signature or persuasion records lack a receipt, yet the review conclusion is still advanced. Cause: Signatures and receipts are not used as branch judgment conditions, and manual review does not intercept.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: Options and branch connections are not verified one by one, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
This function's acceptance: run trials for each option one by one, and check the branch directions and interaction status in the run records; verify options and branch connections one by one in the node, reference variables in subsequent nodes and record nodeId, and confirm that after the interaction is completed, execution continues according to the corresponding option.
Business test: create an abnormal record, see whether the source material can be traced, and check whether the review conclusion has original record support and the reviewer's signature.
- Verify options and branch connections one by one in the node, trigger an interaction status once, and view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, and check whether the name, quantity, date, signature, and receipt of the persuasion records and home visit records are consistent.