What this category's data looks like
What this category's data looks like: Laboratory hazardous chemical procurement and ledger materials include three types: hazardous chemical procurement applications, usage registration, and inventory ledgers. Procurement applications record the product name, specification, quantity, application date, and approval signature; usage registration records the user, usage date, actual issued quantity, and receipt signature; inventory ledgers record the balance quantity, inbound and outbound dates, and custodian signature. The three types of materials come from different sources and have different update rhythms: procurement applications are generated with purchase request batches, usage registration is filled in per instance, and inventory ledgers are updated daily or per batch. In terms of field characteristics, name, quantity, date, and signature are common verification items. When entering workflow orchestration, procurement applications serve as the baseline for exception comparison, usage registration serves as evidence on the consumption side, and inventory ledgers serve as evidence on the balance side; each of the three plays its own role as source material for subsequent nodes to trace and review by branch.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction status records. The "exception list and review conclusion" is completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemical procurement application | Whether the name, quantity, application date, and approval signature are consistent with the usage registration and inventory ledger | Compare the product name, quantity, date, and signature of the three materials one by one, and check whether variables are passed to subsequent nodes |
| Usage registration | Whether the user, usage date, actual issued quantity, and receipt signature match the procurement application and inventory ledger | Trace each usage record one by one to the procurement application and ledger, and check the branch direction corresponding to nodeId |
| Inventory ledger | Whether the balance quantity, inbound and outbound dates, and custodian signature match the procurement application and usage registration | Trace back to the two materials by ledger date and quantity, and check the variables references and branch records |
| Exception list and review conclusion | Whether the exception is supported by original records and whether the reviewer has signed | Attach each exception item to the original material number and signature field one by one, and check the branch direction and interaction status records |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the procurement application and the inventory ledger. Cause: The two materials are entered separately, no field-level comparison is performed, and differences are not identified.
- Phenomenon: The usage registration has been updated, but the inventory ledger still remains at the old version. Cause: The versions are not synchronized, the update rhythms differ, and the ledger is not refreshed with the usage records.
- Phenomenon: The usage registration lacks a receipt signature, and the procurement application lacks an approval signature. Cause: The signature step is not closed-loop, and the signature fields are not checked item by item when materials are transferred.
How to verify the setup
How to verify the setup: Acceptance of this feature: run through each option one by one, check the branch direction and interaction status in the run records, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: create one exception record, see whether it can be traced to the source material, and check whether the exception is supported by original records and whether the reviewer has signed.
- In the user selection node, check the options and branch connections one by one, trigger it once, and view the node status and
nodeIdin the run records. - Reference the selection result variable in a subsequent node and run it once, and check whether
variablestake effect and whether the exception list can be traced to the source material.