What this category's data looks like
This page focuses on three types of materials in enterprise compliance and safety training: compliance training courseware, safety operating procedures, and exam records. Courseware comes from policy clauses and position risk lists, and is revised according to the pace of regulatory updates and accident reviews; procedures come from equipment instructions and work permits, and are synchronized with process changes; exam records come from training sign-ins and answer sheets, and are archived by batch. Field characteristics include material name, version number, effective date, responsible person's signature, and receipt status. When entering the workflow, courseware and procedures serve as the drafting basis, and exam records serve as handover evidence. Together, the three support issuable material drafts and handover records. Only after the fields are complete, the responsible person is clear, and the version and date are consistent can they flow onward.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Issuable material drafts and handover records" are then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Whether the name, version number, effective date, and responsible person's signature are consistent with the policy list | In the node, check the options and branch connections one by one, and reference variables to see whether the selection result variable is passed to subsequent nodes |
| Safety operating procedures | Whether the name, quantity, and date of the same record match across the two materials | Trigger an interaction once, check the node status in the run record, and verify the branch direction corresponding to nodeId |
| Exam records | Whether missing signatures or receipts and unsynchronized versions are blocked | Reference the selection result variable in a subsequent node and run a trial once, checking missing-item prompts and branch direction |
| Handover records | Whether the responsible person is clear, the version and date are consistent, and the receipt fields are complete | Draft one according to the template and complete one handover, then check the branch and interaction status in the run record |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the exam records. Cause: Drafting and handover reference different version sources, and the fields are not checked uniformly.
- Symptom: The version is not synchronized; the procedure has been updated while the courseware still uses the old version. Cause: The update pace is not synchronized, and the node does not prompt version differences according to the branch.
- Symptom: Signatures or receipts are missing, but the material still enters the next stage. Cause: The handover record fields are not fully validated, and the branch direction does not block missing items.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction status in the run record, and confirm that variables, nodeId, and option branches correspond.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the node, check the options and branch connections one by one, trigger an interaction once, and view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, checking the branch direction and interaction status record.