What this category's data looks like
This category involves three types of materials: student registration forms, teaching plans, and skills training records. Student registration forms are updated at semester registration nodes, with fields including student name, major, class, registration date, and signature; teaching plans are revised by major and grade, with fields including course name, credit hours, week numbers, instructor, and approval signature; skills training records are generated by training project batches, with fields including project name, equipment number, training date, assessment result, and mentor signature. The sources for multilingual materials and terminology processing are the original texts and translations of the above materials, with update cadence synchronized with academic system nodes, teaching plan revisions, and training batches. When materials enter workflow orchestration, student registration forms are used to determine student identity and stable translated names for professional terminology, teaching plans are used to unify course names and credit hour expressions, and skills training records are used to align project names, equipment terminology, and assessment result expressions; together, the three support the production of a unified terminology glossary and comparison draft.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state 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 state; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | Whether the same student's name, major, registration date, and signature match across the two materials | Compare student name, major, class, registration date, and signature one by one; check options and branch connections one by one in the node to confirm branch directions and interaction state records |
| Teaching plan | Whether the same course's name, credit hours, week numbers, and approval signature are consistent across the two materials | Compare course name, credit hours, week numbers, and approval signature one by one; reference variables in subsequent nodes and run a trial to confirm the selection result has been passed to subsequent nodes |
| Skills training record | Whether the same training project's project name, equipment number, quantity, training date, and mentor signature are consistent across the two materials | Compare project name, equipment number, quantity, training date, and mentor signature one by one; check the branch connections and interaction state of the node corresponding to nodeId |
| Unified terminology glossary and comparison draft | Whether the same term is written consistently throughout and whether the translated name can refer back to the original text | Extract three terms and check their writing throughout; check the correspondence between the terminology glossary and the comparison draft to confirm branch directions and interaction state records |
Three common errors
- Symptom: The same record's name, quantity, and date do not match between the student registration form and the teaching plan. Cause: The two materials are updated separately, without field-by-field comparison according to the unified terminology glossary and comparison draft.
- Symptom: After the teaching plan is revised, the skills training record still uses the old course name and credit hours. Cause: The versions are not synchronized, and the branch directions and interaction state records were not re-checked after the materials were updated.
- Symptom: The skills training record lacks a mentor signature or the student registration form lacks a receipt. Cause: When the materials entered the workflow, the signature and receipt fields were not checked item by item, and after the interaction was completed the process stopped without continuing.
How to verify the setup
Feature acceptance: Run a trial for each option, check the branch directions and interaction states in the run records, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business testing: Extract three terms and check whether their writing is consistent throughout; check that the same term is consistent throughout the unified terminology glossary and comparison draft, and that the translated name can refer back to the original text.
- Check options and branch connections one by one in the node; after triggering once, view the node status and branch directions in the run records.
- Reference
variablesin subsequent nodes and run a trial to confirm the selection result has been passed to subsequent nodes, and check the interaction state records of the node corresponding tonodeId.