What this category's data looks like
For the kindergarten home-school co-education communication category, the materials include commitment items and response times, descriptions of children's performance, classification of parents' requests, and notification delivery records. The sources are teachers' daily observations, parents' form submissions, and kindergarten notification receipts. The update cadence is daily or weekly, and the field characteristics are structured text and timestamps. When the materials enter the form input node, each has a different role: commitment items and response times serve as required fields and determine the scope visible to parents; descriptions of children's performance serve as text fields for subsequent nodes to generate feedback; classification of parents' requests serves as a selection field for categorization; notification delivery records serve as time fields for verification. Together these materials constitute the externally accessible entry point and authorization scope. The visitor's identity matches the visible scope, and unauthorized content is not visible.
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 externally accessible entry point and authorization scope are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Commitment items and response times | Whether the commitment items receive a response within the agreed time, and whether the response time is consistent with the commitment | Check the form fields, inspect the required markers, and after a test run view the field values obtained by subsequent nodes |
| Descriptions of children's performance | Whether the description content matches the teacher's observation records, and whether there are contradictions or omissions | Verify item by item against the observation records, and confirm that the field values are passed to subsequent nodes |
| Classification of parents' requests | Whether the requests are classified into the correct category, and whether the classification field is referenced by subsequent nodes | Reference the formInputResult field in subsequent nodes, and check whether the classification value is passed correctly |
| Notification delivery | Whether the notification is delivered to the parent, and whether the delivery time and receipt are recorded | Check the delivery time field, use userSelect to select the notification type, and check the field values |
Three common errors
- Symptom: parents receive no response for a long time after submitting a request. Cause: commitment items and response times are not set as required, so subsequent nodes are not triggered to process it.
- Symptom: descriptions of children's performance do not match the observation records. Cause: the form fields are not checked against the observation records, and the description content is not validated.
- Symptom: parents' requests are not categorized, and feedback piles up. Cause: the request classification field is not configured, so subsequent nodes cannot process by category.
How to verify the setup
Acceptance for this feature: fill out the form once and submit it, check the field values obtained by subsequent nodes, and confirm that the formInputResult and selectResult fields are passed correctly.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and confirm that unauthorized content is not visible.
- In the node configuration, check the field names and required settings one by one to ensure they correspond one-to-one with the material fields.
- Reference the
formInputResultfield in subsequent nodes and run a test to confirm that the corresponding field values can be obtained after submission.