What this category's data looks like
Materials for safety grading and classification of university laboratories come from laboratory grading and classification tables, hazard source lists, and safety responsibility statements. The grading and classification table registers entries one by one by laboratory room and category; the hazard source list records type, quantity, and storage location; the safety responsibility statement is tied to the responsible person and the signing date. In terms of update cadence, the grading and classification table is updated as laboratories are adjusted or during semester reviews, the hazard source list changes with procurement, requisition, and disposal, and responsibility statements are refreshed with personnel changes or annual signing. Field characteristics are concentrated in four categories: name, quantity, date, and signature. The naming, counts, and effective dates of the same laboratory across different materials need to be reconcilable. When materials enter the progress record and statistical verification function, the grading and classification table provides the laboratory dimension and category, the hazard source list provides quantity and location, and the responsibility statement provides signature and receipt status. Together, the three form the original basis for 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 are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the rest. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | The name, category, and effective date must reconcile with the hazard source list and safety responsibility statement | Compare the name and date of the same laboratory across the three materials one by one; mark inconsistencies and trace them back to the original registration |
| Hazard source list | Quantity and storage location must be placed in the table header within the statistical scope, and exceptions must be noted | Summarize quantities weekly, check whether the total matches the item-by-item records, and list exceptions separately |
| Safety responsibility statement | Signature and receipt status must be traceable to the responsible person and signing date | Check the signature field and receipt records; list entries missing a signature or receipt separately and note the reason |
| HTTP request | Variable placeholders in the request URL, request headers, and request body can be resolved into actual values | View the fully rendered URL in the request preview, check the Authorization request header and the source of variables, and compare the responseData of one sample |
Three common errors
- Symptom: the name of the same laboratory is inconsistent between the grading and classification table and the hazard source list. Cause: the two materials were registered by different personnel at different times, without unified naming and synchronized verification.
- Symptom: the hazard source quantity does not match between the list and the statistical table. Cause: after requisition or disposal, only one place was updated, versions were not synchronized, and old data was still used during statistics.
- Symptom: the safety responsibility statement is missing a signature or receipt. Cause: after personnel changes, supplementary signing was not done in time, or the receipt was not archived, making the responsible person untraceable during verification.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that Authorization, variables, and responseData are traceable in all three places.
Business test: use one week of records to check the total, and see whether the scope and exceptions are clearly stated; the number of records and the statistical count should match, and the scope should be written into the table header.
- Check the source of each placeholder in the variables panel, and confirm that variables in the request URL, request headers, and request body can be resolved into actual values.
- Use one sample request to compare returned fields, check whether the external system receives empty fields or returns 401, and record timeout situations.