What this category's data looks like
This category's data involves three types of materials: training notices, credit recognition forms, and participant lists. The training notice provides the project name, start and end dates, and target participants; the credit recognition form carries the study hours, credits, and recognition conclusion; the participant list provides personnel identity and sign-in evidence. The three types of materials are usually generated by training batch and updated in batches as training ends, recognition review is completed, and the list is confirmed. Fields include teacher name, ID document number, project number, course name, number of study hours, recognition date, signature, and receipt. When entering the progress record and statistical verification function, the training notice serves as the source of the project scope, the credit recognition form serves as the source of the credit quantity, and the participant list serves as the source of the number of people and identity. Together, the three support the generation of the progress table and the statistical scope statement.
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 "progress table and statistical scope statement" is parsed from the response by subsequent nodes, or handled externally by an external system according to the agreement.
| Object | Check | Verification action |
|---|---|---|
| Training notice | The project name, start and end dates, and target participants must be consistent between the notice and the recognition form, and signatures and receipts must be complete | Compare the project number and date fields between the notice and the recognition form, and check the signature column and receipt attachments |
| Credit recognition form | The study hours, credits, and recognition date must match between the recognition form and the participant list, and the version must be synchronized | Check the name, quantity, and date in the recognition form and the list item by item, and check the version number and signature |
| Participant list | Personnel identity and sign-in records must be consistent with the recognition form, and missing signatures or receipts must be flagged | Use the list to check the number of people and dates in the recognition form, and check whether receipts and signatures are missing |
| HTTP node | The variables in the request URL and path parameters can be resolved into actual values, and Authorization is passed in according to the external system's requirements | View the fully rendered URL in the request preview, check the request header names and value sources, and use a sample request to compare the returned responseData |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the notice and the recognition form. Cause: The two materials are maintained separately, without field-level comparison and version synchronization.
- Symptom: The number of people in the participant list and the recognition form is inconsistent, and signatures or receipts are missing. Cause: After the list is updated, it is not written back to the recognition form, and the signature step is not closed-loop.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: The source of the
Authorizationvalue is incorrect, or thevariablesplaceholders are not resolved into actual values.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare one sample result to confirm that variables, Authorization, and responseData all conform to the agreement.
Business test: use one week of records to check the totals, and see whether the scope and exceptions are clearly stated.
- In the variable panel, check the source of each placeholder and confirm that the placeholders in the request URL, request headers, and request body can all be traced to global variables, system variables, or outputs from preceding nodes.
- Use a sample request to compare the returned fields, check that the request body fields are consistent with the external interface agreement, and record the array length and the tokens budget of the referenced text.