What this category's data looks like
Materials for kindergarten game activity organization come from observation records, area plans, material placement lists, activity objectives, reflection records, and next week's plans. Observation records and area plans must correspond; the quantity of placed materials must match the plan; activity objectives must be consistent with observed behavior; reflections must be turned into next week's plans. When materials enter the form input node, they serve respectively as the exception source, review basis, and conclusion fields: observation records and area plans are used to locate exceptions, material quantity and objective achievement are used for judgment, and reflections and next week's plans are used for review and disposition. The update rhythm is after each activity and before the weekly plan. Field characteristics are multi-line text, dates, quantities, and selection items, and must be checked item by item.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and outputs the field values filled in by the user (passed to subsequent nodes after submission). The "exception list and review conclusion" is then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | The two must correspond; when inconsistent, record the exception source | Check the field names one by one in the node configuration, and confirm that the observation record and area plan fields correspond one to one |
| Material placement quantity | The quantity must match the area plan; when insufficient, mark it as an exception | Check the required settings one by one, and confirm that the material quantity field has been marked as required |
| Activity objective achievement | The objective must match the observation; when it does not, enter review | Reference this field in subsequent nodes and run a test to confirm that the objective achievement field value can be retrieved |
| Reflection converted to next week's plan | The reflection must be converted into next week's plan; when not updated, record an exception | Check the transfer between the reflection field and next week's plan field, and confirm that subsequent nodes can retrieve it after submission |
Three common errors
- Phenomenon: insufficient material quantity is not recorded as an exception. Cause: the material placement quantity and the area plan do not correspond item by item, and the form is not marked as required, resulting in omissions.
- Phenomenon: the activity objective does not match the observation record but still passes review. Cause: the objective achievement field and the observation description are not checked for consistency, and the review basis is missing.
- Phenomenon: the reflection is not converted into next week's plan, and the plan is not updated. Cause: no transfer is established between the reflection field and next week's plan field, so subsequent nodes cannot retrieve the value.
How to verify the setup
Acceptance of this feature: fill it out once and submit, check the field values retrieved by subsequent nodes, and confirm that the formInputResult and selectResult field values can be passed correctly.
Business test: create an exception record, see whether the source material can be traced, and confirm that observation records, material quantity, objective achievement, and reflection plans are all traceable.
- Check the field names one by one in the node configuration, and confirm that they correspond one to one with the material fields to be collected.
- Check the required settings one by one, and confirm that key material fields have been marked as required.