What this category's data looks like
This page addresses the school moral education and homeroom teacher work scenario. Materials include themed class meeting plans, student comprehensive quality records, and home visit records. Themed class meeting plans contain activity objectives, procedures, dates, and homeroom teacher signatures; student comprehensive quality records contain semester, indicators, quantities, and parent receipts; home visit records contain visit time, subject, content, and signatures of both parties. Sources are submissions from each class and archiving by the moral education office, with updates advancing in three rounds: beginning of semester, midterm, and end of semester. When materials enter this function, plans serve as the version master component, records serve as referenced attachments, and receipts serve as signature credentials, each taking on a different role, used to generate 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 completed by subsequent nodes parsing the response, or by an external system handling it according to the agreement. The request URL, path parameters, request headers, and request body can all use variables placeholders, with variables coming from global variables, system variables, or outputs of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Themed class meeting plan | Whether the name, date, and signature of the same plan are consistent across two materials | In the request preview, check the rendered complete URL and request body fields, and confirm that the plan name, date, and signature sources are traceable |
| Student comprehensive quality record | Whether the semester, indicators, quantities, and parent receipt match | Use a sample request to compare the return, verify that the record fields are consistent with the external interface agreement, and check whether the receipt is missing |
| Home visit record | Whether the visit time, subject, content, and signatures of both parties are synchronized | In the variables panel, check the source of each placeholder, and confirm that the home visit time and signature fields are taken from the current version |
| HTTP module | Whether the placeholders in the request URL and path parameters, request headers, and request body can be resolved into actual values | Check the Authorization request header name and value source, and check whether the returned fields include responseData |
Three common errors
- Symptom: The same home visit record has mismatched names and quantities in the class ledger and the moral education office summary. Cause: The two places maintain their own records and do not synchronize references based on the current version.
- Symptom: After the content of a themed class meeting plan is changed, the version number and references are not updated synchronously. Cause: The change record was not submitted together with the request body fields, and the old version is still referenced.
- Symptom: A student comprehensive quality record is missing the parent receipt or homeroom teacher signature. Cause: The request body fields are empty, and the external system still processes it according to the agreement after receiving empty fields.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that variables placeholders are resolved into actual values, Authorization is passed in according to external requirements, and the return includes responseData.
Business test: change one piece of content and see whether the version number and references are updated synchronously
- In the request preview, check the rendered complete URL and request body fields, tracing each item back to a global variable, system variable, or output of a preceding node
- Use a sample request to compare the return, check the request header name and value source, and confirm that the external interface field agreement is consistent