What this category's data looks like
This page addresses authorized access and external services for university laboratory safety grading and classification. The materials come from three types: the laboratory grading and classification table, the hazard source list, and the safety responsibility statement. The grading and classification table provides the laboratory level, hazard source category, and responsibility tier; the hazard source list records the name, quantity, storage location, and update date; the safety responsibility statement carries the signature, receipt, and version date. The three types of materials are updated by semester or academic year, and are revised in sync when hazard sources are added or removed or when the responsible person changes. When entering this function, the grading and classification table serves as the primary basis for the authorization scope, the hazard source list is used to verify the completeness of visible fields, and the safety responsibility statement is used to confirm the identity boundary of the external service recipient. When the external service recipient is a parent or a superior, the materials must first complete internal verification before entering the HTTP interface step.
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 externally available entry point and authorization scope are determined by subsequent nodes parsing the response, or are completed by an external system according to the agreement. The HTTP module sends a request 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 |
|---|---|---|
| Laboratory grading and classification table | Whether the level, hazard source category, and responsibility tier fields are consistent with the hazard source list | Compare the name, quantity, and date of the same laboratory in the two materials, and check whether the signature and receipt are complete |
| Hazard source list | Whether the name, quantity, storage location, and update date can support the determination of the visible scope | Use a sample request to compare the returned fields, and check the source of variables in the variable panel |
| Safety responsibility statement | Whether the signature, receipt, and version date are in sync with the current grading and classification table | Check the version date of the responsibility statement, and confirm that records missing a signature or receipt do not enter the external entry point |
| Request headers and request body | Authentication information is passed in according to the external system's requirements, and the fields are consistent with the external interface agreement | Check the Authorization name and the source of its value, and check whether the request body fields are empty |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the grading and classification table and the hazard source list. Cause: The two materials are maintained separately, without cross-checking.
- Symptom: The version of the safety responsibility statement is not in sync, and an old-version signature is still being referenced. Cause: After revision, the receipt was not returned, and the version date was not updated.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information was not passed in according to the external system's requirements, or the request body fields are inconsistent with the interface agreement.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, and then compare the responseData result against a sample.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting.
- In the request preview, view the complete rendered address, and confirm that the path parameter placeholders can be resolved into actual values.
- In the variable panel, check the source of each placeholder, and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes.