What this category's data looks like
This category's data looks like this: Foreign teacher appointment and course scheduling involves three types of materials: appointment contracts, work permit materials, and course schedules. Appointment contracts contain the appointment period, position, compensation, signature page, and names of both parties; work permit materials contain passport information, degree certificates, criminal record certificates, medical examination certificates, and issue dates; course schedules contain course names, week numbers, classrooms, instructors, and semester start and end dates. The three types of materials come from different processing stages and have different update rhythms: contracts are revised upon renewal or changes to terms, permit materials are updated upon document validity or supplementary submissions, and course schedules are updated upon scheduling adjustments. After entering the workflow, the appointment contract serves as the main record anchor, work permit materials serve as the basis for qualification verification, and the course schedule serves as the scenario for scheduling and terminology implementation; together, the three support multilingual materials and terminology processing.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), 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 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 |
|---|---|---|
| Appointment contract | Whether fields, dates, and signatures are complete, and whether the same record name and quantity are consistent with the permit materials | Check the contract number, appointment start and end dates, and signature page; use nodeId to locate the node to which the material belongs, and check whether the contract fields in variables are passed to subsequent nodes |
| Work permit materials | Whether the passport number, document validity period, and issue date match the contract record, and whether the receipt is retained | Compare item by item the name spelling, dates, and quantities in the permit materials and the contract; run a trial once and check whether the permit fields in variables are passed along the branch |
| Course schedule | Whether the course name, week numbers, and instructor are consistent with the contract position, and whether the semester start and end dates conflict with the appointment period | Extract three terminology items to compare the course schedule and the contract wording; reference variables in subsequent nodes and run a trial, and check whether the branch corresponding to nodeId follows the selected option |
| Unified terminology glossary and comparison draft | Whether the same terminology is written consistently throughout, and whether the translated name can refer back to the source text | Extract three terminology items to check whether the writing is consistent throughout; check whether each translated name in the comparison draft can refer back to the source text, and confirm that no version is out of sync |
Three common errors
- Phenomenon: The same teacher's name is spelled inconsistently in the appointment contract and work permit materials. Cause: The two materials are entered at different processing stages, versions are not synchronized, and there is no unified terminology glossary as a fallback.
- Phenomenon: The week numbers in the course schedule do not match the appointment start and end dates in the contract, and quantities and dates conflict between the two materials. Cause: After scheduling adjustments, the contract side was not written back, and the node branch did not continue execution according to the updated option.
- Phenomenon: Work permit materials lack a signature or receipt, and the process stops after the interaction is completed. Cause: After the user selection, the corresponding branch was not triggered, the interaction state record was not checked in time, and subsequent nodes had no input.
How to verify the setup
Acceptance of this feature: 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, and that nodeId and variables can be referenced in subsequent nodes.
Business testing: Extract three terminology items to check whether the writing is consistent throughout, check that translated names can refer back to the source text, and confirm that the same record name, quantity, and date are consistent across the appointment contract, work permit materials, and course schedule.
- In the user selection node, check the options and branch connections one by one; after triggering once, view the node status and branch directions in the run records.
- Reference the selection result variable in subsequent nodes and run a trial once; check whether
variablesandnodeIdare correctly passed along the branch, and confirm that no default branch is mistakenly taken.