What this category's data looks like
Laboratory hazardous chemical 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, usage date, and custodian signature; inventory ledgers record the balance quantity, batch, update date, and verification signature. When these three types of materials enter the authorized access and external services function, the procurement application serves as the entry basis, the usage registration serves as the process evidence, and the inventory ledger serves as the balance result, jointly determining the visible scope for visitors. The material update rhythm changes with procurement batches and usage frequency. The field characteristics center on name, quantity, date, and signature. The same record must remain consistent across different materials, versions must be synchronized, and signatures and receipts must be complete.
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 externally available entry and authorization scope are determined by subsequent nodes parsing the response, or the external system handles it as agreed and then completes it. Variables can be used as placeholders in all three places: the request URL, request headers, and request body. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Procurement application | The name, quantity, date, and signature must be consistent with the usage registration and inventory ledger | Check the complete rendered URL in the request preview, and compare the name, quantity, date, and signature across the three materials |
| Usage registration | The quantity used, usage date, and custodian signature must be synchronized with the inventory ledger | Check the request header names and value sources, and verify whether Authorization and variables are passed in according to the external system's requirements |
| Inventory ledger | The balance quantity, batch, and update date must match the procurement application and usage registration | Use a sample request to compare the response, and check whether the responseData fields are consistent with the ledger agreement |
| Request body | The fields are consistent with the external interface agreement | Use a sample request to compare the response, and check the field names and value sources |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between two materials. Cause: The procurement application and usage registration are entered separately and are not checked against the same batch.
- Symptom: The version is not synchronized, and the inventory ledger still shows the old balance. Cause: After the usage registration is updated, ledger synchronization is not triggered, and the request body fields take the old values.
- Symptom: Signatures or receipts are missing, and the authorization scope cannot be confirmed. Cause: The approval signature or custodian signature is missing, and the external system receives empty fields.
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 to confirm that the responseData fields are consistent with the agreement.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or the output of preceding nodes. - Check the request header names and value sources, and confirm that
Authorizationis passed in according to the external system's requirements.