What this category's data looks like
In the compulsory education dropout prevention and school retention scenario, material sources include three types: dropout risk ledgers, return-to-school persuasion records, and home visit records. The ledger is updated on a per-semester and monthly report cadence, recording students' basic information, risk level, and responsible person; return-to-school persuasion records are entered as events occur after each persuasion, including persuasion time, participants, result, and signature; home visit records are filled in by the homeroom teacher or assigned teacher weekly or per visit, including home visit date, parent comments, and receipt. When the three types of materials enter this feature, the ledger serves as the primary index providing the object and responsible person, and return-to-school persuasion records and home visit records are attached to the corresponding object as process evidence. Field characteristics are concentrated in dates, quantities, names, signatures, and version numbers. If any field is inconsistent between two materials, it will affect the signability of the materials and the handover receipt.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option. "Signable material drafts and handover records" are then completed by subsequent nodes continuing execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Fields are complete, the responsible person is clear, the version and date are consistent, and the names, quantities, and dates match those in the return-to-school persuasion records and home visit records | Check the options and branch connections one by one in the node, reference variables and nodeId to run a trial once, and view the node status in the run records |
| Return-to-school persuasion record | Persuasion time, participants, result, and signature are complete, and the names, quantities, and dates of the same record are consistent across the ledger and home visit records | Reference the selection result variables in subsequent nodes and run a trial, and check whether the receipt and signature have missing items |
| Home visit record | Home visit date, parent comments, receipt, and signature are complete, the version number is synchronized with the ledger, and there is no unsynchronized version | Trigger a user selection node once, view the node status in the run records, and check whether the same session repeatedly enters the interaction |
| Handover record | The responsible person is clear, the signature or receipt is complete, the version and date are consistent, and the branch direction corresponds to the option | Check the options and branch connections one by one in the node, and check the branch direction and interaction state records corresponding to nodeId |
Three common errors
- Symptom: The names, quantities, and dates of the same record do not match between the ledger and the return-to-school persuasion record. Cause: The two types of materials are updated separately, without field-level comparison and version synchronization.
- Symptom: The home visit record lacks a signature or receipt, and cannot be received at handover. Cause: Process records are entered as events occur, and the signature step is not included in the required validation for material drafting.
- Symptom: 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
Feature acceptance: run a trial 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: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the 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
variablesin subsequent nodes and run a trial once, and check whether the same session repeatedly enters the interaction.