What this category's data looks like
In the off-campus training compliance filing and penalty response scenario, materials are mainly of three types: school operation licenses, course filing materials, and fee disclosure. Sources are approval authority receipts, institution self-retained archives, and disclosure records. The update cadence follows filing batches, change registrations, and penalty rectification milestones. The three types of materials play different roles when entering the workflow: the school operation license provides fields for entity qualifications and permitted scope; course filing materials carry course name, class hours, textbook version, and filing date; fee disclosure carries fee items, standards, refund rules, and disclosure date. Field characteristics center on names, quantities, dates, signatures, and receipts. Multilingual materials and terminology processing require first unifying the terminology glossary, then generating a parallel draft for external release.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Unified terminology glossary and parallel draft" is then completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters an interactive state and the workflow state is recorded. 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 entity name, permitted scope, validity period, and signature receipt are consistent with the course filing materials | In the node, check the options and branch connections one by one, and reference variables and nodeId to record the branch direction |
| Course filing materials | Whether the course name, class hours, textbook version, and filing date match between the two materials | Trigger one user selection and check the node status and selection result in the run record |
| Fee disclosure | Whether the fee items, standards, refund rules, disclosure date, and version are synchronized and no signature is missing | In subsequent nodes, reference the selection result variable and run a trial once, checking that the terminology in the parallel draft refers back to the original text |
| Unified terminology glossary and parallel draft | Whether the same term is written consistently throughout and the translated name can refer back to the original text | Sample three terms to check whether the writing is consistent throughout, and verify the value passed by variables |
Three common errors
- Phenomenon: The same course name is written differently in the filing materials and the fee disclosure. Cause: The terminology glossary was not unified, and the multilingual parallel drafts each continued to use old translated names.
- Phenomenon: The quantity and date of the same record do not match between the two materials. Cause: The versions were not synchronized, and the old version of the materials was not updated with the filing batch.
- Phenomenon: Materials are missing signatures or receipts, and the process stops after the interaction is completed. Cause: The branch does not cover the missing-document case, and the selection result variable is not passed on.
How to verify the setup
Acceptance of this feature: Run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and that the nodeId and variables records are traceable.
Business testing: Sample three terms to check whether the writing is consistent throughout, whether the translated names can refer back to the original text, and whether the parallel draft aligns item by item with the terminology glossary.
- In the node, check the options and branch connections one by one, confirming that selecting a certain option follows the corresponding branch and does not follow the default branch.
- In subsequent nodes, reference the selection result variable and run a trial once, checking repeated entry into the interaction and process stoppage within the same session.