What this category's data looks like
Off-campus training compliance filing and penalty response materials come from three categories: school operating licenses, course filing materials, and fee disclosure. The school operating license contains the institution name, address, validity period, and issue date; the course filing materials contain the course name, class hours, textbook version, and filing date; the fee disclosure contains items, standards, refund rules, and disclosure date. The three categories of materials update at different rhythms: licenses follow the license renewal cycle, course filings follow batches, and fee disclosures follow semesters. When entering workflow orchestration, the school operating license serves as the main record anchor, while course filing materials and fee disclosure serve as branch reference sources, each participating in node decisions through fields, dates, and signatures, forming a handover-ready deployment state and operation record.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. The handover-ready deployment state and operation record are completed by subsequent nodes continuing execution according to the branches. When a 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 |
|---|---|---|
| User selection node | Each option corresponds to one branch, and the branch connections correspond one by one to the option names | In the node, check the options and branch connections one by one, and run a test once to see the direction |
| School operating license | Institution name, address, validity period, issue date, and signature are complete; they match the names and dates in the course filing materials and fee disclosure | Compare the two materials field by field, and check whether signatures and receipts are missing |
| Course filing materials | Course name, class hours, textbook version, filing date, and signature are complete; they match the items and quantities in the fee disclosure | Check item by item according to the handover form, and record inconsistent names, quantities, and dates |
| Fee disclosure | Fee items, standards, refund rules, disclosure date, and signature are complete; they are consistent with the school operating license entity | Check the disclosure date and signature, and inspect whether the version is synchronized |
Three common errors
- Phenomenon: The name and date of the same record do not match between the school operating license and the course filing materials. Cause: The two materials are updated separately and the fields are not aligned to the same version.
- Phenomenon: The fee disclosure has been revised, but the workflow still references the old version. Cause: The version is not synchronized, and the node does not record the currently referenced version.
- Phenomenon: The course filing materials are missing a signature or receipt. Cause: The signature item was not checked when the materials entered the node, and the handover form omitted this field.
How to verify the setup
This feature acceptance: run a test for each option one by one, and check the branch direction and interaction state in the run record; reference the selection result variable variables in a subsequent node and run a test once, then check the node state corresponding to nodeId.
Business test: check item by item once according to the handover form to see which record is missing, focusing on checking the names, quantities, dates, and signatures of the school operating license, course filing materials, and fee disclosure.
- In the node, check the options and branch connections one by one, and after running a test, check the branch direction and interaction state in the run record
- Reference the selection result variable
variablesin a subsequent node and run a test once, and check the node state corresponding tonodeIdand the handover form record