What this category's data looks like
In the off-campus training compliance filing and penalty response scenario, the materials entering the workflow include three categories: the school operating license, course filing materials, and fee disclosure. The school operating license fields include institution name, school address, validity period, issuance date, and issuing authority seal; the course filing materials fields include course name, number of class hours, instructor, filing date, and filing receipt signature; the fee disclosure fields include fee items, fee standards, refund rules, disclosure date, and responsible person signature. The three categories of materials come from different sources: the license is issued by the approval authority, course filing is submitted by teaching research or academic affairs, and fee disclosure is posted and retained by finance or the campus. In terms of update cadence, the license is reissued upon renewal or change, course filing is updated on a rolling basis by semester or class cohort, and fee disclosure is re-posted when prices or rules are adjusted. When materials enter the workflow, the license serves as the baseline for subject qualification, course filing serves as the basis for content compliance, and fee disclosure serves as the proof of fund compliance; cross-comparison of the three forms the original record support for the exception list and review conclusions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "exception list and review conclusions" are 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 state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| School operating license | Institution name, school address, validity period, issuance date, and issuing authority seal must correspond item by item with the course filing materials and fee disclosure, and dates must not be inverted | Check the options and branch connections one by one in the node, reference variables and nodeId to locate the branch corresponding to this material, and trigger one viewing of the node status in the run records |
| Course filing materials | Course name, number of class hours, instructor, filing date, and filing receipt signature must be consistent with the school operating license and fee disclosure, and the receipt must not be missing | Reference the selection result variable in a subsequent node and run a test once, and check whether the fields and signatures of this material in the branch direction are complete |
| Fee disclosure | Fee items, fee standards, refund rules, disclosure date, and responsible person signature must match the school operating license and course filing materials, and the version must be synchronized | Check the options and branch connections within the node, trigger one viewing of the node status in the run records, and confirm that the disclosure version is consistent with the filing version |
Three common errors
- Symptom: The name, quantity, and date of the same course do not match across two materials. Cause: Course filing materials and fee disclosure are maintained separately, and enter review without cross-comparison.
- Symptom: After the school operating license is renewed, the course filing materials and fee disclosure still use the old version. Cause: The versions are not synchronized, the update cadence is inconsistent, and the old materials have not been replaced.
- Symptom: The course filing receipt or fee disclosure signature is missing, yet the exception record is still advanced for handling. Cause: The review step does not check signatures and receipts, and the original record support is incomplete.
How to verify the setup
This feature's acceptance: run a test for each option one by one, check the branch direction and interaction state in the run records, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and reference variables and nodeId to locate the node.
Business test: create an exception record, see whether it can be traced back to the source material, check that the exception has original record support and a reviewer signature, and hand it to the responsible person for handling.
- Check the options and branch connections one by one in the node, trigger one viewing of the node status in the run records, and confirm that the process continues after the interaction is completed.
- Reference the selection result variable in a subsequent node and run a test once, and check whether the name, quantity, date, and signature receipt of the same record are consistent across the two materials.