What this category's data looks like
Enterprise compliance and security training deployment, operations, and application handover materials fall into three categories: compliance training courseware, security operating procedures, and exam records. Courseware includes course name, version number, applicable position, effective date, and preparer signature; procedures include operating steps, risk level, version, and approval signature; exam records include personnel name, exam paper version, score, exam date, and receipt signature. Courseware and procedures are updated quarterly or upon regulatory changes, and exam records are generated one by one per session. When entering the workflow, courseware and procedures serve as the reference basis for branch judgment, and exam records serve as the verification draft for the handover form; the fields, dates, and signatures of the three must be mutually consistent, and neither the version number nor the receipt may be missing.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters the interaction 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 | The courseware name, version number, applicable position, effective date, and preparer signature must be consistent with the handover form; if the name and date of the same courseware do not match across the two materials, it is inconsistent | Check the options and branch connections one by one in the node, and confirm that the branch corresponding to the courseware version is selected; after triggering once, view the node status in the run record |
| Security operating procedures | The procedure version, risk level, and approval signature must be synchronized with the version referenced by the exam records; if the version is not synchronized or the approval signature is missing, it is inconsistent | Reference the selection result variable in a subsequent node and run a trial once, checking whether the procedure version matches the branch direction; check whether the handover form is accompanied by a receipt |
| Exam records | The personnel name, exam paper version, score, exam date, and receipt signature must be consistent with the versions and dates of the courseware and procedures; if the quantity and date do not match or the receipt is missing, it is inconsistent | Check the fields of the exam records against the courseware and procedures item by item according to the handover form; in the run record, check whether variables carries the exam paper version and whether nodeId points to the correct branch |
Three common errors
- Symptom: after selecting an option, the default branch is still taken. Cause: the options and branch connections were not checked one by one, or the selection result variable was not passed to subsequent nodes, causing the branch judgment to fail.
- Symptom: the name, quantity, and date of the same record do not match between the courseware and the exam records. Cause: the versions were not synchronized, the two materials were updated separately, and the fields were not compared item by item during handover.
- Symptom: the process stops after the interaction is completed, or signatures and receipts are missing. Cause: the interaction status record was not generated, subsequent nodes did not continue execution according to the branch, and the handover form lacks the receipt item.
How to verify the setup
Feature acceptance: run a trial for each option one by one, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, and check in subsequent nodes whether the references to variables and nodeId are correct.
Business testing: check item by item once according to the handover form, see which record is missing, and focus on checking whether the versions, dates, and signatures of the courseware, procedures, and exam records are consistent across all three.
- Check the options and branch connections one by one in the node, and after triggering once, view the node status in the run record to confirm that the interaction status is recorded.
- Reference the selection result variable in a subsequent node and run a trial once, checking whether the branch direction and the versions, dates, and signatures in the handover form are complete.