What this category's data looks like
This page addresses the primary and secondary school teacher training credit management scenario. The materials come from training notices, credit recognition forms, and participant lists, organized by batch by school administrators or training organizers, and updated with the training cycle and recognition milestones. The training notice provides the project name, start and end dates, and training requirements; after entering this function, it serves as the rule source for intake questions, used to determine whether a question is missing key information; the credit recognition form carries the teacher's name, credit amount, recognition date, and signature; after entering this function, it serves as the material basis for answers, used to check whether the name, amount, and date of the same record are consistent; the participant list records the participants and sign-in receipts; after entering this function, it is used to fill in missing items and identify cases of missing signatures or receipts. The versions of the three types of materials must be synchronized. If the name, amount, or date of the same record does not match across two materials, or the versions are not synchronized, or a signature or receipt is missing, the question-and-answer intake should first ask follow-up questions before answering, and forward the completed question items and the intake record to the organizer for handling.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting the branch direction and interaction state records. The "intake record and completed question items" are completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Whether the fields, dates, and signature match the credit recognition form and participant list | Check the project name, start and end dates, and training requirements to confirm whether the missing question items are filled in by the notice fields; check the options and branch connections one by one in the node, and check the interaction state corresponding to nodeId |
| Credit recognition form | Whether the name, amount, and date of the same record are consistent across the two materials | Check the teacher's name, credit amount, recognition date, and signature to confirm that the answer has a material basis; reference variables in subsequent nodes and run a trial once |
| Participant list | Whether the versions are synchronized, and whether signatures or receipts are missing | Check the participants, sign-ins, and receipts to confirm that missing items are identified and followed up on; trigger once and view the node status in the run record |
| User selection node | Whether each option corresponds to one branch, and whether the selection result is passed to subsequent nodes | Check the options and branch connections one by one in the node, confirm that the selection result variable has been passed to subsequent nodes, and check whether the process continues after the interaction is completed |
Three common errors
- Symptom: The name, amount, and date of the same record do not match between the training notice and the credit recognition form. Cause: The two materials are maintained separately, and field comparison and version synchronization were not performed before intake.
- Symptom: The participant list version is not synchronized, and the old version is still referenced. Cause: The material was not version-marked after updating, and the workflow node still continues execution along the old-version branch.
- Symptom: The credit recognition form is missing a signature or the participant list is missing a receipt. Cause: The material collection step did not verify signatures and receipts, and the missing items were not identified and followed up on.
How to verify the setup
This function's acceptance: run a trial for each option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, that variables has been passed to subsequent nodes, that the interaction state corresponding to nodeId is recorded, and that the process continues after the interaction is completed.
Business test: submit a question missing key information, see whether it first asks follow-up questions before answering, and check whether the follow-up items come from the fields of the training notice, credit recognition form, and participant list.
- In the user selection node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and check whether the interaction state is recorded.
- Reference the selection result variable in subsequent nodes and run a trial once, confirm that the branch direction is correct, and that the intake record and completed question items are forwarded to the organizer for handling.