What this category's data looks like
The data for this category of credit management for primary and secondary school teacher training mainly consists of three types of materials: training notices, credit recognition forms, and attendance lists. Training notices are issued by the organizing party and include the training name, start and end dates, credit hours, and sign-in requirements; credit recognition forms are filled out by the school where the teacher works and include name, ID document number, training project, recognized credits, and signature of the person in charge; attendance lists are provided by the hosting institution and include name, unit, attendance date, and receipt signature. The three types of materials come from different sources and have different update rhythms. Notices are often rescheduled due to venue or course adjustments, recognition forms are revised multiple times along with the review progress, and lists are supplemented after check-in. When materials enter the workflow, the notice serves as the trigger source for version changes, the recognition form serves as the baseline for field comparison, and the list serves as the basis for verifying signatures and receipts. Together, the three support the generation of the version ledger and change records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. When a node is triggered, the conversation enters an interaction state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option. The version ledger and change records are then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Whether the name and dates of the same training are consistent in the two materials | Check the training name, start and end dates, and credit hour fields in the notice and recognition form, compare item by item, and record differences |
| Credit recognition form | Whether the recognized credits match the sign-in dates and signatures in the attendance list | Check the name, unit, attendance date, signature of the person in charge, and receipt in the recognition form and list; separately mark items missing a signature or receipt |
| Attendance list | When versions are not synchronized, whether the old version is traceable and whether references are synchronized | Reference the selection result variable variables in a subsequent node, run a trial once, and inspect the branch direction and interaction status record corresponding to nodeId |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized | After changing one piece of content, check whether the version number is updated and whether documents referencing that content are synchronized to point to the new version |
Three common errors
- Symptom: The training name, quantity, and dates of the same record do not match between the notice and the recognition form. Cause: The two materials are filled in at different stages, and no field-level comparison is performed before entering the process.
- Symptom: Versions are not synchronized, and the old version is still referenced. Cause: The change only modified a single material, and the version number and effective scope were not registered in the ledger.
- Symptom: The recognition form lacks the signature of the person in charge, and the list lacks a receipt. Cause: The signature and receipt columns were not checked during material circulation, and the process directly entered the next node after interaction was completed.
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 run a trial once referencing this variable in a subsequent node.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and check that the current version is unique, the old version is traceable, and references are synchronized.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and avoid still taking the default branch after selecting an option.
- Trigger a node once, inspect the node status and interaction status record in the run records, and confirm that the process continues after interaction is completed and that the same session does not enter the interaction repeatedly.