What this category's data looks like
This page is for the foreign teacher appointment and course scheduling category. The materials come from appointment contracts, work permit materials, and course scheduling tables. The update cadence follows appointment batches and semester scheduling. The field characteristics center on name, ID number, position, class hours, start and end dates, and signature fields. When entering this feature, the appointment contract serves as the main record of the appointment relationship, the work permit materials serve as evidence of admission and validity period, and the course scheduling table serves as the basis for scheduling and class hours. Each of the three plays its own source role and together supports exception tracing and manual review.
Configuration and implementation checks
This step is executed by the workflow node (user selection and branching), outputting branch direction and interaction state records. The "exception list and review conclusion" is then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | Check whether the name, position, start and end dates, and signature are consistent with the work permit materials | Compare the contract and permit materials field by field, check whether the signature field and receipt are complete, and record the locations of discrepancies |
| Course scheduling table | Check whether the class hours, instructor, week numbers, and the position and validity period in the appointment contract correspond | Compare the course scheduling table and the contract item by item by week number, and mark entries whose quantity or dates do not match |
| Work permit materials | Check whether the ID number, permit period, and contract dates are synchronized and the versions are consistent | Check the version number of the permit materials and the version of the contract attachment, and confirm there are no missing signatures or receipts |
| User selection node | Check whether each option corresponds to one branch and record the interaction state | In the node, check the options and branch connections one by one, reference variables in subsequent nodes and run a trial once, and view the node status and nodeId in the run record |
Three common errors
- Symptom: The name and quantity of the same record do not match between the contract and the course scheduling table. Cause: The two materials were entered separately, without field-level comparison and unification.
- Symptom: The version of the work permit materials is not synchronized, and the permit period is inconsistent with the contract dates. Cause: After the materials were updated, they were not written back to the contract attachment, and the version record is missing.
- Symptom: The review conclusion lacks a signature or receipt, and the exception list has no original record support. Cause: The review step did not enforce a trace, and the signature field and receipt were not archived with the process.
How to verify the setup
Feature acceptance: run trials option by option, check the branch direction and interaction state in the run record, confirm that the selection result variable has been passed to subsequent nodes, and check that variables, nodeId, and the option branch connections are consistent.
Business test: create an exception record, see whether it can be traced back to the source material, confirm that the exception has original record support and the reviewer's signature, and then hand it to the responsible person for handling.
- In the user selection node, check the options and branch connections one by one, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial, confirming that after selecting a certain option it follows the corresponding branch and does not follow the default branch.