What this category's data looks like
This category's data looks like this: Foreign teacher appointment and course scheduling involves three core types of materials: appointment contracts, work permit materials, and course scheduling tables. Appointment contracts come from the personnel and foreign affairs departments and are updated by semester or appointment period; fields include name, passport number, position, compensation, signature, and date. Work permit materials come from the foreign experts and entry-exit stages and are updated by approval batch; fields include education, no criminal record, medical examination, employing unit, and validity period. Course scheduling tables come from academic affairs and departments and are adjusted weekly or monthly; fields include course name, class, class hours, classroom, instructor, and start and end dates. When the three types of materials enter workflow orchestration, appointment contracts and work permit materials are the baseline records for responsibility handover, and course scheduling tables are the execution basis for scheduling and sign-off; each plays the role of field source, version anchor, and signature receipt.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction state records. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option. "Draft materials that can be issued and handover records" are then completed by subsequent nodes continuing execution along the branch.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | Fields are complete, the responsible person is clear, and the version and date are consistent; check name, passport number, position, compensation, signature, and date | In the node, check the options and branch connections one by one, reference variables to record contract fields and signature receipts, and compare names, quantities, and dates item by item against the work permit materials and course scheduling table |
| Work permit materials | Fields are complete, the responsible person is clear, and the version and date are consistent; check education, no criminal record, medical examination, employing unit, and validity period | In subsequent nodes, reference the selection result variable and run a trial once, check the branch direction corresponding to nodeId, and confirm that the name, employing unit, and validity period in the permit materials are consistent with the appointment contract |
| Course scheduling table | Fields are complete, the responsible person is clear, and the version and date are consistent; check course name, class, class hours, classroom, instructor, and start and end dates | Trigger an interaction once, view the node status in the run record, and check whether the instructor name, dates, and class hour quantities in the course scheduling table match those in the appointment contract and work permit materials |
| Handover record | The responsible person is clear, the version and date are consistent, and missing items are blocked; check the sign-off person, handover time, receipt, and version number | In the node, check the options and branch connections one by one, check the sign-off fields and receipt status in variables, and confirm that the process is blocked when the version is not synchronized or a signature is missing |
Three common errors
- Symptom: The same teacher's name is written inconsistently in the appointment contract and work permit materials. Cause: The materials are drafted in different stages, are not checked against a unified field template, and missing items are not blocked during handover.
- Symptom: The class hour quantity in the course scheduling table does not match the appointment contract. Cause: After scheduling adjustments, the version is not synchronized, the handover record still references the old version, and deviations appear in dates and quantities.
- Symptom: The handover record lacks a signature or receipt, but the process continues downward. Cause: The selection result variable is not correctly passed to subsequent nodes, and the branch direction and interaction state record are not verified.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that nodeId and variables are correctly referenced in subsequent nodes, and that selecting a certain option does not still follow the default branch.
Business test: draft one copy according to the template and complete one handover, see whether missing items are blocked, and confirm that the fields, dates, and signatures of the appointment contract, work permit materials, and course scheduling table are complete.
- In the node, check the options and branch connections one by one, trigger an interaction once, then view the node status in the run record, and confirm that the same session does not enter the interaction repeatedly.
- In subsequent nodes, reference the selection result variable and run a trial once, check the transfer results of
variablesandnodeId, and confirm that the process continues downward after the interaction is completed.