What this category's data looks like
This category involves three core types of materials: registration forms, care bonus point materials, and admission rosters, all structured around form fields, dates, signatures, and receipts. The registration form collects the candidate's basic information, application level, and subject category, with many fields and dense mandatory requirements; the care bonus point materials include certificate names, numbers, and validity periods, and must be aligned item by item with the names, quantities, and dates of the same record in the registration form; the admission roster carries the batch, major, planned number, and admission conclusion, and signatures and receipts determine whether the handover is valid. The three types of materials are updated in batches according to the rhythm of registration, review, and admission. For the same candidate, inconsistencies in names, quantities, and dates are likely to appear among the registration form, bonus point materials, and roster, versions may not be synchronized, or signatures and receipts may be missing. When materials enter the form input node, their respective roles are a set of fields to be filled and the basis for handover; the node is only responsible for collecting the filled values, does not recognize content, and does not judge authenticity.
Configuration and implementation checks
This part 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 material drafts that can be issued and the handover records are completed by subsequent nodes or manually afterward. After the form input node is triggered, the conversation enters the interaction state and records the workflow state. After the user completes the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Registration form | Fields are complete, the responsible person is clear, the version and date are consistent, and the names, quantities, and dates of the same record match those in the care bonus point materials | Check the field names one by one in the node configuration, confirm that the required markers cover the key material fields, reference the field in subsequent nodes after submission, and run a trial |
| Care bonus point materials | The certificate name, number, and validity period are consistent with the registration form, and signatures and receipts are not missing | Check the required settings item by item, verify the field values obtained by subsequent nodes after submission, and compare the names, quantities, and dates of the two materials |
| Admission roster | The batch, major, planned number, and admission conclusion fields are complete, the version and date are synchronized, and the responsible person's signature is complete | Reference the field in subsequent nodes and run a trial, and check whether the subsequent nodes can obtain the corresponding field values after submission |
| Form input node | If required items are empty, submission is not allowed; after submission, the field values can be obtained by subsequent nodes; the conversation does not remain in the interaction state | Check the required settings and field passing, and run a trial of one complete submission |
Three common errors
- Symptom: For the same candidate, the names, quantities, and dates in the registration form and care bonus point materials do not match. Cause: The two materials are drafted separately, the fields are not compared item by item, and the versions are not synchronized.
- Symptom: The admission roster lacks a signature or receipt, and the handover cannot be accepted. Cause: The handover record does not circulate together with the material draft, and the responsible person does not confirm before submission.
- Symptom: After submission, subsequent nodes cannot obtain the values, and the conversation remains in the interaction state. Cause: Required markers are missing or field names are inconsistent with subsequent references, and no trial run was performed for verification.
How to verify the setup
Acceptance of this feature: fill it out once and submit, check the field values obtained by subsequent nodes, confirm that submission is not allowed when required items are empty, and that the conversation does not remain in the interaction state.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the field names one by one in the node configuration, confirm that they correspond one-to-one with the material fields, and that key material fields have been marked as required.
- Reference the field in subsequent nodes and run a trial, verify the field passing after submission, and check whether
formInputResultandselectResultvalues are obtained normally.