What this category's data looks like
This category's data mainly consists of four types: class weekly reports, child observation records, parent request registrations, and notification receipts. Weekly reports come from teachers' daily entries, with an update cadence of once per week; observation records are supplemented at any time by activity segment, with fields including descriptions of child performance and time points; request registrations are submitted from the parent side, and must be categorized and annotated with committed items and response times; notification receipts record delivery status and confirmation results. When these materials enter workflow orchestration, weekly reports and observation records serve as the input basis for branch decisions, while request registrations and receipts serve as references for interaction state records. The deployment, operations, and application handover stage requires consistency among version, connection, and task records; the roles of the materials are respectively: weekly reports and observation records determine branch direction, while request registrations and receipts determine the content that subsequent nodes continue to execute. In terms of update cadence, weekly reports are by week, observation records by instance, request registrations by item, and receipts by delivery batch; the handover sheet must check missing record items one by one.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Options and branches | Each option corresponds to one branch; check whether committed items and response times fall into different branches | Check the options and branch connections one by one in the node, confirming that each option has an independent direction |
| Interaction state | The state is recorded when entering the node; check whether descriptions of child performance and observation records are consistent | Trigger once, view the node state in the run records, and check whether the interaction state is recorded |
| Selection result variable | Already passed to subsequent nodes; check whether parent request categories and notification delivery are assigned to the corresponding branches | Reference this variable in a subsequent node and run a trial once, confirming that variables has been passed in |
| Deployment status and operation records | Version, connection, and task records are consistent; check whether unclassified feedback is recorded | Check item by item once according to the handover sheet, checking whether nodeId and variables correspond |
Three common errors
- Symptom: commitments not responded to. Cause: the branch corresponding to the option does not cover the committed items, and after the interaction state is recorded, subsequent nodes are not triggered to continue execution.
- Symptom: descriptions do not match observation records. Cause: weekly report descriptions and observation record fields are inconsistent, and the wrong variable was referenced during branch decision.
- Symptom: feedback not categorized. Cause: parent request categories are not aligned with notification delivery status, and the handover sheet lacks the corresponding record item.
How to verify the setup
Feature acceptance: run trials option by option, check the branch direction and interaction state in the run records, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business testing: check item by item once according to the handover sheet, see which record item is missing, and confirm that version, connection, and task records are consistent.
- Check the options and branch connections one by one in the node, confirming that each option has an independent direction and that the interaction state is recorded.
- Reference
variablesin a subsequent node and run a trial once, checking the branch direction and interaction state records corresponding tonodeId.