What this category's data looks like
The data for this category looks like this: Foreign teacher appointment and course scheduling involves three types of materials: appointment contracts, work permit materials, and course scheduling tables. The appointment contract contains name, passport number, position, start and end of appointment period, compensation, and signatures of both parties; the work permit materials contain permit number, issue date, validity period, position, and photo; the course scheduling table contains course name, class, week number, classroom, instructor, and academic affairs signature. The material sources are the school's human resources, academic affairs, and foreign affairs systems. The update rhythm is triggered by contract changes, renewal before permit expiration, and course schedule adjustments by semester. When entering the HTTP interface function, the appointment contract serves as the main record providing identity and appointment period fields, the work permit materials serve as qualification attachments providing permit status, and the course scheduling table serves as scheduling input providing time and class fields. Together, the three support the version ledger and change records.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The version ledger and change records are parsed from the response by subsequent nodes, or handled externally according to the agreement to complete the process.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | Contract fields, appointment period dates, and signatures must be consistent with the work permit materials | Check the contract name, passport number, appointment period start and end, and signature fields, then compare item by item with the work permit materials |
| Work permit materials | Permit number, issue date, validity period, and position must correspond to the contract | Check the permit number, validity period, and position, and check whether signatures or receipts are missing |
| Course scheduling table | Course name, class, week number, and instructor must match the contract appointment period | Check the course table dates and teacher names, and check whether the academic affairs signature and receipt are complete |
| Request and response fields | Path parameters, request headers, and request body fields must be consistent with the external interface agreement | View the rendered full address in the request preview, and compare the returned fields with a sample request |
Three common errors
- Symptom: The same teacher's name is written differently in the contract and the work permit materials. Cause: The two materials are entered separately, without unified field mapping and version synchronization.
- Symptom: The week numbers in the course scheduling table do not match the contract appointment period. Cause: Contract changes did not trigger course table updates, and the old version is still referenced.
- Symptom: The work permit materials lack signatures or receipts, and the interface returns empty fields. Cause: The materials were read by the workflow before completing internal circulation.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample; check whether the three identifiers Authorization, variables, and responseData are traceable.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- In the variable panel, check the source of each placeholder and confirm that the values of
variablesandAuthorizationare traceable. - Use a sample request to compare the response, and record whether the response body and
responseDatafields are consistent with the agreement.