What this category's data looks like
This page focuses on compulsory education dropout prevention and school retention materials, covering three core ledgers: the dropout risk ledger, the persuasion-to-return records, and the home visit records. Ledger fields include student name, student ID number, risk level, persuasion-to-return date, home visit date, signature, and receipt; persuasion-to-return records must have the persuader's signature and the parent's receipt; home visit records must have the home visit teacher's signature and the parent's confirmation. The material sources are daily school reporting, township aggregation, and county-level review, and the update cadence is screening at the start of the semester, dynamic updates during the semester, and archiving at the end of the semester. The three types of materials play different roles when entering workflow orchestration: the dropout risk ledger serves as the basis for branch decisions, while the persuasion-to-return records and home visit records serve as evidence materials for the authorized visible scope. Field characteristics require that the name, quantity, and date of the same record be consistent across the two materials, that versions be synchronized, and that signatures or receipts be complete; otherwise, it cannot serve as the authorization basis for the external service entry point.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction state records. "The externally available entry point and authorization scope" is then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Whether the risk level, persuasion-to-return status, date, and signature are consistent with the persuasion-to-return records | Check the options and branch connections one by one in the node, and view the branch direction corresponding to the risk level |
| Persuasion-to-return records | Whether the persuasion-to-return date, persuader's signature, and parent's receipt match the home visit records | Trigger one interaction and view the node status and selection result variables in the run records |
| Home visit records | Whether the home visit date, home visit teacher's signature, and parent's confirmation are synchronized with the ledger version | Reference variables in subsequent nodes and run a trial once to check the visible scope |
| Authorization entry point | Whether the visitor's identity matches the visible scope, and unauthorized access is not visible | Access once with a restricted identity and check the visible materials of the branch corresponding to nodeId |
Three common errors
- Symptom: The date of the same persuasion-to-return record does not match between the ledger and the home visit records. Cause: The two materials were entered separately, versions were not synchronized, and verification was not performed against a unified date field.
- Symptom: The persuasion-to-return records lack the parent's receipt or the home visit records lack a signature. Cause: Signatures and receipts were not validated during the material circulation step, and no item-by-item check was performed before archiving.
- Symptom: After selecting a certain option, the default branch is still taken. Cause: The options and branch connections were not checked one by one, and after the interaction completes the process stalls or the same session repeatedly enters the interaction.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables has been passed to subsequent nodes and that the branch corresponding to nodeId is correct.
Business testing: access once with a restricted identity, see whether the visible scope matches the settings, and confirm that unauthorized materials are not visible.
- Check the options and branch connections one by one in the node, trigger one interaction, and view the node status and selection result variables in the run records.
- Reference
variablesin subsequent nodes and run a trial once to check whether the visible scope of the branch corresponding tonodeIdmatches the authorization entry point.