What this category's data looks like
Materials for laboratory hazardous chemical procurement and ledgers usually include three types: hazardous chemical procurement applications, usage registration records, and inventory ledgers. Procurement applications come from the research group or laboratory supervisor, submitted by batch or quarter, with fields including product name, specification, quantity, purpose, supplier, expected arrival date, and signature; usage registration records come from the user, filled in for each usage, with fields including product name, quantity, usage date, purpose, and user signature; inventory ledgers are maintained by the custodian, updated weekly or monthly, with fields including balance quantity, storage location, update date, and review signature. When the three types of materials enter the form input node, each plays a different role: the procurement application determines the authorization scope and the application basis for the external entry point, the usage registration record determines the visible scope and usage records, and the inventory ledger determines the balance and dates that can be displayed in external services. The update rhythm is mainly immediate for usage, periodic for ledgers, and on demand for procurement, and the field characteristics are concentrated in four items: name, quantity, date, and signature. Any misalignment will affect the determination of authorized access and external services.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The external entry point and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and records the workflow state. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemical procurement application | The product name, quantity, date, and signature in the procurement application must be aligned item by item with the usage registration record and inventory ledger; the authorization scope is defined by the user and purpose in the application | Check the field names and required settings one by one in the node configuration, and after submission, reference the formInputResult field in subsequent nodes for a trial run |
| Usage registration record | The name, quantity, usage date, and user signature in the usage registration record must be consistent with the procurement application and inventory ledger; the visible scope is limited by the identity of the user | Check the required settings one by one, submit once with a restricted identity, and check whether the field values obtained by subsequent nodes are consistent with the registration |
| Inventory ledger | The balance quantity, update date, and review signature in the ledger must match the procurement application and usage registration record; external services only display the balance within the set scope | Reference the userSelect and formInputResult fields in subsequent nodes for a trial run, and check whether the ledger fields are correctly passed |
| External entry point and authorization scope | The visitor identity matches the visible scope, and unauthorized content is not visible; the entry point fields are consistent with the authorization objects of the application, registration, and ledger | Access once with a restricted identity, see whether the visible scope matches the settings, and check whether the userSelect selection result falls within 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 filled in separately without item-by-item alignment, and the field values are passed directly to subsequent nodes after submission.
- Symptom: The usage registration date and the ledger update date are inconsistent, and the balance displayed externally conflicts with the usage record. Cause: The versions are not synchronized; usage is updated immediately while the ledger is updated weekly, so data is misaligned in the interim.
- Symptom: The procurement application lacks the supervisor's signature, the usage registration lacks the user's receipt, and the authorization scope cannot be determined. Cause: Key material fields are not marked as required, submission is not blocked, and subsequent nodes cannot obtain the signature basis.
How to verify the setup
Acceptance of this feature: fill in and submit once, check whether the field values obtained by subsequent nodes are consistent with the filled-in content, and confirm that the formInputResult field can be referenced in subsequent nodes.
Business test: access once with a restricted identity, see whether the visible scope matches the settings, unauthorized content is not visible, and the userSelect selection result falls within the authorization scope.
- Check the field names and required markers one by one in the node configuration to ensure that key material fields are marked as required, and after submission, reference the
formInputResultfield in subsequent nodes for a trial run. - Submit a usage registration once with a restricted identity, check the name, quantity, date, and signature field values obtained by subsequent nodes, and check the passing results of
userSelectandformInput.