What this category's data looks like
This page focuses on progress records and statistics verification for enterprise compliance and safety training. The materials include three categories: compliance training courseware, safety operating procedures, and exam records. The courseware and procedures provide the required learning content, version identifiers, and effective dates, while the exam records provide personnel, session, score, and signed receipt. The materials come from the training organizer, the safety management department, and the assessment executor, and are updated weekly or monthly. Fields include name, quantity, date, version number, and signature field. When entering this function, the courseware and procedures serve as the basis for the definitions, and the exam records serve as the source of records. Together, the three support verification of the progress table and the statistical definition 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 definition statement" is parsed by subsequent nodes from the response, or handled by an external system according to the agreement before continuing.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Whether the name, version number, effective date, and signature field are consistent with the statistical definition statement | In the request preview, view the fully rendered URL and verify whether the variables placeholders are resolved to the courseware version and date |
| Safety operating procedures | Whether the quantity, applicable positions, revision date, and receipt signature match | Verify the request header names and the source of their values, and confirm that Authorization is passed in according to the external system's requirements |
| Exam records | Whether personnel, session, score, date, and signature correspond one by one with the progress table | Use one sample request to compare the response, and verify that the responseData fields are consistent with the external interface agreement |
| Statistical definition statement | Whether the record count and statistical count are equal, and whether exceptional cases are clearly stated | In the variables panel, verify the source of each placeholder and confirm that the definition fields can be traced to specific materials |
Three common errors
- Symptom: The name, quantity, and date of the same training session do not match across two materials. Cause: The courseware and exam records are maintained separately and are not merged under a unified definition.
- Symptom: The procedures have been revised, but the progress table is still counted according to the old version. Cause: The version was not synchronized, and the request body does not reference the latest version identifier.
- Symptom: Exam records lack a signature or receipt, but the statistics still count them as completed. Cause: The definition does not state exceptions, and the external system handles them as empty fields.
How to verify the setup
Acceptance for this function: preview the rendered request, verify the status code and returned fields, then compare the result against one sample to confirm that the values and sources of variables, Authorization, and responseData are consistent.
Business test: use one week of records to verify the totals, and check whether the definitions and exceptions are clearly stated.
- In the variables panel, verify the source of each placeholder and confirm that the variables in the request URL, request headers, and request body can be traced to global variables, system variables, or outputs from preceding nodes.
- Use one sample request to compare the response, verify that the fields received by the external system are non-empty, and record the array length and the tokens budget of the referenced text.