What this category's data looks like
This page addresses kindergarten childcare daily life management materials, covering three core types of forms: the daily life schedule, morning and afternoon check records, and child health observation records. The materials come from daily entries by class teachers, aggregation by the health room, and review by the kindergarten management lead, with an update cadence of daily entry, weekly archiving, and monthly aggregation. Field characteristics center on dates, activity segment names, child names, observation items, quantities, signatures, and receipts. The daily life schedule carries the timeline and segment attribution, the morning and afternoon check records carry entry and midday health status, and the child health observation records carry continuous individual tracking. When these three types of materials enter the workflow orchestration feature, they serve respectively as the data source for the authorized visible scope, the basis for visitor identity matching, and the content carrier for the external service entry, jointly determining the fields and record scope visible to parents or superiors.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entries and authorized scope" is then completed by subsequent nodes continuing execution along the branches. When a node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Daily life schedule | Whether the date and segment names are consistent across the two materials, and whether signatures and receipts are complete | Check the options and branch connections one by one in the node to confirm the visible scope corresponding to this form; trigger it once and view the node status in the run records |
| Morning and afternoon check records | Whether the morning check and afternoon check quantities, dates, and observation items for the same child match, and whether missing signatures or receipts have been corrected | Reference variables in subsequent nodes and run a trial once to check whether the selection result variable is passed to the visible scope determination |
| Child health observation records | Whether the versions are synchronized, and whether the name and date of the same record are consistent across the two materials from the class and the health room | Use nodeId to locate the node and check the branch direction and state records after this record enters the interaction |
| External entry and authorized scope | Whether the visitor identity matches the visible scope, and whether unauthorized access is invisible | Access once with a restricted identity and check whether the visible fields and record scope conform to the settings |
Three common errors
- Symptom: the same child's name is inconsistent between the morning and afternoon check records and the health observation records. Cause: the two materials are entered separately, without field alignment and version synchronization.
- Symptom: the dates and segment quantities do not match between the daily life schedule and the morning and afternoon check records. Cause: the entry cadences differ, and dates and quantities were not checked during aggregation.
- Symptom: after the external entry is opened, records missing signatures or receipts are still visible to parents. Cause: the authorized scope was not filtered by signature status, and the branch direction did not cover this situation.
How to verify the setup
Feature acceptance: run trials 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, and that the selection result variable has been passed to subsequent nodes.
Business test: access once with a restricted identity, see whether the visible scope conforms to the settings, and whether unauthorized content is invisible.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and use
nodeIdto locate the node and view the state records. - Reference
variablesin subsequent nodes and run a trial once to confirm that the selection result variable has been passed, and that the process continues downward after the interaction is completed.