What this category's data looks like
Kindergarten home-school co-education communication materials center on four categories: committed items and response times, descriptions of children's performance, classification of parents' requests, and notification delivery. Committed items come from oral or written agreements between teachers and parents, and their update cadence changes with daily communication; descriptions of children's performance come from observation records and must correspond to the day's activities; classification of parents' requests comes from parents' messages and receipts and must be categorized by item; notification delivery comes from class announcements and receipts. When these materials enter the form input node, each has a different role: committed items and response times serve as fields to be confirmed, descriptions of children's performance serve as descriptive fields, classification of parents' requests serves as a selection field, and notification delivery serves as a confirmation field. The field characteristics are multiple sources, requiring an responsible person, and requiring version and date consistency. Drafting materials and handing off responsibility require complete fields, a clear responsible person, and sign-off when handed to the next stage.
Configuration and implementation checks
| Object | Check | Verification action |
|---|---|---|
| Commitment item and response time | Whether the commitment is responded to and whether the response time is clear | Check the field names and required settings one by one in the node configuration, and after a trial run confirm that subsequent nodes can retrieve the field value |
| Toddler performance description | Whether the statement is consistent with the observation record | Check the description field against the observation record, reference this field in subsequent nodes, and run a trial |
| Parent request classification | Whether the feedback is categorized and whether the classification is clear | Check the classification field and required marker, and after submission check whether subsequent nodes can retrieve the corresponding field value |
| Notification delivery | Whether the delivery confirmation and date version are consistent | Check the delivery confirmation field and date field, submit using formInput, and then check field passing |
Three common errors
- Symptom: After a committed item is submitted in the form, subsequent nodes do not receive the response time field. Cause: The field was not marked as required, so it could still pass when empty on submission, resulting in a missing item in the handoff record.
- Symptom: The description of children's performance is inconsistent with the observation records and is returned during handoff. Cause: The description field was not checked against the observation records, and was filled in from impression during drafting, with version and date not aligned.
- Symptom: Parents' requests are not categorized, and subsequent nodes cannot process them by category. Cause: The classification field did not use
userSelectto limit options, and free-form entry caused scattered classification, so feedback was not categorized.
How to verify the setup
Fill it out once and submit, check the field values retrieved by subsequent nodes, and confirm that fields are passed correctly after formInput submission and that submission is blocked when required items are empty.
Business test: Draft one according to the template and complete one handoff, and see whether missing items are blocked.
- Check the field names and required markers one by one in the node configuration to ensure that key material fields are marked as required.
- Reference the field in subsequent nodes and run a trial to confirm that after submission subsequent nodes can retrieve the corresponding field value.