What this category's data looks like
For laboratory hazardous chemicals procurement and ledger, the materials mainly consist of three sets: hazardous chemicals procurement applications, usage registration, and inventory ledger. Procurement applications include product name, specification, quantity, application date, and approval signature; usage registration includes the person taking the materials, quantity taken, purpose, date taken, and issuance signature; inventory ledger includes balance quantity, batch, inbound date, and inventory count records. The three types of materials update at different rhythms: procurement applications are submitted as needs arise, usage registration occurs per instance, and the inventory ledger rolls forward with inventory counts or inbound/outbound movements. When the materials enter workflow orchestration, each plays its role: procurement applications and usage registration form the input for branch decisions, while the inventory ledger serves as the basis for balance verification; the external entry point and authorization scope are further executed by subsequent nodes according to the branch, and the materials themselves do not determine the visible scope.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The external entry point and authorization scope are further completed by subsequent nodes according to the branch. When a node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemicals procurement application | Product name, quantity, application date, and approval signature are consistent across the three materials, and signatures are complete | Check options and branch connections one by one in the node, and access once with a restricted identity to see whether the visible scope of the procurement application matches the configuration |
| Usage registration | The person taking the materials, quantity taken, date taken, and issuance signature correspond to the inventory ledger records | Reference the selection result variable variables in a subsequent node and run a trial once to check the branch direction of the usage registration |
| Inventory ledger | Balance quantity, batch, inbound date, and inventory count record versions are synchronized, with no missing receipts | Trigger a user selection node once, and in the run records view the node status and branch direction by nodeId |
| External entry point and authorization scope | Visitor identity matches the visible scope, and unauthorized access is not visible | Access once with a restricted identity and check whether the entry point's visible scope is consistent with the authorization scope |
Three common errors
- Symptom: The name and quantity of the same batch of hazardous chemicals do not match between the procurement application and the inventory ledger. Cause: The two materials are entered separately, and the batch and balance are not synchronized to the same version.
- Symptom: The usage registration lacks an issuance signature or receipt, and the date is inconsistent with the inbound/outbound date in the inventory ledger. Cause: Registration and ledger updates have different rhythms, and receipts are not recorded in a timely manner.
- Symptom: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: Options and branch connections were not checked one by one, and the interaction state was not fully recorded.
How to verify the setup
Acceptance for this feature: run trials for each option one by one, and check the branch direction and interaction state in the run records; reference the selection result variable variables in a subsequent node, and view the node status by nodeId.
Business test: access once with a restricted identity and see whether the visible scope matches the configuration.
- Check options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a user selection node once, and view the node status and the passing of the selection result variable in the run records.