What this category's data looks like
This category's data involves three core types of materials: appointment contracts, work permit materials, and course scheduling tables. The appointment contract records the teacher's name, position, start and end dates of the appointment period, and signatures of both parties; the work permit materials record the permit number, validity period, issuance date, and receipt; the course scheduling table records the course name, number of class hours, teaching dates, and scheduling signature. The three types of materials come from different sources: the contract is issued by the human resources department, the permit materials are provided by the foreign affairs department, and the course table is generated by academic scheduling. In terms of update cadence, the contract is updated upon renewal or change, the permit materials are updated upon approval and extension, and the course table is adjusted by semester or month. When the materials enter the exception tracing and manual review function, the contract and permit materials serve as the original basis for appointment compliance, and the course table serves as the comparison benchmark for scheduling execution. The fields of the three must be checked item by item in the form, forming a traceable exception list and review conclusion.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The "exception list and review conclusion" is completed by subsequent nodes or manually afterward. After the form input node is triggered, the conversation enters an interactive state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | The teacher's name, position, start and end dates of the appointment period, and signature in the contract must be compared item by item with the work permit materials and the course scheduling table; names, dates, and quantities must not contradict each other | Check the contract field names one by one in the form fields, confirm that the required markers cover the key material fields, and after submission check whether subsequent nodes can retrieve the corresponding field values |
| Work permit materials | The permit number, validity period, issuance date, and receipt must be cross-checked with the appointment period in the appointment contract and the teaching dates in the course scheduling table; the version should be synchronized and no signature or receipt should be missing | Check whether the required settings cover the permit number and validity period, and after submission reference the formInputResult field for a trial run to confirm that subsequent nodes can retrieve the work permit material field values |
| Course scheduling table | The course name, number of class hours, teaching dates, and scheduling signature must be consistent with the position in the appointment contract and the validity period in the work permit materials; if the quantity and dates of the same record do not match across the two materials, it is an exception | Check the course field names one by one in the node configuration, and after submission check whether subsequent nodes can retrieve the course scheduling field values; if necessary, use userSelect to select the exception type |
| Exception list and review conclusion | Exception entries must be supported by original records, and the review conclusion must have the reviewer's signature; entries missing a signature or receipt must not enter the handling stage | Create an exception record, fill in the exception description and source material fields in the form, and after submission check the field values retrieved by subsequent nodes to confirm that the source material can be traced |
Three common errors
- Symptom: the same teacher's name is written inconsistently in the appointment contract and the work permit materials. Cause: the two materials are entered by different departments, versions are not synchronized, and the form does not perform field-level comparison.
- Symptom: the number of class hours in the course scheduling table does not match the agreed quantity in the appointment contract. Cause: after scheduling adjustments, only the course table is updated, the contract is not revised in sync, and there is a lack of original record support during exception tracing.
- Symptom: the review conclusion lacks the reviewer's signature or receipt. Cause: the form's required markers do not cover the signature field, subsequent nodes cannot retrieve the signature value after submission, and the manual review step cannot be closed.
How to verify the setup
Acceptance of this function: fill out the form once and submit it, then check whether the field values retrieved by subsequent nodes are consistent with the filled-in content, focusing on whether the formInputResult and selectResult fields can be correctly referenced by subsequent nodes.
Business test: create an exception record, see whether the source material can be traced, and confirm that the exception list and review conclusion are supported by original records and that the reviewer's signature is complete.
- In the node configuration, check one by one whether the form field names correspond one-to-one with the material fields of the appointment contract, work permit materials, and course scheduling table, and confirm that the key material fields are marked as required.
- After submission, reference the
formInputResultfield for a trial run to confirm that subsequent nodes can retrieve the corresponding field values; if they cannot, check whether the field names and reference paths are consistent.