What this category's data looks like
This page handles three types of materials for school safety hazard inspections and campus incident reporting: safety inspection forms, hazard rectification ledgers, and emergency incident reports. Safety inspection forms come from daily patrols and are submitted weekly or per inspection; their fields include inspection item, hazard description, and inspector signature. Hazard rectification ledgers are updated by safety officers according to the rectification cycle; their fields include hazard name, rectification quantity, rectification date, and responsible person signature. Emergency incident reports are submitted within a time limit after an incident occurs; their fields include incident name, involved quantity, occurrence date, and receipt. After the three types of materials enter the same object chain, they respectively assume the three roles of discovery, tracking, and reporting, and material verification and discrepancy localization revolve around the name, quantity, date, and signature of the same object.
Configuration and implementation checks
Enable commercial file permissions and give the member read access to the knowledge base.
This part is enforced by member permissions and file-level permissions (server-side authentication), and outputs the set of visible files filtered by member. The "discrepancy list" is completed subsequently by AI nodes, code nodes, or manual work; the file list and retrieval only return the readable set filtered by member. The file list and retrieval return results only within that set; unauthorized files do not occupy a place and are not recalled.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection form | Whether the name, quantity, and date of the same hazard are consistent across the two materials, and whether signatures are complete | Use a restricted member account to view the list and details, check the form's read permission and fields; record inconsistent fields |
| Hazard rectification ledger | Whether the rectification quantity and rectification date match the corresponding record in the safety inspection form, and whether the version is synchronized | Use a collaborator account to try deleting a file not created by the creator; it should be filtered and a prompt should appear; check the ledger fields and signatures |
| Emergency incident report | Whether the incident name, involved quantity, and occurrence date are consistent with the ledger, and whether the receipt is missing | Use a restricted member account to search for the same issue and check whether unauthorized files are recalled; check the receipt and date |
| File-level permission configuration | Filter item by item by member; viewing requires knowledge base read permission plus file read permission, and deletion is limited to the creator | Check the authentication configuration of the workflow and nodes, and confirm authentication by member identity; use teamId and tmbId to locate member and file ownership |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match between the safety inspection form and the rectification ledger. Cause: The two materials are maintained by different members respectively, and are not written back and compared against the same object.
- Symptom: The rectification ledger has been updated, but the safety inspection form still shows the old version, and the versions are not synchronized. Cause: The materials have different update rhythms, and there is a lack of version verification linked by object.
- Symptom: The emergency incident report lacks a signature or receipt, and review cannot confirm it. Cause: The reporting materials do not mandatorily collect signature and receipt fields, and the absence is discovered only when verification begins.
How to verify the setup
Acceptance of this feature: Use a restricted account to view the list and perform one retrieval, and check whether the visible scope contains only files readable by that member, with unauthorized files not occupying a place and not being recalled.
Business test: Use one real record to find fields inconsistent with the ledger, record discrepancies in name, quantity, date, and signature, and submit them to the reviewer for confirmation and write-back.
- Check file read permissions item by item by member: viewing the list and details requires knowledge base read permission plus file read permission; use
teamIdandtmbIdto locate ownership. - Use a collaborator account to try deleting a file not created by the creator, confirm that it is filtered and a prompt appears; check whether the workflow and nodes authenticate by member identity.