What this category's data looks like
This category's data revolves around three types of materials: the college entrance examination registration form, household registration and student status certificates, and materials for children accompanying migrating parents. The materials are mostly filled in by the candidate's family and issued by schools or examination and enrollment institutions, and are submitted and corrected in batches according to the registration cycle. The fields are concentrated in name, ID number, household registration address, student status number, start and end dates of enrollment, parents' residence and social security information, signatures, and receipts. After entering the authorized access and external service scenario, the college entrance examination registration form assumes the role of the main form, providing the basic fields for the external entry point; the household registration and student status certificates assume the role of consistency comparison, checking the name, quantity, and dates of the same record; the materials for children accompanying migrating parents assume a supplementary role, completing the residence and social security chain. The versions of the three must be synchronized. Missing a signature or receipt is regarded as incomplete. The form only collects filled-in values; it does not identify material content, nor does it judge the authenticity of materials.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The external entry point and authorization scope are 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 |
|---|---|---|
| College entrance examination registration form | Field names must correspond one-to-one with the material fields to be collected; name, ID number, household registration address, student status number, and start and end dates of enrollment must match item by item | Check the field names one by one in the node configuration, and check the required settings |
| Household registration and student status certificates | The name, quantity, and dates of the same record in the two materials must be consistent, and the versions must be synchronized | Check the name, quantity, and dates item by item against the college entrance examination registration form; return those missing signatures or receipts for correction |
| Materials for children accompanying migrating parents | Residence and social security fields must corroborate each other with the registration form and household registration and student status certificates, and date ranges must not overlap or have gaps | Check the start and end of residence and the social security months, and reference this field in subsequent nodes and run a trial |
| Field transfer after submission | Subsequent nodes can retrieve the corresponding field values, and the visible range for restricted identities matches the settings | After submitting with formInput, reference the field with userSelect in a subsequent node and run a trial to see whether unauthorized access is invisible |
Three common errors
- Phenomenon: The name, quantity, and dates of the same record in the two materials do not match. Cause: The college entrance examination registration form and the household registration and student status certificates are entered separately, without consistency comparison.
- Phenomenon: The version of the materials for children accompanying migrating parents is not synchronized, and old residence or social security information is still referenced. Cause: After correction, it was not written back to the main form, and the version was not synchronized.
- Phenomenon: After submission, the conversation remains in the interaction state, and subsequent nodes cannot retrieve the values. Cause: Required items can be submitted even when empty, or the field is not referenced in subsequent nodes.
How to verify the setup
Acceptance of this function: Fill in the college entrance examination registration form once and submit it, check whether the field values retrieved by subsequent nodes are consistent with what was filled in, and check once each with formInputResult and selectResult.
Business test: Access once with a restricted identity, and see whether the visible range matches the settings, with unauthorized access invisible.
- Check the form fields one by one against the material fields in the node configuration for one-to-one correspondence, and check the required markers.
- Reference this field in subsequent nodes and run a trial to check whether the field transfer after submission succeeds.