What this category's data looks like
Compulsory education dropout prevention and control materials mainly consist of dropout risk ledgers, persuasion-to-return records, and home visit records. They are reported by schools and townships, and their update cadence changes with the school term and the progress of persuasion-to-return efforts. Dropout risk ledger fields include student name, risk level, determination date, and responsible person's signature; persuasion-to-return records include persuasion-to-return time, method, result, and parent or guardian signature; home visit records include home visit date, teacher signature, and parent receipt. When these three types of materials enter workflow orchestration, each plays a different role: the dropout risk ledger serves as the primary index, while persuasion-to-return records and home visit records serve as process evidence and must be aligned item by item with the ledger. Version maintenance focuses on the current version being unique, old versions being traceable, and references being synchronized. Any change to any material must trigger an update of the version number and reference relationships.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Whether fields, dates, and signatures are complete, and whether the name, quantity, and date of the same record match across the two materials | Check options and branch connections one by one in the node, reference variables and nodeId, and run a trial |
| Persuasion-to-return record | Whether the persuasion-to-return time, method, result, and parent signature are consistent with the ledger, and whether the version is synchronized | Trigger an interaction state once and view the node status and branch direction in the run records |
| Home visit record | Whether the home visit date, teacher signature, and parent receipt are missing, and whether the old version is traceable | Reference the selection result variable in a subsequent node and run a trial to check whether the reference is synchronously updated |
| Version ledger and change records | Whether the current version is unique, and whether the version number and references are synchronized after changing one piece of content | Record the number of array entries and the reference text tokens; record the number of array entries separately |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the dropout risk ledger and the persuasion-to-return record. Cause: The two materials are maintained separately and have not been aligned item by item.
- Symptom: The home visit record version is not synchronized, and the old version is still referenced. Cause: After the change, the version number and reference relationships were not triggered to update.
- Symptom: The persuasion-to-return record lacks a parent signature or the home visit record lacks a receipt. Cause: The signature and receipt fields were not checked when the materials were archived.
How to verify the setup
This feature acceptance: run each option as a trial, check the branch direction and interaction state in the run records, and confirm that the selection result variable has been passed to subsequent nodes.
Business test: change one piece of content and see whether the version number and references are synchronously updated.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in a subsequent node and run a trial once, then view the node status in the run records.