What this category's data looks like
This page is intended for the scenario of credit management for primary and secondary school teacher training. The materials include three categories: training notices, credit recognition forms, and participant lists. Training notices provide the project name, start and end dates, and signature/seal requirements, and are the original basis for the source of credits; credit recognition forms carry teacher names, subjects, credit hours, and recognition conclusions, and are the core vouchers for crediting credits; participant lists record attendance, sign-ins, and receipts, and are used for cross-verification. The three categories of materials are updated by semester or project batch, and their fields are characterized by name, ID number, date, credit hours, and signature. After entering this function, training notices are used to confirm the project and time range, credit recognition forms are used to extract recognition entries, and participant lists are used to check personnel and attendance. Together, the three support the traceback and version judgment of basis entries.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Basis entries that can be traced back to the original text" are completed by subsequent nodes continuing execution according to the branch. When this 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, start and end dates, and signature/seal are consistent with the credit recognition form, and whether the version is the current one | Check the options and branch connections one by one in the node, trigger it once, then view the node status in the run record to confirm that the notice version and the recognition form reference the same batch |
| Credit recognition form | Whether the teacher name, credit hours, and recognition conclusion can be traced back to the original text of the notice, and whether the signature and receipt are complete | Reference the selection result variable variables in a subsequent node and run a trial once, check the correspondence between the recognition form entries and the original text of the notice, and record missing signature items |
| Participant list | Whether the attendance count, sign-in dates, and number of recognition forms match, and whether the receipts are complete | Locate the list source through nodeId in a subsequent node, run a trial once, and check the consistency of the counts and dates between the list and the recognition form |
| Basis entry | Whether the entry can be traced back to the original text, whether the version is the current one, and whether it matches the material fields | Check the branch direction in the run record, confirm the correspondence between the entry source and the original text of the material, and record items whose versions are not synchronized |
Three common errors
- Phenomenon: The same teacher's name or credit hours do not match between the notice and the recognition form. Cause: The two materials were entered at different times, and cross-checking was not performed before proceeding to subsequent nodes.
- Phenomenon: The recognition form references the dates and project name of an old version of the training notice. Cause: The version was not synchronized, and the selection branch was not re-triggered after the material was updated.
- Phenomenon: The participant list lacks signatures or receipts but is still treated as a valid basis entry. Cause: The verification action did not cover the signature field, and the interaction status record did not reflect the missing items.
How to verify the setup
This function's acceptance: run trials on each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business test: ask a cross-material basis question, see whether the answer gives a traceable source, and check whether the source can be traced back to the original text of the training notice, credit recognition form, or participant list.
- Check the options and branch connections one by one in the node, trigger it once, then view the node status in the run record to confirm that the process continues downward after the interaction is completed.
- Reference the selection result variable
variablesin a subsequent node and run a trial once, and at the same time usenodeIdto locate the source node, checking the branch direction and the traceback relationship of the basis entry.