What this category's data looks like
This page addresses off-campus training compliance filing and penalty response scenarios. The material sources are three types: school operation license, course filing materials, and fee disclosure. The school operation license fields include institution name, school address, validity start and end dates, issuing authority, and signature; the course filing materials fields include course name, number of class hours, course start date, instructor, and receipt; the fee disclosure fields include fee items, amount range, disclosure date, and seal. The update cadence advances according to semesters and filing change nodes, and historical versions need to be traced back during penalty response. When materials enter workflow orchestration, the school operation license serves as the entry point for subject qualification, the course filing materials serve as the basis for course visibility scope, and the fee disclosure serves as the source of externally displayed content. The three respectively assume the roles of identity verification, content authorization, and display standards.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Externally available entry points and authorization scope" is completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 operation license | Whether the institution name, address, validity start and end dates, issuing authority, and signature match the filing record item by item | Check the options and branch connections one by one in the node, and compare the name, dates, and signature in the license and the filing record |
| Course filing materials | Whether the course name, number of class hours, course start date, instructor, and receipt are consistent with the disclosure standard | Trigger a check of the node status in the run record, and verify whether the course quantity and dates match in the two materials |
| Fee disclosure | Whether the fee items, amount range, disclosure date, and seal are synchronized with the filing version | Reference the selection result variable in a subsequent node and run a test once, and verify the disclosure date and seal receipt |
| Authorization scope record | Whether the visitor identity matches the visible scope, and whether unauthorized content is invisible | Access once with a restricted identity, and verify the branch direction and visible scope corresponding to variables and nodeId |
Three common errors
- Symptom: The name, quantity, and dates of the same course do not match in the two materials. Cause: The filing materials and the disclosure standard are maintained separately, and no field-level comparison was performed.
- Symptom: The school operation license version is not synchronized, and the old version is still referenced. Cause: The update cadence is not bound to the filing change node, and historical versions are not marked as invalid.
- Symptom: The course filing materials lack a signature or receipt, and the fee disclosure lacks a seal. Cause: The signature and receipt fields were not checked when the materials were archived, and verification is impossible after entering the workflow.
How to verify the setup
Acceptance for this feature: run tests option by option, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and that after the interaction is completed the process continues without repeatedly entering the interaction.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, confirm that unauthorized content is invisible, and verify the reference results of variables and nodeId in subsequent nodes.
- Check the options and branch connections one by one in the node, and confirm that selecting a certain option will not still follow the default branch.
- Reference the selection result variable in a subsequent node and run a test once, and confirm that after the interaction is completed the process does not stop, and the same session does not repeatedly enter the interaction.