What this category's data looks like
Enterprise compliance and safety training materials include three categories: compliance training courseware, safety operating procedures, and exam records. Courseware comes from regulatory updates and internal policy revisions, and updates are triggered quarterly or by regulatory changes; operating procedures come from equipment and process changes, and are revised in sync with change orders; exam records come from sign-in sheets, answer sheets, and signed receipts after training is delivered. When the three categories of materials enter workflow orchestration, their roles differ: courseware and procedures serve as content to be published, requiring a version ledger and change records for support; exam records serve as evidence materials, requiring one-to-one correspondence with courseware versions and procedure versions. Field characteristics center on name, quantity, date, and signature fields. When the same record appears in two materials, the name, quantity, and date must be consistent, the version number and reference location must be synchronized, and signatures or receipts must not be missing. The update rhythm is triggered by change orders; old versions remain traceable, and the current version is unique.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The "version ledger and change records" are continued and completed by subsequent nodes according to the branches. When the user selection 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 |
|---|---|---|
| Compliance training courseware | Whether the courseware name, version number, publication date, applicable regulatory clauses, and signature fields are complete | Check the options and branch connections one by one in the node, and confirm that the courseware version branch and the reference branch are each independent; trigger once and check the node status in the run record, verifying the status corresponding to nodeId |
| Safety operating procedures | Whether the procedure name, quantity, effective date, revision order number, and signature or receipt are missing | Reference the selection result variables in a subsequent node and run a trial, checking whether the procedure version number and reference location are synchronized; check the date and quantity against the change order |
| Exam records | Whether the record name, number of people, exam date, corresponding courseware version, and signature receipt are complete | Check whether the exam records correspond one-to-one with the courseware version and procedure version; reference variables in a subsequent node and run a trial, checking whether the reference points to the current version |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized; whether the name, quantity, and date of the same record in the two materials are consistent | After changing one piece of content, trigger the user selection node, check the branch direction and interaction state records, and confirm that the version number and reference are updated synchronously; check whether the old version is traceable |
Three common errors
- Symptom: The name, quantity, and date of the same record in the two materials do not match. Cause: Courseware and procedures are maintained separately, the field definitions are not unified on the change order, and the ledger is not written back when referencing.
- Symptom: The version is not synchronized, and the old version is still referenced. Cause: The user selection branch does not cover all reference locations, and subsequent nodes continue execution along the default branch instead of following the branch corresponding to the selection result.
- Symptom: Signatures or receipts are missing, and exam records cannot correspond to the courseware version. Cause: The process stops after the interaction is completed, or the same session repeatedly enters the interaction, and the state record is not written to the corresponding node.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, and check the branch direction and interaction state in the run record; check the options and branch connections one by one in the node, confirming that each option corresponds to one branch; reference the selection result variables in a subsequent node and run a trial, checking the status corresponding to nodeId.
Business testing: change one piece of content and see whether the version number and reference are updated synchronously; check that the current version is unique, old versions are traceable, and references are synchronized, and check whether the exam records correspond one-to-one with the courseware version and procedure version.
- Check the options and branch connections one by one in the user selection node, and after triggering once, check the node status and branch direction in the run record.
- Reference the selection result
variablesin a subsequent node and run a trial, checking whether the version number, reference location, and signature receipt are updated synchronously.