What this category's data looks like
This page focuses on Q&A intake and missing-item follow-up for university laboratory safety grading and classification. The materials come from the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. The grading and classification table provides the laboratory name, room number, hazard source category and level, and classification date; the hazard source list provides the hazard source name, quantity, storage location, control measures, and update date; the safety responsibility statement provides the responsible person, signature, signing date, and receipt. When these three types of materials enter this function, their roles differ: the grading and classification table is used to determine the question category and level, the hazard source list is used to verify quantity and date, and the safety responsibility statement is used to confirm signature and receipt. The update cadence is triggered by semester or by changes in hazard sources, and the field characteristics are the four types: name, quantity, date, and signature. During Q&A intake, missing-item follow-up is based on the completeness of the material fields, and answers must cite the original text of the materials.
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 intake records and the completed follow-up items are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to finish the process. The HTTP module sends requests to the target address, and variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Laboratory grading and classification table | Whether the name, quantity, date, and signature fields are complete and consistent with the hazard source list | Verify that the request body fields correspond to the grading and classification table fields, use variables to placehold the name and date, and view the rendered address in the request preview |
| Hazard source list | Whether the hazard source name, quantity, storage location, and update date match the grading and classification table | Verify the Authorization authentication information in the request header, compare the returned fields with a sample request, and confirm there is no conflict in quantity or date |
| Safety responsibility statement | Whether the responsible person, signature, and receipt are complete, and whether the signing date is within the validity period | Verify the signature and receipt identifiers in the returned fields, and check whether responseData contains the missing-item follow-up marker |
| External system interface | Whether the fields are consistent with the external interface agreement, and whether the path parameters and request body variables can be parsed into actual values | Verify the source of the placeholder variables in the request address, check the origin of each placeholder in the variables panel, and compare the returned status code |
Three common errors
- Symptom: The name, quantity, and date of the same laboratory do not match between the grading and classification table and the hazard source list. Cause: The two materials were filled in by different personnel at different times without cross-checking.
- Symptom: The version of the hazard source list is not synchronized, and the old quantity conflicts with the new grading and classification table. Cause: After the update, it was not uniformly replaced, and the external system still references the old data.
- Symptom: The safety responsibility statement lacks a signature or receipt, so the intake record cannot confirm the responsible party. Cause: The signing process was not closed-loop, and the receipt was not returned to the external system.
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 a sample. Check whether the three identifiers Authorization, variables, and responseData appear as agreed, and confirm that the response body fields are consistent with the external interface agreement.
Business test: submit a question that lacks key information and see whether it asks a follow-up before answering. For example, provide only the laboratory name and not the hazard source quantity and date, and observe whether it first asks about the missing items and then gives an answer based on the materials.
- Check the source of each placeholder in the variables panel, and confirm that the variables in the path parameters, request body, and request headers come respectively from global variables, system variables, or the output of preceding nodes.
- Compare the response using a sample request, check that the response body fields are consistent with the external interface agreement, that the status code is normal, and that there are no empty fields or timeouts.