Workflow Orchestration for Kindergarten and Family Communication: Compare Documents and Locate Differences

Family Communication: review workflows for document checks. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

Kindergarten home-school co-education communication materials come from class teachers' daily records, parent feedback forms, kindergarten notice ledgers, and commitment response registrations. The update rhythm is daily aggregation and weekly verification. Field characteristics include commitment items and response times, descriptions of children's performance, classification of parents' demands, and notice delivery status. When materials enter the workflow, class records serve as the observation source, parent feedback serves as the demand source, the notice ledger serves as the delivery basis, and the commitment registration serves as the response basis. After the four types of materials are triggered by the user selection node, they enter an interactive state; the workflow records the state and follows branches according to the options, and subsequent nodes generate a discrepancy list based on this.

Configuration and implementation checks

This link is executed by workflow nodes (user selection and branching), outputting branch directions and interactive state records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. When the node is triggered, the conversation enters an interactive state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.

ObjectCheckVerification action
Commitment items and response timesThe response time and response status of the same commitment are consistent in the two materialsCompare the commitment registration and class records item by item, check the options and branch connections in the node, and reference variables to record discrepancy fields
Descriptions of children's performanceThe performance description of the same child is consistent with the observation record wordingExtract one real record, compare it against the observation record to check description discrepancies, and reference nodeId in subsequent nodes to write back
Classification of parents' demandsThe classification attribution of the same demand is consistent in the two materialsCheck item by item according to the demand classification table, trigger one view of the node status in the run record, and mark unclassified items
Notice deliveryThe delivery status and date of the same notice are consistent in the two materialsCompare the notice ledger and parent feedback, check the delivery fields, and include inconsistent items in the discrepancy list

Three common errors

  • Phenomenon: the response time of a commitment item is inconsistent in the two materials. Cause: the update rhythms of the commitment registration and class records are not synchronized, and the response was not written back in time.
  • Phenomenon: the description of a child's performance does not match the wording of the observation record. Cause: the wording of parent feedback retelling and teacher observation records differs, and the description has not been unified.
  • Phenomenon: the classification of a parent's demand is attributed differently in the two materials. Cause: the feedback was not classified or the classification criteria are inconsistent, causing the same demand to fall into different categories.

How to verify the setup

Acceptance of this function: run trials option by option, check the branch direction and interactive state in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.

Business test: use one real record to find fields inconsistent with the ledger, record the discrepancy list, and submit it to the reviewer for confirmation and write-back.

  • Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
  • Trigger the user selection node once, view the node status in the run record, and confirm that the process continues after the interaction is completed.