What this category's data looks like
This category's data looks like this: Credit management for primary and secondary school teacher training involves three types of materials: training notices, credit recognition forms, and attendance rosters. Training notices come from the project supervisory department, are updated by batch, and contain course name, start and end dates, credit hours, and signature/seal fields; credit recognition forms are consolidated by the teacher's school, are submitted by semester or academic year, and contain name, ID number, course name, recognized credits, and signature field; attendance rosters are provided by the organizing institution, are generated by class session, and contain name, unit, attendance date, attendance, and receipt. When the three types of materials enter the workflow, their roles differ: the training notice serves as the source of definitions, defining recognizable credits and time boundaries; the attendance roster serves as the source of records, providing actual attendance entries; the credit recognition form serves as the object of reconciliation, consolidating the results pending recognition. In terms of update rhythm, notices change with project batches, rosters are archived when class sessions end, and recognition forms are submitted centrally at the end of the semester. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures, and the same record must be aligned item by item across the three materials.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "progress table and statistical definition description" is continued and completed by subsequent nodes according to 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 | Course name, start and end dates, credit hours, and signature/seal fields are aligned item by item with the credit recognition form and attendance roster | In the node, check the options and branch connections one by one, and confirm that the notice definition branch and the roster branch are each independent; reference variables to record the notice number, and reference nodeId to locate the node |
| Credit recognition form | Name, ID number, course name, recognized credits, and signature field are aligned entry by entry with the attendance roster | Trigger the user selection node once, view the node status in the run record, and confirm that after the recognition form branch is selected it enters the consolidation node; check whether the signature field is empty |
| Attendance roster | Name, unit, attendance date, attendance, and receipt are aligned entry by entry with the training notice and credit recognition form | In a subsequent node, reference the selection result variable and run a trial once, confirm that the variables and nodeId carried by the roster branch point correctly, and mark missing receipt items separately |
Three common errors
- Symptom: The same teacher's name is written differently in the training notice and the attendance roster, and the credit recognition form cannot match it. Cause: The three materials are entered separately, the name field has not been standardized, and dates and quantities consequently do not match.
- Symptom: The training notice has already updated the batch, but the attendance roster still uses the old dates, and the recognition form is consolidated according to the old definition. Cause: Versions are not synchronized, the materials circulate separately, and there is a lack of a unified version identifier and comparison step.
- Symptom: The credit recognition form lacks a signature or the attendance roster lacks a receipt, but they are still counted during consolidation. Cause: Signatures and receipts are not used as branch judgment conditions, exception items are not listed separately, and the statistical definition is not written into the header.
How to verify the setup
How to verify the setup: Acceptance of this function: run trials option by option, and check the branch directions and interaction states in the run records; confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are each run once in a trial, checking whether selecting an option still follows the default branch, whether the process stops after the interaction is completed, and whether the same session repeatedly enters the interaction.
Business test: Use one week of records to check the totals, and see whether the definitions and exceptions are clearly written; compare the names, quantities, dates, and signatures of the training notices, credit recognition forms, and attendance rosters item by item, confirm that the record counts and statistical counts match, that the definitions are written into the header, and that exception items are listed separately.
- In the user selection node, check the options and branch connections one by one, trigger it once, then view the node status in the run record, and confirm that the interaction state is recorded and the branch direction is correct.
- In a subsequent node, reference the selection result variable and run a trial once, check whether
variablesandnodeIdpoint to the expected branch, and confirm that missing signature and receipt items in the recognition form and attendance roster have been marked separately.