What this category's data looks like
This page addresses the compulsory education dropout prevention and school retention category. Materials come from three types: dropout risk ledgers, return-to-school persuasion records, and home visit records. The update cadence is weekly supplementary entry and monthly archiving, and field characteristics include student name, date, signature, and receipt. When multilingual materials enter the workflow, the risk ledger serves as the primary index providing student identifiers and risk levels, the persuasion records provide persuasion counts and outcomes, and the home visit records provide visit times and parent signatures. In the terminology processing step, the three types of materials each serve as a comparison anchor: the risk ledger defines the student and risk level, the persuasion records define the persuasion action and outcome, and the home visit records define the communication facts and signature status. The unified terminology glossary and comparison draft need to cover the field names and translated names of the three types of materials, ensuring that the same term is consistent throughout and that translated names can refer back to the source text. Before external release, complete a spot check of three terms to see whether their usage is consistent throughout.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. 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 match the persuasion records and home visit records | Check the options and branch connections one by one in the node, reference variables and run a trial once, and view the node status in the run records |
| Persuasion records | Whether the name, quantity, and date of the same record are consistent across the two materials | Reference nodeId in subsequent nodes and run a trial once, and check the branch direction and interaction status records |
| Home visit records | Whether a supplementary entry branch is triggered when a signature or receipt is missing | Trigger a user selection once, and view the node status and selection result variable in the run records |
| Unified terminology glossary and comparison draft | Whether the same term is consistent throughout and translated names can refer back to the source text | Spot-check three terms to see whether their usage is consistent throughout, and check the branch direction and interaction status records |
Three common errors
- Phenomenon: The name, quantity, and date of the same student do not match between the risk ledger and the persuasion records. Cause: The two materials are entered separately, and field alignment and version verification were not done before terminology processing.
- Phenomenon: The home visit record lacks a signature or receipt, but the persuasion record shows completed. Cause: Material versions were not synchronized, and the receipt status was not updated with the latest record.
- 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 passed to subsequent nodes.
How to verify the setup
This feature acceptance: run trials for each option one by one, check the branch direction and interaction status in the run records, and confirm that variables, nodeId, and the selection result variable have been passed to subsequent nodes.
Business test: spot-check three terms to see whether their usage is consistent throughout, and check that translated names can refer back to the source text.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once, and check the branch direction and interaction status records.