What this category's data looks like
This page addresses the scenario of primary and secondary school teacher training credit management. The materials include three types: training notices, credit recognition forms, and participant lists. Training notices contain the project name, training dates, credit hours, registration conditions, and receipt requirements; credit recognition forms contain teacher names, ID numbers, course names, credit hours, recognition dates, and signature fields; participant lists contain names, units, participation dates, and sign-in status. The three types of materials often exist in parallel in multiple language versions, and terminology and translated names need to refer back to the source text. After the materials enter the workflow, training notices provide the original source of terminology and the publication wording, credit recognition forms provide field comparisons and signature evidence, and participant lists provide consistency verification for personnel and dates. The update rhythm changes with training batches and recognition cycles, and version synchronization and signed receipts are common gaps.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "Unified Terminology Glossary and Comparison Draft" is continued and completed by subsequent nodes according to the branches. 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.
| Object | Check | Verification action |
|---|---|---|
| Training notice | The same terminology is consistent throughout, and translated names can refer back to the source text; the project name, training dates, credit hours, and receipt requirements correspond across language versions | Check the options and branch connections one by one in the node, trigger it once and then view the node status in the run record, and use nodeId to locate the branch |
| Credit recognition form | Teacher names, course names, credit hours, recognition dates, and signature fields are aligned in the multilingual comparison draft, and the names and quantities of the same record do not fail to match across two materials | Reference variables in a subsequent node and run a trial once to check whether the selection result variable has been passed to the subsequent node |
| Participant list | Names, units, participation dates, and sign-in status are consistent with the training notice and credit recognition form, and entries missing signatures or receipts are marked separately | Sample three terms to check whether their spelling is consistent throughout, and verify whether the dates and quantities of the same record match across the two materials |
| Unified terminology glossary and comparison draft | Terminology translated names can refer back to the source text, versions are synchronized, and there are no unsynchronized entries before external publication | Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch |
Three common errors
- Phenomenon: The same teacher's name is written inconsistently in the training notice and the participant list. Cause: Multilingual materials do not use a unified terminology glossary, versions are not synchronized, and field entry wording differs.
- Phenomenon: The training dates and credit hour quantities in the credit recognition form and the participant list do not match. Cause: The two materials are updated separately, no item-by-item comparison is performed, and missing receipts and signatures are not intercepted.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to the subsequent node.
How to verify the setup
Feature acceptance: run trials for each option one by one, and check the branch direction and interaction status in the run record; trigger a user selection node once, confirm that the conversation enters the interaction state and the state is recorded, then check that each option corresponds to one branch, and reference variables and nodeId in a subsequent node to run a trial once.
Business testing: sample three terms to check whether their spelling is consistent throughout, and verify whether the names, quantities, and dates of the same record match across the two materials, and whether entries missing signatures or receipts are marked separately.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and after triggering once, view the node status in the run record.
- Reference
variablesin a subsequent node and run a trial once to confirm that the selection result variable has been passed to the subsequent node, and sample three terms to check whether their spelling is consistent throughout.