What this category's data looks like
Enterprise compliance and safety training materials usually include three categories: compliance training courseware, safety operating procedures, and exam records. Courseware is mostly presentation documents updated quarterly, with fields including course name, applicable position, training date, and instructor signature; safety operating procedures are divided into volumes by equipment or process, with fields including procedure number, version number, effective date, approval signature, and receipt number; exam records are archived by batch, with fields including candidate name, exam paper name, score, exam date, and invigilator signature. The three categories play different roles when entering the workflow: courseware and procedures serve as the baseline to be checked against, exam records serve as the objects to be compared, and the ledger serves as the summary reference. In terms of update rhythm, courseware changes with regulatory adjustments, procedures change with equipment changes, and exam records are added by batch; field naming and date formats are often inconsistent, so they must be normalized before comparison.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. When the user selection node is triggered, the conversation enters the interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option. The discrepancy list is completed by subsequent nodes continuing execution along the branch; the node itself does not produce a business deliverable.
| Object | Check | Verification action |
|---|---|---|
| Compliance training courseware | Course name, training date, and instructor signature match the ledger item by item | Check the options and branch connections in the node, reference variables for a trial run, and compare the courseware fields with the ledger fields |
| Safety operating procedures | Procedure number, version number, effective date, approval signature, and receipt number match | Trigger a user selection node once, check the node status in the run record, and confirm that when the version is not synchronized, the discrepancy branch is taken |
| Exam records | Candidate name, exam paper name, score, exam date, and invigilator signature match | Reference the selection result variable in a subsequent node and run a trial once to locate fields whose name, quantity, or date do not match |
| Discrepancy list | The name, quantity, and date of the same object match across the two materials | Write back the discrepancy fields by nodeId, mark missing signatures or receipts separately, and submit to the reviewer for confirmation |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the exam records. Cause: Field naming and date formats were not normalized, and no mapping was done before comparison.
- Symptom: The version of the safety operating procedure is not synchronized, and the old version is still referenced. Cause: The version number and effective date were not included in the verification dimensions, and no review was triggered after the update.
- Symptom: Exam records lack an invigilator signature or receipt, and the discrepancy list omits items. Cause: Signature and receipt fields were not set as mandatory verification items, and the branches did not cover missing cases.
How to verify the setup
This feature's acceptance: run trials for each option one by one, check the branch directions and interaction states in the run records, confirm that each option corresponds to one branch, and that after the interaction is completed the process continues executing downward.
Business test: use one real record to find fields inconsistent with the ledger, record the name, quantity, and date discrepancies, and write them back to the discrepancy list.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run record.
- Reference the selection result variable in a subsequent node and run a trial once, write back the discrepancy fields by
nodeId, and submit to the reviewer for confirmation.