What this category's data looks like
The raw materials for this category are mainly three types: compliance training courseware, security operating procedures, and exam records. Courseware comes from the training lead and is updated annually, containing course name, applicable position, effective date, and signature field; operating procedures come from the security management department and are revised by equipment and process, containing step number, risk level, version number, and receipt field; exam records are exported by the assessment system, containing personnel identifier, exam paper name, score, date, and reviewer signature. When the three types of materials enter the exception tracing and manual review function, their roles differ: courseware and procedures serve as the comparison baseline, exam records serve as the object being traced, and together they support the exception list and review conclusions. In terms of update cadence, courseware is revised immediately as regulations change, procedures are reviewed quarterly, and exam records are generated per session. Field characteristics center on four types: name, quantity, date, and signature; version number and receipt field are the key to judging whether things are in sync.
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 exception list and review conclusions are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP module sends requests to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Whether the courseware name, applicable position, effective date, and signature field match the exam paper name, date, and reviewer signature in the exam records | In the variable panel, check the source of each placeholder, and confirm that after the courseware fields are mapped to the request body they are compared item by item with the exam records |
| Security operating procedures | Whether the step number, risk level, version number, and receipt field are in sync with the courseware and exam records, and whether the receipt is missing | Use a sample request to compare the response, and check whether the procedure version number and receipt field appear in the returned fields |
| Exam records | Whether the name, quantity, and date of the same record are consistent across the courseware and procedures, and whether the reviewer signature is complete | In the request preview, look at the fully rendered address, and confirm that the exam record identifier and date can be traced back to the source materials |
| Request headers and authentication | Authorization is passed in according to the external system's requirements, and the value source of variables is traceable | Check the request header names and value sources, and confirm that the responseData fields are consistent with the agreement |
Three common errors
- Symptom: The name and date of the same exam do not match between the courseware and the exam records. Cause: The two materials are maintained separately, lacking a unified comparison field.
- Symptom: The security operating procedure version is not in sync, and the old step number still appears in the review conclusions. Cause: The version number was not updated with the revision, and the request body did not carry the version field.
- Symptom: The review conclusions lack a signature or receipt. Cause: The exam record export did not include the reviewer signature field, and the external system did not return the receipt.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the three placeholders Authorization, variables, and responseData are parsed correctly.
Business test: create an exception record, see whether it can be traced back to the source materials, and check whether the exception list and review conclusions contain support from the original records and the reviewer signature.
- In the variable panel, check the source of each placeholder, and confirm that the fields and dates of the courseware, procedures, and exam records can be traced to specific origins.
- Use a sample request to compare the response, check that the request body fields are consistent with the external interface agreement, and record the signature and receipt status in the returned fields.