What this category's data looks like
The materials for credit management of primary and secondary school teacher training include three types: training notice, credit recognition form, and participant list. Their sources are the training project initiation notice, participation registration records, and assessment results. The update rhythm is at three time points: before the project starts, after completion, and during the annual recognition window. The training notice carries the project name, training hours, start and end dates, and reporting requirements; the credit recognition form carries the participant's identity, recognized credits, recognition date, and review signature; the participant list carries name, unit, ID number, and attendance records. When the three types of materials enter the workflow, the training notice serves as the initiation basis, the participant list serves as the personnel roster, and the credit recognition form serves as the result voucher. Their fields must be cross-aligned. If any material lacks a signature or receipt, it is deemed an incomplete handover.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The material drafts that can be issued and the handover records are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Whether the project name, training hours, start and end dates, reporting requirements, and signature field are complete, and whether the dates are consistent with the participant list | Check the fields and signature field item by item, compare the project name and start and end dates of the two materials, and after triggering the user selection node, view the branch direction |
| Credit recognition form | Whether the participant's identity, recognized credits, recognition date, and review signature are complete, and whether the name and quantity are consistent with the participant list | Check the fields and signature, compare the names and number of people in the two materials, reference variables in subsequent nodes, and run a trial once |
| Participant list | Whether the name, unit, ID number, and attendance records are complete, and whether the hours and dates are consistent with the training notice | Check the fields and receipt, compare the dates and quantities of the two materials, and view the interaction status corresponding to nodeId in the run records |
| Handover record | Whether the responsible person, version number, handover date, and receipt status are clear, and whether the version and date are synchronized | Check the responsible person's signature and version date, confirm that missing items are blocked, trigger a user selection once, and check whether the selection result variable is passed to subsequent nodes |
Three common errors
- Phenomenon: The project name or start and end dates of the same record do not match between the training notice and the participant list. Cause: The two materials were drafted separately, and field cross-comparison was not performed before handover.
- Phenomenon: The version of the credit recognition form is not synchronized, and the old and new versions circulate at the same time. Cause: The version number was not updated with modifications, and the handover record did not indicate the version and date.
- Phenomenon: The credit recognition form lacks a review signature or the participant list lacks a receipt. Cause: The handover step did not check the signature field item by item, and missing items were not blocked before entering the next step.
How to verify the setup
Acceptance of this function: Run trials option by option, check the branch direction and interaction status in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and record variables and nodeId.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the user selection node, check the options and branch connections one by one, and after triggering once, view the node status and branch direction in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once to check whether the variable has been passed in; at the same time, compare whether the names, quantities, and dates of the training notice, credit recognition form, and participant list are consistent.