What this category's data looks like
This category's data looks like this: Enrollment consultation conversion at training institutions involves three types of materials: program brochures, consultation records, and trial class schedules. The sources are course consultants, academic affairs staff, and trial class teachers, and the update cadence rolls with class terms and trial batches. Program brochures contain course names, number of class hours, start dates, fee items, and signature fields; consultation records contain the consultant, intended course, follow-up date, and receipt status; trial class schedules contain trial time, instructor, classroom, sign-in, and confirmation signature. When the three types of materials enter the workflow, the program brochure serves as the baseline source for unified terminology and translated names, the consultation records serve as samples of how terminology is actually written in conversations, and the trial class schedules serve as the cross-checking draft for dates, quantities, and signature fields. The field characteristics are mixed multilingual text, multiple translated names for the same course, and dates and quantities that are prone to misalignment between the two materials.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The unified terminology list and comparison draft are continued and completed by subsequent nodes according to the branches. When a node is triggered, the conversation enters an interaction state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Program brochure | Whether the course name, number of class hours, start date, fee items, and signature fields align item by item with the consultation records, whether the same terminology is written consistently throughout, and whether the translated name can refer back to the original text | Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and reference variables in a subsequent node to do a trial run |
| Consultation records | Whether the consultant, intended course, follow-up date, and receipt status match the dates, quantities, and signatures in the trial class schedules, and whether the versions are synchronized | Reference nodeId in a subsequent node to locate the branch source, and do a trial run to check the name, quantity, and date of that record in the two materials |
| Trial class schedules | Whether the trial time, instructor, classroom, sign-in, and confirmation signature are complete, whether signatures or receipts are missing, and whether the translated names are consistent with the unified terminology list | Check the branch direction and interaction status output by that node in the run records, and sample three terms to check whether their writing is consistent throughout |
Three common errors
- Phenomenon: The name and number of class hours for the same course do not match between the program brochure and the consultation records. Cause: The multilingual materials are translated separately, the terminology list is not unified, and the versions are not synchronized.
- Phenomenon: The dates in the trial class schedules are misaligned with the follow-up dates in the consultation records, and receipts are missing. Cause: The two materials are maintained separately, no cross-check is performed, and the signature fields are left blank.
- Phenomenon: After selecting an option, the default branch is still followed, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the interaction status was not confirmed in the run records.
How to verify the setup
Acceptance for this feature: Run a trial for each option one by one, check the branch direction and interaction status in the run records, and confirm that options and branches correspond one to one and that execution continues downward after the interaction is completed.
Business test: Sample three terms to check whether their writing is consistent throughout, and check whether the translated names can refer back to the original text.
- Check the options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference
variablesandnodeIdin a subsequent node and do a trial run to confirm that the selection result variable has been passed to the subsequent node.