What this category's data looks like
Laboratory hazardous chemicals procurement and ledgers involve three types of materials: procurement applications, usage registrations, and inventory ledgers. Procurement applications record the item name, specification, quantity, application date, and approval signature; usage registrations record the user, quantity used, date of use, and custodian signature; inventory ledgers record the balance quantity, date, and inventory count signature. Materials are summarized weekly or monthly, and the fields are mainly name, quantity, date, and signature. When entering this function, procurement applications and usage registrations serve as the sources of request body fields, while the inventory ledger serves as the verification baseline. The three exchange data with external systems through the HTTP interface, and the progress table and statistical scope description are completed by subsequent nodes parsing the response or by the external system handling it as agreed.
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 description are completed by subsequent nodes parsing the response, or by the external system handling it as agreed. The HTTP module sends a request to the target address, and variables can be used as placeholders in 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 |
|---|---|---|
| Procurement application | Whether the name, quantity, date, and signature are consistent with the usage registration | Check the request body fields against the external interface agreement, and compare the response using a sample request |
| Usage registration | Whether the quantity used and date match the inventory ledger | Check the source of each placeholder in the variables panel, and confirm that variables can be resolved into actual values |
| Inventory ledger | Whether the balance quantity and inventory count date are synchronized with the versions of the two materials | View the fully rendered address in the request preview, and check Authorization and the returned fields |
| HTTP response body | Whether the status code and returned fields cover the fields required for progress records | Compare the responseData fields with the sample, and confirm that the statistical scope is written into the header |
Three common errors
- Symptom: The name and quantity of the same record do not match between the procurement application and the usage registration. Cause: The request body fields were not mapped according to the external interface agreement, and the variable sources were not checked one by one.
- Symptom: The dates in the inventory ledger and the usage registration are inconsistent, and the versions are not synchronized. Cause: The output of the preceding node was not updated, and the request header authentication information does not match the external system's requirements.
- Symptom: Signatures or receipts are missing, and the statistical counts do not match. Cause: The external system received empty fields, the response body was not written back as agreed, and subsequent nodes did not parse the response.
How to verify the setup
Acceptance for this function: preview the rendered request, check the status code and returned fields, then compare the result against a sample, and confirm that the three placeholders Authorization, variables, and responseData are all traceable.
Business test: use one week of records to verify the totals, check whether the scope and exceptions are clearly stated, and confirm that the record count and statistical count match and that the scope is written into the header.
- In the request preview, check the fully rendered address and request header names, and confirm that the path parameters and request body fields are consistent with the external interface agreement.
- In the variables panel, check the source of each placeholder, compare the returned fields using a sample request, and confirm that the statistical scope and exceptions are written into the header.