What this category's data looks like
Daily materials for university laboratory safety grading and classification management include laboratory grading and classification tables, hazard source lists, and safety responsibility statements. The grading and classification table records the laboratory name, room number, hazard level, and adjustment date; the hazard source list registers the hazard source name, quantity, storage location, and update date; the safety responsibility statement states the responsible person, signature, and receipt date. These materials are updated by semester or academic year, with fields centered on name, quantity, date, and signature. When entering the exception tracing and manual review function, the grading and classification table is used to locate the laboratory and level, the hazard source list is used to check the items and quantities involved in the exception, and the safety responsibility statement is used to confirm the responsible person and signature status; together, the three support the generation of the exception list and review conclusion.
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 conclusion" is parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. The request URL, path parameters, request headers, and request body can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | The name, room number, hazard level, and adjustment date must be consistent with the hazard source list and safety responsibility statement, and the signature field must not be blank | Check the placeholder sources in the variable panel, preview the rendered request URL, and compare the name and date in the returned fields |
| Hazard source list | The hazard source name, quantity, storage location, and update date must match the corresponding records in the grading and classification table, and the version must be synchronized | Use a sample request to compare the response, and check whether the quantity and date fields in responseData are consistent with the list |
| Safety responsibility statement | The responsible person, signature, and receipt date must be complete; a missing signature or receipt is regarded as a failed review | Check the source of the Authorization value in the request header, and confirm the signature status field returned by the external system |
| HTTP node output | The status code and returned fields must be able to support the tracing of the exception list and review conclusion | View the complete rendered URL in the request preview, and check the source of each placeholder in variables |
Three common errors
- Symptom: The name or quantity of the same hazard source does not match between the grading and classification table and the hazard source list. Cause: The two materials are maintained by different personnel, and no cross-check was performed during updates.
- Symptom: The version of the grading and classification table referenced by the exception record is not synchronized with the version of the safety responsibility statement. Cause: After the materials were updated, they were not pushed uniformly, and the old version is still in circulation.
- Symptom: The review conclusion lacks a signature or receipt. Cause: The signature field of the safety responsibility statement was not filled in, or the receipt was not archived together with the exception record.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; at the same time, check the positions of the three identifiers Authorization, variables, and responseData in the request and response.
Business test: create an exception record, see whether it can be traced back to the source materials, and confirm that the exception is supported by original records and the reviewer's signature.
- Check the source of each placeholder in the variable panel, and confirm that the variables in the request URL, path parameters, request headers, and request body can all be resolved into actual values.
- Use a sample request to compare the response, check whether the external system received empty fields, and verify whether the returned fields are consistent with the agreement.