What this category's data looks like
For question acceptance and missing-item follow-up in kindergarten home-school co-education communication, the materials come from questions submitted by parents, class notices, and child observation records. Parent questions first enter the acceptance stage, which is used to identify whether the request category and key information are complete; class notices are used to verify committed matters and response times; child observation records are used to compare whether the parent's statements are consistent with daily performance. The material update rhythm rolls forward with daily communication and weekly records, and the field characteristics are concentrated in five categories: committed matters, response time, child performance description, parent request category, and notice delivery. When entering the HTTP interface and external systems, parent questions are the input that triggers acceptance, while notices and observation records are references for follow-up questions and basis judgment, each playing a different role.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "acceptance record and completed follow-up items" are parsed by subsequent nodes from the response, or handled by an external system according to the agreement to complete the next step. The HTTP module sends requests to the target address, and variables can be used as placeholders in three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Parent question | Whether the request category and key information are complete, and whether missing items can be identified and followed up | In the request preview, view the complete rendered address, check that the request body fields match the external interface agreement, and compare the response using a sample request |
| Class notice | Whether committed matters and response times are responded to, and whether notice delivery is traceable | Check the request header names and value sources, confirm that authentication information is passed in according to the external system's requirements, and check whether placeholder variables can be resolved into actual values |
| Child observation record | Whether the child performance description is consistent with the parent's statements, and whether feedback is categorized | In the variable panel, check the source of each placeholder, confirm that variables and responseData can be traced to specific origins, and compare the returned fields using a sample |
| External system response | Whether the status code and returned fields support subsequent parsing and transfer to the handler | Check how Authorization is passed in, and check whether the returned fields contain the content needed for the acceptance record and completed follow-up items |
Three common errors
- Phenomenon: A parent question is answered directly even though key information is missing. Cause: The acceptance stage did not first identify missing items and ask follow-up questions, and committed matters and response times did not enter the judgment.
- Phenomenon: The parent's statements are inconsistent with the child observation record. Cause: During follow-up questioning, the observation record was not retrieved for comparison, and the child performance description field was not used as a basis.
- Phenomenon: Feedback is not categorized, causing confusion when transferring to the handler. Cause: The parent request category and notice delivery fields are not distinguished in the response, making it difficult for subsequent nodes to parse.
How to verify the setup
Acceptance for this feature: preview the rendered request, check the status code and returned fields, and then compare the result against a sample.
Business test: submit a question that is missing key information and see whether it asks follow-up questions before answering.
- Check the request address and path parameters, and confirm that placeholder variables can be resolved into actual values.
- Check the request headers and request body, and confirm that the fields match the external interface agreement and that variable sources are traceable.