What this category's data looks like
In the compulsory education dropout prevention and retention scenario, material drafting and responsibility handover revolve around three types of materials: the dropout risk ledger, the persuasion-to-return record, and the home visit record. The ledger is updated by semester and by month, and contains student name, student ID number, risk level, responsible person, date, and signature; the persuasion-to-return record is produced with each persuasion-to-return action, and contains persuasion time, location, participants, result, and receipt; the home visit record is produced with each household visit, and contains visit date, visit target, problem description, handling opinion, and parent signature. When these three types of materials enter the forms and interaction function, the ledger takes on the role of baseline data and responsibility allocation, the persuasion-to-return record takes on the role of process traceability, and the home visit record takes on the role of supporting evidence and linkage, jointly supporting the material draft and handover record that can be issued.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The material draft and handover record that can be issued are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters the 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 | Whether the fields, date, and signature are complete, and whether the name, quantity, and date of the same record match across the two materials | Check the field names and required settings one by one in the node configuration, reference the fields with formInputResult, and run a trial |
| Persuasion-to-return record | Whether the persuasion time, participants, result, and receipt are consistent with the ledger, and whether the version is synchronized | Check the required markers one by one, reference the field values obtained by userSelect in subsequent nodes, and run a trial |
| Home visit record | Whether the visit date, visit target, handling opinion, and parent signature link up with the persuasion-to-return record | Reference the formInputResult field values in subsequent nodes, and check whether missing signatures or receipts are blocked |
| Handover record | Whether the responsible person, version, and date are consistent, and whether the next step can sign for receipt | Draft one according to the template and complete one handover, and check whether missing items are blocked |
Three common errors
- Phenomenon: The name and date of the same student do not match between the ledger and the persuasion-to-return record. Cause: The two materials are filled in separately, and the field values are not cross-checked before submission.
- Phenomenon: The material version is not synchronized, and the old draft continues to circulate. Cause: The version and date are not recorded at handover, and the subsequent nodes obtain expired field values.
- Phenomenon: The home visit record lacks a parent signature or receipt, and the handover is returned. Cause: Key fields are not marked as required, and the missing items are only discovered after submission.
How to verify the setup
This function's acceptance: fill in once and submit, check the field values obtained by subsequent nodes, and confirm that the formInputResult and selectResult references can obtain the corresponding values.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the field names and required settings one by one in the node configuration, and confirm that key material fields are marked as required.
- Reference the
formInputResultandselectResultfields in subsequent nodes and run a trial, and confirm that the corresponding field values can be obtained after submission.