What this category's data looks like
Materials for off-campus training compliance filing and penalty response come from three categories: school operating licenses, course filing materials, and fee disclosure. The update cadence rolls with filing changes, course adjustments, and fee disclosure periods. The school operating license carries the entity name, address, validity period, and approval signature; the course filing materials carry the course name, number of class hours, start date, and responsible person's seal; the fee disclosure carries fee items, standards, disclosure date, and receipt. After the three enter the workflow, each becomes an independent comparison object. The name, quantity, date, and signature of the same record must be aligned across materials. Any field change triggers an update to the version ledger and change records, and is synchronized to the knowledge base or external documents.
Configuration and implementation checks
This part is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The "version ledger and change records" are then completed by subsequent nodes continuing execution according to the branch. 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 |
|---|---|---|
| School operating license | Entity name, address, validity period, and approval signature are consistent between the license and the course filing materials | Compare item by item the name, address, date, and signature in the license and the course filing materials, and check the branch direction of the node corresponding to nodeId in the run records |
| Course filing materials | Course name, number of class hours, start date, and responsible person's seal are consistent between the filing materials and the fee disclosure | Compare the course name, quantity, date, and seal in the filing materials and the fee disclosure, and check whether variables pass the selection result to subsequent nodes |
| Fee disclosure | Fee items, standards, disclosure date, and receipt are consistent between the fee disclosure and the school operating license | Compare the fee items, standards, date, and receipt in the fee disclosure and the license, and check the interaction state of variables and nodeId in the run records |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, run through each option, and check the branch direction and interaction state |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the course filing materials. Cause: The two materials are maintained separately, without cross-material field alignment and version comparison.
- Symptom: The fee disclosure has been updated, but the course filing materials still reference the old version. Cause: The version was not synchronized, the change records were not written back, and references were not refreshed with the version number.
- Symptom: The course filing materials lack the responsible person's signature or the fee disclosure lacks the receipt. Cause: Signatures and receipts were not included as required fields in the version ledger, and were not validated during changes.
How to verify the setup
Acceptance for this feature: run through each option, check the branch direction and interaction state in the run records, and confirm that each option corresponds to one branch, that the process continues after interaction is completed, and that the same session does not enter interaction repeatedly.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the node, check the options and branch connections one by one, trigger once, and then view the node status and the
nodeIdcorrespondence in the run records. - Reference the selection result variable
variablesin a subsequent node and run once to confirm that the branch direction and interaction state are recorded correctly.