What this category's data looks like
When foreign teacher appointment and course scheduling enter deployment, operations, and application handover, the materials fall into three categories: appointment contracts, work permit materials, and course scheduling tables. Appointment contracts provide position, appointment period, signature, and receipt fields; work permit materials provide permit number, validity period, and issue date; course scheduling tables provide course name, class, week number, period number, and instructor. The three materials enter the workflow in batches: appointment contracts and work permit materials enter at the appointment node, and course scheduling tables enter at the scheduling node, each playing the role of identity verification, permit validity, and class-hour placement. The update rhythm is synchronized with the semester and permit approval documents, and the field characteristics are concentrated in name, ID number, date, signature, and receipt.
Configuration and implementation checks
This stage is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The handover-ready deployment state and operation records are continued and completed by subsequent nodes according to the branches. When a 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.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | Check whether the name, ID number, appointment start and end dates, signature, and receipt are consistent with the work permit materials | Check the options and branch connections one by one in the node, reference variables, and run a trial once |
| Work permit materials | Check whether the permit number, issue date, and validity period cover the appointment period in the appointment contract | Trigger once and view the node status and nodeId in the run records |
| Course scheduling table | Check whether the course name, class, week number, period number, and instructor are consistent with the position in the appointment contract | Reference the selection result variable in subsequent nodes and run a trial once |
| User selection node | Check that each option corresponds to one branch and that the interaction state is recorded | Run a trial for each option one by one, and check the branch direction and interaction state in the run records |
Three common errors
- Symptom: The name and ID number of the same teacher do not match between the appointment contract and the work permit materials. Cause: The two materials were entered at different times, and the fields were not compared item by item against the same record.
- Symptom: The course name and week number in the course scheduling table do not match the position in the appointment contract. Cause: The scheduling version was not synchronized, and the old course scheduling table is still being referenced.
- Symptom: The appointment contract lacks a signature or the work permit materials lack a receipt. Cause: During handover, only the fields were checked, not the signature and receipt, so the materials were not closed-loop.
How to verify the setup
This feature acceptance: run a trial for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables, nodeId, and the option branches correspond.
Business test: check item by item once according to the handover form, see which record is missing, and confirm that the version, connection, and task record are consistent.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger the user selection node once, and check whether the node status and selection result variable in the run records have been passed to subsequent nodes.