What this category's data looks like
This category's data involves three types of materials: training notices, credit recognition forms, and attendance rosters. Training notices are issued by teacher development institutions and contain the project name, start and end dates, credit hours, and seal; they are the upstream basis for exception tracing. Credit recognition forms are filled out by schools or training units and contain the teacher's name, ID number, course name, recognized credits, and the signature of the person in charge; they are the direct voucher for crediting credits. Attendance rosters are provided by the organizer and contain attendees, attendance days, assessment results, and receipts; they are used for cross-comparison. Materials are updated monthly or by project batch, with fields centered on names, dates, quantities, and signatures. When entering the exception tracing and manual review workflow, notices are used to verify whether the project exists and the date range, recognition forms are used to locate discrepant records, and rosters are used to check attendance and receipts; together, the three support the exception list and review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" 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 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 project name, start and end dates, credit hours, and seal are consistent with the recognition form, and whether the date range can cover the attendance records | Check the options and branch connections one by one in the node, reference nodeId to locate the notice source node, and compare the dates and seal |
| Credit recognition form | Whether the teacher's name, course name, recognized credits, and signature of the person in charge are complete, and whether the name, quantity, and date on the same record match the roster | Reference variables in subsequent nodes and run a trial once, check whether the selection result variable is passed in, and verify the signature and receipt |
| Attendance roster | Whether the attendees, attendance days, assessment results, and receipts are complete, and whether the version is synchronized with the recognition form | Trigger a user selection node once, check the node status in the run record, and confirm the roster version and receipt |
| Exception record | Whether the exception is supported by original records, and whether the reviewer has signed | Create an exception record, trace it back to the source materials, and check the branch direction and interaction state records |
Three common errors
- Symptom: The name or credit quantity of the same teacher does not match between the recognition form and the attendance roster. Cause: The two materials are filled out by different units, and no field-level cross-comparison was performed.
- Symptom: The training notice date has been updated, but the recognition form still references the old version date. Cause: The version was not synchronized, and re-verification was not triggered after the material was updated.
- Symptom: The recognition form lacks the signature of the person in charge, or the attendance roster lacks a receipt. Cause: The signature and receipt fields were not validated during material archiving, and the exception record has no original support.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction state in the run record, and confirm that nodeId, variables, and the selection result variable are passed correctly.
Business test: Create an exception record, see whether it can be traced back to the source materials, and check whether the exception list and review conclusions are completed by subsequent nodes continuing execution according to the branch.
- Check the options and branch connections one by one in the node, trigger a user selection node once, and view the node status and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once, confirm that
variableshas been passed in, and then verify the signatures and original records of the exception list and review conclusions.