What this category's data looks like
In the laboratory hazardous chemical procurement and ledger scenario, three types of materials enter the workflow simultaneously: hazardous chemical procurement applications, issuance registrations, and inventory ledgers. Procurement applications come from requisition forms submitted by each laboratory group, with fields including item name, specification, quantity, application date, and applicant signature; issuance registrations come from daily warehouse distribution records, with fields including recipient, issued quantity, issuance date, and issuer signature; inventory ledgers come from periodic warehouse counts and inbound/outbound summaries, with fields including balance quantity, batch, count date, and reviewer signature. The three types of materials update at different rhythms: procurement applications are added immediately upon requisition, issuance registrations are recorded per transaction, and inventory ledgers are summarized weekly or monthly. Therefore, the same record may easily fail to match in name, quantity, and date across the two materials, and unsynchronized versions, missing signatures, or missing receipts are also common. When materials enter this function, procurement applications serve as the source to be verified, issuance registrations serve as the intermediate consumption evidence, and inventory ledgers serve as the balance baseline. The three are aligned by item name and batch and then compared field by field, to locate discrepant fields and form a discrepancy list.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. When the user selection node is triggered, the conversation enters an interactive state and the workflow state is recorded. After the user completes the selection, execution continues along the branch corresponding to the selected option. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemical procurement application | Name, quantity, application date, and applicant signature are consistent across the three materials | Align the procurement application and inventory ledger by item name and batch, compare name, quantity, and date field by field, check whether the signature field is complete, and use variables to record the comparison result |
| Issuance registration | Issued quantity, issuance date, and issuer signature are consistent between the issuance registration and inventory ledger | Link the issuance registration and inventory ledger by recipient and issuance date, compare quantity and date, check whether the issuer signature and receipt are missing, and use nodeId to locate the node containing the discrepant record |
| Inventory ledger | Balance quantity, count date, and reviewer signature can be aligned with the procurement application and issuance registration | Summarize inbound and outbound by batch and compare with the balance quantity in the inventory ledger, check the count date and reviewer signature, and mark ledger rows whose versions are not synchronized |
| User selection node | Each option corresponds to one branch, the interaction state is recorded, and the selection result variable has been passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and reference variables in a subsequent node for a trial run |
Three common errors
- Phenomenon: The same record has different name spellings in the procurement application and inventory ledger, and the quantity and date also fail to match. Cause: The two materials are registered at different stages, item names are not unified, and date standards are inconsistent.
- Phenomenon: The issuance registration has been updated, but the inventory ledger is still the old version, and the balance quantity does not match the issuance records. Cause: The ledger is summarized weekly or monthly, versions are not synchronized, and batch alignment fields are missing.
- Phenomenon: The procurement application lacks the applicant signature, and the issuance registration lacks the issuer signature or receipt. Cause: Signatures and receipts were not archived together with the materials, so the responsible stage cannot be confirmed during verification.
How to verify the setup
This function's acceptance: run trials option by option, check the branch directions and interaction states in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that the process continues downward after the interaction is completed.
Business test: use one real record to find fields inconsistent with the ledger, compare name, quantity, date, and signatures, locate discrepant fields and form a discrepancy list, submit it to the reviewer for confirmation and write it back.
- Align the procurement application, issuance registration, and inventory ledger by item name and batch, compare name, quantity, and date field by field, mark discrepant rows, and record missing signatures or receipts.
- Check the options and branch connections one by one in the user selection node, trigger once to view the node status in the run records, and confirm that the selection result variable has been passed to subsequent nodes.