What this category's data looks like
In compulsory education dropout prevention and retention work, the materials mainly consist of dropout risk ledgers, return-to-school persuasion records, and home visit records. The ledger is updated per semester and includes student name, risk level, date, and signature; persuasion records are generated per instance and include the persuasion target, number of attempts, receipt, and signature; home visit records are generated per instance and include the home visit target, date, signature, and parent receipt. When the three types of materials enter the workflow, their roles differ: the ledger serves as the risk base, while persuasion records and home visit records serve as process evidence. The material sources are submissions from schools and townships, and the update rhythm is at the beginning, middle, and end of the semester. The field characteristics are that the name, quantity, and date of the same record may be inconsistent across different materials, versions are not synchronized, and signatures or receipts may be missing. Workflow orchestration needs to branch the three types of materials by risk level and number of persuasion attempts, ensuring that basis items can be traced back to the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Basis items that can be traced back to the original text" are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Fields include student name, risk level, date, and signature; it is necessary to check whether the name, quantity, and date are consistent with the persuasion records and home visit records | In the node, check the options and branch connections one by one, and reference variables to see whether the selection result variable is passed |
| Persuasion record | Fields include persuasion target, number of attempts, receipt, and signature; it is necessary to check whether the date and signature match those in the ledger and home visit records | Trigger a user selection node once, and in the run record view the node status and branch direction corresponding to nodeId |
| Home visit record | Fields include home visit target, date, signature, and parent receipt; it is necessary to check whether the name and quantity are consistent with the ledger and persuasion records | Reference variables in a subsequent node and run a test once to confirm that the selection result variable has been passed to the subsequent node |
| User selection node | Each option corresponds to one branch; the options and branch connections need to be checked one by one | In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the ledger and the persuasion record. Cause: The two types of materials are filled in by different personnel, and no cross-check was performed.
- Symptom: Material versions are not synchronized, and an old version of the ledger is still referenced. Cause: The update rhythm is mid-semester, and the version was not synchronized with the persuasion record.
- Symptom: The persuasion record lacks a signature or the home visit record lacks a receipt. Cause: Process materials were not signed in a timely manner, and no completeness check was performed during archiving.
How to verify the setup
Acceptance of this feature: run a test for each option one by one, check the branch direction and interaction state in the run record, and confirm that nodeId and variables are passed correctly.
Business test: ask a cross-material basis question and see whether the answer provides a traceable source.
- In the node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- Reference
variablesin a subsequent node and run a test once to confirm that the selection result variable has been passed to the subsequent node.