What this category's data looks like
This page addresses primary and secondary school teacher training credit management. The materials come from training notices, credit recognition forms, and participant lists. The update cadence advances with training batches and recognition cycles. Fields cover teacher name, ID number, subject, training program name, number of training hours, credit value, training start and end dates, signature field, and receipt number. When entering workflow orchestration, the training notice is responsible for triggering the branch starting point, the participant list provides the personnel roster, and the credit recognition form carries the final recognition result; the three enter the user selection node in different roles, and the node records the interaction state and outputs the branch direction, so that subsequent nodes can continue executing deployment, operations, and application handover according to the branch.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branch), outputting the branch direction and interaction state record. The handover-ready deployment state and operation records are completed by subsequent nodes continuing execution according to the branch. When the 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 | The training program name, start and end dates in the notice must be compared item by item with the participant list and credit recognition form, and signatures and receipt numbers must be complete | In the node, check the options and branch connections one by one, reference variables and run a trial once, then view the node status in the run records |
| Participant list | The teacher names, ID numbers, subjects, and number of people in the list must correspond one by one with the credit recognition form, and dates and signatures must not be missing | Trigger an interaction once, reference the selection result variable corresponding to nodeId in a subsequent node, and check whether that variable has been passed to the subsequent node |
| Credit recognition form | The number of training hours, credit value, and recognition date in the recognition form must be consistent with the training notice and participant list, and signatures or receipts must be complete | In the node, check the options and branch connections one by one, and after a trial run, view the branch direction and interaction state in the run records |
| Deployment state and operation records | Version, connection, and task records must be consistent, and after checking the handover form item by item there must be no missing items | Check the handover form item by item once, see which record is missing, and check whether the variables and nodeId references are consistent |
Three common errors
- Symptom: The program name, number of training hours, and dates for 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 was not performed before entering the node.
- Symptom: The number of people in the participant list is inconsistent with the number of people in the credit recognition form, and receipt numbers are missing. Cause: After the list was updated, it was not synchronized to the recognition form, and the signature or receipt step was missed.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to the subsequent node.
How to verify the setup
Acceptance of this function: run a trial for each option one by one, check the branch direction and interaction state in the run records, and confirm that the variables and nodeId references are correct and that the selection result variable has been passed to the subsequent node.
Business test: check the handover form item by item once, see which record is missing, confirm that version, connection, and task records are consistent, and then hand over to operations or the next shift.
- In the node, check the options and branch connections one by one, trigger an interaction once, and view the node status and branch direction in the run records.
- Reference the selection result variable in a subsequent node and run a trial once, then check the fields, dates, and signatures of the training notice, participant list, and credit recognition form item by item according to the handover form.