What this category's data looks like
Laboratory hazardous chemicals procurement and ledger materials cover three types of records: hazardous chemicals procurement applications, usage registration, and inventory ledgers. The sources are internal laboratory forms and approval receipts, and the update cadence changes with procurement batches, usage frequency, and monthly inventory counts. Procurement applications include product name, specification, quantity, supplier, application date, and approval signature; usage registration includes the user, purpose, quantity used, date of use, and custodian signature; inventory ledgers include balance quantity, inbound date, outbound date, and inventory count signature. When these three types of materials enter workflow orchestration, the procurement application serves as the branch starting material, usage registration serves as the intermediate flow material, and the inventory ledger serves as the summary verification material. Each assumes a different node role and together they support the generation and traceability of version ledgers and change records.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. 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. The "version ledger and change records" are then completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemicals procurement application | The product name, quantity, date, and signature in the procurement application must correspond item by item with the usage registration and inventory ledger. The name, quantity, and date of the same record in the two materials must not fail to match. | Check the options and branch connections one by one in the node, compare the product name, quantity, and date fields of the procurement application and usage registration, and confirm that the approval signature is complete. |
| Usage registration | The quantity used, date of use, and custodian signature in the usage registration must be consistent with the outbound records in the inventory ledger. When the version is not synchronized, the current version is the sole authoritative one. | Reference variables in subsequent nodes and run a trial once to check whether the dates and quantities in the usage registration and inventory ledger are updated in sync. |
| Inventory ledger | The balance quantity, inbound date, and outbound date in the inventory ledger must form a closed loop with the procurement application and usage registration. Records missing signatures or receipts must not enter the current version. | Trigger the user selection node once, view the node status in the run record, and check whether the branch direction corresponding to nodeId is consistent with the ledger fields. |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the procurement application and usage registration. Cause: The two materials are maintained separately, and the fields and signatures were not compared item by item within the node.
- Symptom: The inventory ledger has been updated, but the usage registration still remains at the old version. Cause: The versions are not synchronized, and the rules that the current version is unique and old versions are traceable were not implemented in the branch.
- Symptom: The procurement application lacks an approval signature or the usage registration lacks a receipt. Cause: The process stops after the interaction is completed, and subsequent nodes do not continue execution according to the branch to complete the missing signatures and receipts.
How to verify the setup
Feature acceptance: run trials option by option, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are queryable in the run record.
Business test: change one piece of content, see whether the version number and references are updated in sync, and confirm that the current version is unique, old versions are traceable, references are synchronized, and the names, quantities, dates, and signatures of the procurement application, usage registration, and inventory ledger remain consistent.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and avoid still taking the default branch after selecting a certain option.
- Trigger the user selection node once, view the node status in the run record, check whether the process continues downward after the interaction is completed, and check whether the same session repeatedly enters the interaction.