What this category's data looks like
In the scheduling and class-hour deduction scenario of training institutions, the materials entering the exception tracing and manual review function mainly fall into three categories: class schedules, class-hour deduction records, and schedule change requests. Class schedules are usually updated weekly or monthly, with fields including course name, class date, instructor, class, and signature field; class-hour deduction records are generated with each post-class registration, including student name, deducted class hours, deduction date, and receipt; schedule change requests are initiated by academic affairs staff or instructors, including the original class date, the adjusted date, the reason for the change, and approval signature. The three types of materials play different roles in exception tracing: the class schedule is the baseline reference, the class-hour deduction record is the execution voucher being checked, and the schedule change request is the supplementary basis for explaining date or quantity discrepancies. The update rhythm of materials is affected by scheduling adjustments and supplementary entries, and they need to be archived by batch with original versions retained, so that each item can later be traced back to the source material.
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 "exception list and review conclusion" is parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs of preceding nodes through variables, and authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Whether the course name, class date, instructor, and signature field are consistent with the schedule change request | Take the class schedule and schedule change request for the same class on the same date and compare them field by field, checking whether the date and signature field are complete |
| Class-hour deduction record | Whether the student name, deducted class hours, deduction date, and receipt match the class schedule | Use one sample request to compare the response, checking whether the deducted class hours and deduction date match and whether the receipt is missing |
| Schedule change request | Whether the original class date, adjusted date, and approval signature are in sync with the class schedule version | Check each placeholder source in the variables panel, confirming that the schedule change request version and the class schedule version are not misaligned |
| HTTP request | Whether the request URL, request headers, and request body fields are consistent with the external interface agreement | View the fully rendered URL in the request preview, and check Authorization and the responseData returned fields |
Three common errors
- Symptom: The student name or deducted class hours for the same class-hour deduction record do not match between the class schedule and the class-hour deduction record. Cause: The two materials were entered at different times, and no field-by-field comparison was performed.
- Symptom: The schedule change request has been updated, but the class schedule is still the old version, and the date and instructor do not match. Cause: The versions are not synchronized, and batch archiving and version checking are lacking.
- Symptom: The class-hour deduction record is missing a receipt or the schedule change request is missing an approval signature, so the exception cannot be closed. Cause: Signatures and receipts were not included in the review checklist, and the source materials are incomplete.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample, confirming that the exception list fields in responseData are consistent with the original records.
Business test: create one exception record, see whether it can be traced back to the source material, and check whether the dates, quantities, and signatures in the class schedule, class-hour deduction record, and schedule change request are traceable.
- Check the source of each placeholder in the variables panel, confirm that
variablescan resolve to actual values, and check the request header names and value sources. - Use one sample request to compare the response, check that the request body fields are consistent with the external interface agreement, and hand the exception list and review conclusion to the responsible person for handling.