What this category's data looks like
This category's data involves three types of materials: training notices, credit recognition forms, and participant rosters. A training notice provides the project name, start and end dates, and the organizing unit; a credit recognition form records class hours, credits, and review signatures; a participant roster lists teacher names, units, and participation status. The materials are mostly issued in batches by teacher development institutions, and the update cadence follows the training cycle. Common fields include name, ID number, project number, date, class hours, signature, and receipt. When entering the Q&A acceptance and missing-item follow-up function, the training notice is used to verify the project and dates, the credit recognition form is used to verify the credit amount and signature, and the participant roster is used to verify personnel identity and participation status. The three corroborate one another, and if any one is missing, a follow-up question is triggered.
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 acceptance record and the completed follow-up items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to finish the process. The HTTP module sends a request to the target address. Variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Whether the project name, start and end dates, and organizing unit are consistent with the credit recognition form | Compare the project number and date fields of the two materials, and check the signature or receipt |
| Credit recognition form | Whether class hours, credit amount, and review signature are complete | Check class hours and credits item by item, and check whether the signature field and receipt are missing |
| Participant roster | Whether teacher names, units, and participation status correspond to the recognition form | Match by name and unit, and check the date and status fields |
| HTTP request configuration | Whether the placeholder variables in path parameters, request headers, and request body can be resolved into actual values | View the rendered full address in the request preview, check the Authorization request header and the source of variables, and use a sample request to compare the returned responseData fields |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the training notice and the credit recognition form. Cause: The two materials are filled in by different stages, and no cross-check was performed.
- Symptom: The participant roster version is not synchronized, and the old roster is still referenced. Cause: The attachment was not replaced after the update, and an expired version was read during acceptance.
- Symptom: The credit recognition form lacks a signature or receipt, so it still cannot be completed after follow-up. Cause: The signature was omitted in the material circulation stage, and the receipt was not attached.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, and then compare the result against a sample.
Business test: submit a question missing key information and see whether it asks a follow-up question before answering.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes. - Check the request header names and value sources, confirm that
Authorizationis passed in according to the external system's requirements, and use a sample request to compare theresponseDatareturned fields.