What this category's data looks like
This category's data looks like this: Laboratory hazardous chemicals procurement and ledger materials include three types: hazardous chemicals procurement applications, requisition registrations, and inventory ledgers. Procurement applications record the product name, specification, quantity, application date, and approval signature; requisition registrations record the requisitioner, requisition quantity, requisition date, and issuance signature; inventory ledgers record the balance quantity, inbound date, outbound date, and custodian signature. These materials are updated on a rolling basis by batch and shift, and fields flow among paper documents, spreadsheets, and system records, where naming conventions, quantity units, and date formats are often inconsistent. When entering workflow orchestration, procurement applications serve as trigger-side materials, requisition registrations serve as verification-side materials, and inventory ledgers serve as comparison-side materials, each taking on a different role for subsequent nodes to continue executing along branches.
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 handover-ready deployment status and operation records are completed by subsequent nodes continuing execution along branches. When the user selection node is triggered, the conversation enters an interaction 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 |
|---|---|---|
| User selection node | Each option corresponds to one branch, and the option-to-branch connections must be checked one by one | Check the options and branch connections one by one in the node, confirm that options and branches correspond one-to-one, and record nodeId and the interaction status |
| Hazardous chemicals procurement application | The product name, specification, quantity, application date, and approval signature must be consistent with the requisition registration and inventory ledger | Compare the name, quantity, and date in the procurement application and requisition registration item by item, check whether the signatures are complete, and verify whether the variables references are consistent |
| Requisition registration | The requisitioner, requisition quantity, requisition date, and issuance signature must be consistent with the inventory ledger | Compare the name, quantity, and date in the requisition registration and inventory ledger item by item, check whether the receipt is retained, and verify whether the variables references are consistent |
| Inventory ledger | The balance quantity, inbound date, outbound date, and custodian signature must be consistent with the procurement application and requisition registration | Check the name, quantity, and date in the inventory ledger against the two materials item by item, check whether the versions are synchronized, and verify the nodeId and variables references |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the procurement application and the requisition registration. Cause: The two materials were filled in separately, without item-by-item comparison using the same field definitions.
- Symptom: The inventory ledger version is not synchronized, and the balance quantity is inconsistent with the requisition registration. Cause: Ledger updates lag behind requisition records, and versions were not checked during handover.
- Symptom: The procurement application lacks an approval signature, and the requisition registration lacks an issuance receipt. Cause: The handover form did not check signatures and receipts item by item, and material flow was interrupted.
How to verify the setup
How to verify the setup: Acceptance for this feature: run a trial for each option one by one, check the branch directions and interaction status in the run records, confirm that each option corresponds to the correct branch, that the interaction status is recorded, and that the selection result variable has been passed to subsequent nodes, and verify the nodeId and variables references.
Business test: Check once item by item according to the handover form, see which record is missing, and confirm that the version, connections, and task records are consistent.
- Check the options and branch connections one by one in the node, and after the trial run, view the node status and branch directions in the run records, and record
nodeIdand the interaction status - Reference the selection result variable in subsequent nodes and run a trial once to confirm that
variableshas been passed in; verify the name, quantity, date, and signatures of the procurement application, requisition registration, and inventory ledger