What this category's data looks like
For the foreign teacher appointment and course scheduling category, the materials consist of the appointment contract, work permit materials, and the course schedule. The appointment contract provides the appointment relationship, position, term, and signatures/seals; the work permit materials provide the permit category, number, validity period, and approval receipt; the course schedule provides the course name, class, week number, instructor, and signature. The sources are the school's HR, academic affairs, and external approval systems, and the update cadence keeps pace with contract renewals, permit changes, and semester scheduling. The field characteristics center on four types: names, quantities, dates, and signatures: the same teacher's name may be written differently in the contract and the permit materials, the number of class hours may be inconsistent between the contract and the schedule, the permit validity period and the contract term may be misaligned, and receipts and signatures may be missing. When the materials enter the Q&A intake and missing-item follow-up function, the appointment contract is used to confirm the appointment relationship and term, the work permit materials are used to confirm legal eligibility to hold the position, and the course schedule is used to confirm teaching tasks and scheduling status; together the three support question-item identification and follow-up requests for completion.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The intake record and the follow-up question items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP module sends requests to the target address, and variables can be used as placeholders in three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | Whether the name, quantity, date, and signature are consistent with the work permit materials and the course schedule | Check the teacher's name, position, term start and end, number of class hours, and signatures/seals in the contract, and view the fully rendered address and request body fields in the request preview |
| Work permit materials | Whether the permit number, validity period, approval receipt, and signatures/seals are complete and match the contract term | Check the permit category, number, validity period, and receipt signature, and inspect the source of the Authorization value in the request headers |
| Course schedule | Whether the course name, class, week number, instructor, and signature correspond to the contract and permit materials | Check the schedule fields and scheduling dates, compare the response with a sample request, and confirm the field mapping of responseData and variables |
| Q&A intake record | Whether missing items are identified and followed up on, and whether answers are based on materials | Check the question items and follow-up content in the intake record, and confirm which material and which field each missing item comes from |
Three common errors
- Symptom: the same teacher's name is written differently in the contract and the permit materials. Cause: the two materials are entered by different systems, and name normalization has not been done.
- Symptom: the number of class hours does not match between the contract and the course schedule. Cause: after scheduling adjustments, the contract version was not updated in sync.
- Symptom: the permit validity period and the contract term are misaligned, and the receipt or signature is missing. Cause: the approval receipt was not returned, and the material versions were not synchronized.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample, and confirm that the value sources of responseData and variables are traceable.
Business test: submit a question that lacks key information, and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder, and confirm that the variables in the path parameters, request body, and request headers can all be resolved into actual values.
- Check the request header names and value sources, and confirm that
Authorizationis passed in according to the external system's requirements, to avoid returning 401 or the external system receiving empty fields.