What this category's data looks like
This category's data covers three types: procurement applications, usage registrations, and inventory ledgers. Procurement applications contain product name, specification, quantity, application date, and approval signature; usage registrations contain user, usage date, purpose, remaining amount, and custodian signature; inventory ledgers contain inbound and outbound quantities, balance, inventory date, and review receipt. The material sources are internal laboratory circulation and external reporting, and the update rhythm is triggered by each procurement, usage, and inventory event, with fields mainly consisting of names, quantities, dates, and signatures. When entering workflow orchestration, procurement applications serve as the branch starting material, usage registrations serve as the verification material, and inventory ledgers serve as the back-reference material. Multilingual materials and terminology processing need to keep the same term consistent throughout the entire text and ensure translated names can refer back to the original text in a unified terminology glossary and comparison draft.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Procurement application | Hazardous chemicals procurement application fields, dates, and signatures | Check options and branch connections one by one in the node, and see whether the product name, quantity, date, and signature of the procurement application correspond to the branch direction |
| Usage registration | Usage registration fields, dates, and signatures | Reference variables and run a trial once, and check whether the name, quantity, and date of the usage registration and procurement application are consistent |
| Inventory ledger | Inventory ledger fields, dates, and signatures | Reference nodeId and variables in subsequent nodes, and check whether the inventory ledger balance, inventory date, and review receipt are aligned with the usage registration |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the procurement application and the usage registration. Cause: Multilingual materials and terminology processing are not unified, and field mapping lacks back-reference to the comparison draft.
- Phenomenon: The inventory ledger version is not synchronized, and the old balance and the new usage registration coexist. Cause: The branch direction is not recorded, and subsequent nodes continue execution according to the default branch.
- Phenomenon: The usage registration lacks a signature or receipt, and the approval column of the procurement application is blank. Cause: The interaction state record is incomplete, and the selection result variable is not passed to subsequent nodes.
How to verify the setup
This function acceptance: Run trials option by option, check the branch direction and interaction state in the run record, and check whether nodeId and variables are correctly referenced in subsequent nodes.
Business test: Sample three terms and check whether their writing is consistent throughout the entire text, with the same term consistent throughout the entire text and translated names able to refer back to the original text.
- Check options and branch connections one by one in the node, and trigger once to view the node status in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once, and check the branch direction and interaction state record.