What this category's data looks like
This page centers on credit management for primary and secondary school teacher training, focusing on the version and change maintenance of three types of materials: training notices, credit recognition forms, and participant lists. Training notices are drafted by the training management department and state the training name, start and end dates, and the conversion rules between class hours and credits; credit recognition forms are filled in by the school where the participating teacher works or by the training institution, and include name, ID number, training program, recognized credits, signature, and date; participant lists are compiled by the organizer and include name, unit, participation status, and receipt. The fields of the three types of materials cross-reference one another, and the name, quantity, and date of the same teacher and the same program must be consistent across the two materials. The update rhythm of the materials is affected by training batches, policy adjustments, and supplementary entries; old versions must be traceable, and the current version must be unique. After entering the HTTP interface and external systems, training notices and participant lists often serve as sources of request body fields, credit recognition forms serve as the basis for verification, and variables are injected from the output of preceding nodes or from global variables.
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 version ledger and change records are parsed from the response by subsequent nodes, or handled by the external system according to the agreement and then completed. The HTTP node is only responsible for sending requests according to the agreement, and does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Training notice | The training name, start and end dates, and the conversion rules between class hours and credits must be consistent with the current version, and the old version must be traceable | Check whether the request body fields reference the dates and credit rules of the current notice, and compare the version identifier returned in responseData |
| Credit recognition form | The name, ID number, training program, recognized credits, signature, and date must match the participant list | Use one sample request to compare the returned fields, check whether the recognized credits are consistent with the quantity in the participant list, and mark an anomaly when the signature or receipt is missing |
| Participant list | The name, unit, participation status, and receipt must be synchronized with the training notice batch | Check the list source in variables in the variable panel, and confirm that the value source of the request header Authorization meets the requirements of the external system |
| HTTP node output | The response body, status code, and returned fields can be parsed by subsequent nodes, and references are updated synchronously | Preview the rendered request, check the status code and returned fields, and after changing one piece of content, see whether the version number and references are updated synchronously |
Three common errors
- Symptom: The name or credit quantity of the same teacher does not match between the two materials. Cause: The training notice and the credit recognition form are maintained separately, and the current version is not used as the sole reference source.
- Symptom: The old notice has been changed, but the participant list still references the old date. Cause: The version was not synchronized, and the HTTP request body fields were not updated along with the version ledger.
- Symptom: The credit recognition form lacks a signature or receipt, and the external system receives empty fields. Cause: The request body fields are inconsistent with the external interface agreement, and the variable sources were not checked.
How to verify the setup
Acceptance of this feature: preview the rendered request, check the status code and returned fields, then compare the result against one sample, and confirm that the three identifiers variables, Authorization, and responseData can all be traced to specific sources.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the variable panel, check the source of each placeholder and confirm that the variables in the request URL, request headers, and request body can be resolved into actual values.
- Use one sample request to compare the returned fields, check that the current version is unique, the old version is traceable, and references are synchronized, and record a change when the signature or receipt is missing.