What this category's data looks like
This category's data covers three types of materials: the daily life schedule, morning and afternoon check records, and child health observation records. The schedule is updated weekly or daily, with fields including time slot, activity segment, responsible person, and signature; the morning and afternoon check records are completed twice daily, with fields including date, body temperature, oral and hand condition, abnormality description, and childcare worker signature; the health observation records are filled in as needed, with fields including observation time, symptoms, handling, and parent receipt. The dates of the three types of materials must be aligned, and the same child's name, headcount, and abnormality items should be consistent across the two materials. When entering workflow orchestration, the schedule serves as the skeleton of the main process, while the morning and afternoon check records and health observation records serve as the basis for branch triggering; the user-selected node determines the subsequent direction, and the materials themselves do not make choices for the user.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution along the branch. When a node is triggered, the conversation enters the interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option, with options and branches corresponding one by one, the selection result passed to subsequent nodes as variables, and the node identity located by nodeId.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Time slot, activity segment, responsible person, and signature are complete, and the date is aligned with the morning and afternoon check records | Check the options and branch connections one by one in the node, confirm the reference path of the schedule as the skeleton of the main process, and record the nodeId |
| Morning and afternoon check records | Date, body temperature, abnormality description, and childcare worker signature are consistent with the health observation records | Trigger a user-selected node once, view the node status in the run records, and check the branch direction triggered by the morning and afternoon check records |
| Child health observation records | Observation time, symptoms, handling, and parent receipt are consistent with the schedule date | Reference variables in a subsequent node and run a trial once, and check whether the branch corresponding to the health observation records is correctly selected |
| Handover form | Version, connection, and task records are consistent, and signatures and receipts are not missing | Check the handover form item by item once, see which record is missing, and confirm that the interaction state and branch direction have been written into the run records |
Three common errors
- Symptom: The same child's name or the number of abnormality items does not match between the schedule and the morning and afternoon check records. Cause: The two materials are updated separately, and field comparison and date alignment are not performed before the node branch.
- Symptom: After selecting an option, the default branch is still taken, and the handover form lacks the corresponding branch record. Cause: The options and branch connections are not checked one by one, and the selection result variable is not passed to subsequent nodes.
- Symptom: After the interaction is completed, the process stops, or the same session repeatedly enters the interaction, and signatures and receipts are missing. Cause: The interaction state is not correctly recorded, and subsequent nodes do not continue execution along the branch.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, the selection result is passed to subsequent nodes as variables, and the node is identified by nodeId.
Business testing: Check the handover form item by item once, see which record is missing, and confirm that version, connection, and task records are consistent and that signatures and receipts are complete.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and record the
nodeIdand branch direction. - Trigger a user-selected node once, view the node status in the run records, and confirm that the interaction state is recorded and the selection result has been passed to subsequent nodes.