What this category's data looks like
This category's data involves three types of materials: hazardous chemical procurement applications, usage registrations, and inventory ledgers. Procurement applications record the product name, specification, quantity, application date, and approval signature; usage registrations record the person taking the chemicals, quantity taken, date taken, and custodian signature; inventory ledgers record the balance quantity, inbound date, and inventory count receipt. The three types of materials are updated weekly or monthly, field names and quantity units tend to drift between versions, and when signatures or receipts are missing, the loop cannot be closed. When the materials enter the conversation log feature, each is pulled in pages as question-and-answer evidence in the session, used to reconcile the number of records and statistical totals, and does not directly serve as the version basis for the business ledger.
Configuration and implementation checks
This step is performed by the conversation log interface (by application and session dimension), outputting a session message list and the total number of records, including role and reference information. The progress table and statistical scope description are then completed manually or by an external system. The message list is not the version ledger of business materials; only the session evidence is taken.
| Object | Check | Verification action |
|---|---|---|
| Hazardous chemical procurement application | Whether the fields, dates, and signatures are consistent with the usage registration | Pull the session records by chatId, reconcile the application quantity with the usage quantity, the application date with the usage date, and check whether the approval signature is complete |
| Usage registration | Whether the name, quantity, and date match the inventory ledger | Locate a single record by dataId, reconcile the person taking the chemicals, the quantity taken, and the balance quantity in the inventory ledger, and check the custodian signature or receipt |
| Inventory ledger | Whether the version is synchronized and whether the total matches the total number of records | Open a single record with value, reconcile the reference information and the elapsed-time field, and check whether the ledger version and the weekly report scope are synchronized |
| Conversation log interface output | Whether the total number of records matches the number of records in the paginated list | Pull two pages in succession and compare the offset and total, confirm response code of 200 and that the total number of records total matches the number of items in the list |
Three common errors
- Symptom: The names and quantities of the same batch of hazardous chemicals do not match across the two materials. Cause: Procurement applications and usage registrations each maintain their own fields and are not reconciled under a unified scope.
- Symptom: The inventory ledger version is not synchronized, and the weekly report total is inconsistent with the total number of records. Cause: After the materials are updated, the ledger is not written back, and the statistical scope is not written into the header.
- Symptom: The usage registration lacks a signature or receipt, making it impossible to confirm the fact of usage. Cause: The registration step is not closed-loop, and signatures and receipts are not archived with the records.
How to verify the setup
This feature's acceptance: page through and retrieve all records by the total number of records total, sample one record to reconcile the role, reference information, and time, and confirm response code of 200 and that the number of items in the list matches the total.
Business test: use one week of records to reconcile the total, see whether the scope and exceptions are clearly stated, and confirm that the three materials—procurement applications, usage registrations, and inventory ledgers—match.
- Pull in pages by application and session dimension, reconcile
chatIdwith the actual session, and confirm that the total number of records total matches the number of items in the list. - Open a single record to reconcile
dataIdandvalue, check the reference information and the elapsed-time field, and confirm that each message has an identified role.