What this category's data looks like
Compulsory education dropout prevention and retention materials mainly consist of dropout risk ledgers, persuasion-to-return records, and home visit records, sourced from routine reporting by schools, townships, and education authorities. The update cadence runs in parallel by semester and by month, with persuasion-to-return and home visit records added immediately as events occur. Field characteristics center on student name, class, risk level, persuasion-to-return date, home visit date, and signed receipt. When materials enter the forms and interaction feature, the ledger defines identity and visibility scope, while persuasion-to-return records and home visit records serve as the credentials for external service entry points; together the three support the authorized access scope and external service standards.
Configuration and implementation checks
This part is executed by the form input node (interaction node) in the workflow, outputting the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry points and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interaction state and records the workflow state; after the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Field names correspond one-to-one with risk level, class, and date; unauthorized identities cannot see it | Check field names one by one in the node configuration, and access once with a restricted identity |
| Persuasion-to-return record | Persuasion-to-return date and signed receipt are complete; the same record has consistent name and date across both materials | Check the required settings one by one, reference the formInputResult field in subsequent nodes, and run a trial |
| Home visit record | Home visit date and receipt signature are traceable; version is in sync with the ledger | Check version synchronization, and access once with a restricted identity to see the visibility scope |
formInputResult field passing | Subsequent nodes can retrieve the corresponding field values | Reference the formInputResult and selectResult fields in subsequent nodes and run a trial |
Three common errors
- Symptom: The same persuasion-to-return record has mismatched name, quantity, and date between the ledger and the home visit record. Cause: The two materials are entered separately, without field alignment and version synchronization.
- Symptom: The home visit record lacks a signature or receipt, yet the external service entry point can still be submitted. Cause: Key material fields are not marked as required, making them untraceable after submission.
- Symptom: After submission, subsequent nodes cannot retrieve the values, and the conversation stays in the interaction state. Cause: Field passing is not referenced and trial-run in subsequent nodes, and the interaction state is not correctly ended.
How to verify the setup
Feature acceptance: Fill in once and submit, check the field values retrieved by subsequent nodes, and confirm that the formInputResult and selectResult field values can be referenced.
Business testing: Access once with a restricted identity, see whether the visibility scope matches the settings, and confirm that unauthorized access is not visible.
- Check field names and required markers one by one in the node configuration, ensuring that key material fields are marked as required.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a trial, confirming that field values can be passed after submission.