What this category's data looks like
The data for this category looks like this Training institution enrollment consultation conversion involves three types of materials: program brochures, consultation records, and trial class schedules. Program brochures come from marketing and academic affairs, are updated by semester or class type, and their fields include course name, class hours, start date, and fee description; consultation records come from the consultation role, are updated daily or weekly, and their fields include consultation date, student name, intended course, follow-up status, and signature; trial class schedules come from academic administration, are updated weekly, and their fields include trial date, student name, course name, instructor, and receipt. When the three types of materials enter the workflow, the program brochure serves as the baseline for definitions, the consultation records serve as the source of progress, and the trial class schedules serve as the evidence for conversion verification, each playing a different role.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "Progress Table and Statistical Definition Description" is continued and completed by subsequent nodes according to the branches.
| Object | Check | Verification action |
|---|---|---|
| Program brochure | Whether the course name, class hours, start date, fee description, and version date are complete, and whether it can serve as the baseline for statistical definitions | Check the fields and version date item by item, and confirm that the course names are consistent with those in the consultation records and trial class schedules |
| Consultation records | Whether the consultation date, student name, intended course, follow-up status, and signature are filled in for each entry, and whether the dates are continuous | Extract records weekly, check the number of records against the statistical count, and inspect for missing signatures and receipts |
| Trial class schedules | Whether the trial date, student name, course name, instructor, and receipt correspond to the consultation records | Compare the name, quantity, and date of the same student in the two materials item by item, and mark inconsistencies |
| Workflow nodes | Whether each option corresponds to one branch, whether the interaction status is recorded, and whether the selection result variable is passed to subsequent nodes | Check the options and branch connections one by one in the node, trigger it once to view the node status in the run record, reference variables in subsequent nodes, and run a trial |
Three common errors
- Symptom: The course name, quantity, and date for the same student do not match between the consultation records and the trial class schedules. Cause: The two materials are maintained separately and are not checked against the same definition.
- Symptom: The program brochure version is not synchronized, and the consultation records still reference the old class hours and old start date. Cause: The update rhythms differ, and the version date is not marked.
- Symptom: The consultation records lack signatures or the trial class schedules lack receipts, making it impossible to confirm the validity of records during statistics. Cause: No signature and receipt verification points are set in the material circulation process.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes; you can use nodeId to locate the node.
Business test: use one week of records to check the totals, see whether the definitions and exceptions are clearly written, whether the number of records matches the statistical count, and whether the definitions are written in the header.
- Check the options and branch connections one by one in the node, trigger it once to view the node status in the run record, and confirm that the interaction status is recorded.
- Reference
variablesin subsequent nodes and run a trial to check whether the selection result variable has been passed to subsequent nodes.