What this category's data looks like
This category's data covers three types of materials: thematic class meeting plans, student comprehensive quality records, and home visit records. Thematic class meeting plans include activity objectives, process, and signature fields; student comprehensive quality records include moral conduct performance, activity participation, and dates; home visit records include visit targets, problem descriptions, and acknowledgments. The materials are updated weekly or monthly by homeroom teachers and grade groups, and the field characteristics are multi-table intersection with signatures and acknowledgments coexisting. When entering the exception tracing and manual review function, the three types of materials serve respectively as comparison sources: thematic class meeting plans provide activity names and dates, student comprehensive quality records provide participation counts and evaluations, and home visit records provide visit times and signatures. The exception list needs to extract original records from these materials, the review conclusion needs to be signed and confirmed by the reviewer, and finally handed to the person in charge for disposition.
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 are parsed from the response by subsequent nodes, or completed by an external system according to the agreement. The HTTP node does not replace the external system in writing to the database or approving; it is only responsible for initiating requests according to the agreement and returning results.
| Object | Check | Verification action |
|---|---|---|
| Thematic class meeting plan | The activity name, date, and signature field must be consistent with the corresponding entries in the comprehensive quality records | In the request preview, check the rendered address and request body fields, and compare the activity name and date in the plan |
| Student comprehensive quality record | The participation count and evaluation date must be mutually traceable with the visit time and acknowledgment in the home visit records | Check the Authorization in the request headers and the source of variables in the variable panel, and confirm the field values |
| Home visit record | The visit target, problem description, and acknowledgment signature must match the roster and dates in the thematic class meeting plan | Use a sample request to compare the returned responseData fields, and check whether the acknowledgment and signature are missing |
| Exception list and review conclusion | Each exception must be supported by an original record, and the reviewer's signature must be complete | Check whether the exception entries in the returned fields correspond one-to-one with the names, quantities, and dates of the source materials |
Three common errors
- Phenomenon: The same activity name is written differently in the thematic class meeting plan and the comprehensive quality record. Cause: The two materials are filled in by different personnel, and the naming rules have not been unified, resulting in failure to match during tracing.
- Phenomenon: The visit date in the home visit record differs by several days from the evaluation date in the comprehensive quality record. Cause: The versions are not synchronized, and after one party modifies it, the other party is not notified to update, causing the dates to mismatch.
- Phenomenon: Entries in the exception list are marked with a review conclusion but lack the reviewer's signature. Cause: The acknowledgment or signature field is not completely filled in, the review process is not closed-loop, and it cannot be handed to the person in charge for disposition.
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 one sample; at the same time confirm the value sources of variables and responseData.
Business test: create one exception record, see whether the source material can be traced, and check whether the names, quantities, dates, and signatures among the thematic class meeting plan, student comprehensive quality record, and home visit record are consistent.
- In the variable panel, check the source of each placeholder, and confirm that the
Authorizationrequest header is passed in according to the external system's requirements. - Use a sample request to compare the returned
responseDatafields, and check whether the exception entries correspond to the names, quantities, and dates of the original records.