What this category's data looks like
This page focuses on exception tracing and manual review of kindergarten home-kindergarten co-education communication, with materials drawn from daily class records and parent-side interaction traces. Four types of materials—commitment items and response times, child performance descriptions, parent request classifications, and notification delivery—each have their own role when entering the workflow: commitment and response times are used to compare whether closure occurred on time, child performance descriptions are used to check consistency against observation records, parent request classifications are used to determine whether feedback is assigned to the corresponding category, and notification delivery is used to confirm whether information arrived. Materials are updated daily or weekly, and fields include timestamps, class, child identifier, item type, original text summary, and processing status. Exception tracing requires that each exception can be traced back to the original record, and manual review requires that after the reviewer signs, it is handed to the person in charge for handling. Workflow orchestration accordingly turns materials into traceable branch paths.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The exception list and review conclusions are continued and completed by subsequent nodes according to the branches. When the user selection node is triggered, the conversation enters an interactive state and the workflow status is recorded. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Commitment items and response times | The commitment was not responded to, or the response time exceeded the agreed node | In the node, check the options and branch connections one by one, confirm that the timeout branch is selected, and reference variables to look back at the original commitment record |
| Child performance descriptions | The statement does not match the observation record, or the corresponding observation entry is missing | In a subsequent node, reference nodeId to locate that branch, compare the description text with the original observation record text, and mark inconsistencies |
| Parent request classifications | The feedback was not classified or was assigned to the wrong category | Trigger a user selection once, check the node status in the run record, and confirm that the classification branch direction matches the selected category |
| Notification delivery | The notification was not delivered, or the delivery status does not match the record | In the node, check the delivery branch connections, run a test once, and check whether the interaction status is recorded |
Three common errors
- Symptom: A commitment item appears in the list as responded, but the original record has no response time. Cause: The options and branch connections are misaligned; even though responded was selected, the default branch was still taken, and the original commitment record was not looked back at.
- Symptom: The child performance description does not match the observation record, and the source material cannot be found during review. Cause: The description text is not bound to the observation entry, so subsequent nodes cannot reference the original record of the corresponding branch.
- Symptom: Parent request feedback is not classified, and the review conclusion cannot be handed to the person in charge for handling. Cause: The classification options do not cover that request type; after the interaction is completed, the process stops and does not enter subsequent nodes to continue execution.
How to verify the setup
This feature acceptance: run tests option by option, and check the branch directions and interaction status in the run record; in subsequent nodes, reference variables and nodeId to confirm that the selection result variable has been passed to subsequent nodes.
Business test: create an exception record, see whether the source material can be traced, and confirm that the reviewer signature and the person-in-charge handling path are complete.
- In the node, check the options and branch connections one by one, trigger a user selection once, and check whether the node status is recorded in the run record.
- In a subsequent node, reference the selection result variable and run a test once to confirm that after the interaction is completed, the process continues downward and does not stop in the interactive state.