What this category's data looks like
Enrollment consultation conversion materials for training institutions come from three types of source materials: enrollment brochures, consultation records, and trial class schedules. The update cadence rolls forward according to enrollment batches and trial class scheduling. Enrollment brochures carry the course name, number of class hours, start date, and school signature; consultation records carry the consultation time, intended course, follow-up owner, and receipt; trial class schedules carry the trial date, instructor, classroom, and confirmation signature. When these three types of materials enter workflow orchestration, each plays a different role: the enrollment brochure serves as the baseline for external messaging, consultation records serve as the source of handover facts, and trial class schedules serve as the basis for sign-off in the next step. Field characteristics are concentrated in six categories: name, quantity, date, version, signature, and receipt. If any field does not match between two materials, the issuable material draft and handover record will fail the determination of complete fields, clear responsible person, and consistent version and date, and will therefore be stuck before being handed to the next step for sign-off.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch direction and interaction status records. The "issuable material draft and handover record" is completed by subsequent nodes continuing execution according to the branch. When the 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 |
|---|---|---|
| Enrollment brochure | Whether the course name, number of class hours, start date, and school signature are consistent with the consultation records, and whether the version and date are synchronized | Check the options and branch connections one by one in the node, and confirm that the brochure fields enter the branch direction record |
| Consultation record | Whether the consultation time, intended course, follow-up owner, and receipt are complete, and whether the name, quantity, and date of the same record match between the two materials | Trigger once, view the node status in the run record, and check whether the consultation record fields are correctly referenced by the branch |
| Trial class schedule | Whether the trial date, instructor, classroom, and confirmation signature are missing, and whether the receipt flows together with the handover record | Reference the selection result variable in the subsequent node and run a trial once, and check whether the trial class schedule fields are blocked for missing items |
| Handover record | Whether the version and date are consistent, whether the responsible person is clear, and whether the signature or receipt is synchronized with the material draft | Draft one according to the template and complete one handover, and check the values of variables and nodeId in the run record and the branch direction |
Three common errors
- Symptom: The course name, number of class hours, and start date of the same record do not match between the enrollment brochure and the consultation record. Cause: The two materials maintain fields separately, and same-source verification is not performed in the branch direction record.
- Symptom: The trial class schedule has been updated, but the handover record still references the old version, and the version and date are inconsistent. Cause: The version is not synchronized, and subsequent nodes continue execution along the default branch.
- Symptom: The handover record lacks a signature or receipt but is still passed on as an issuable material draft. Cause: The complete-field determination does not block missing items, and the responsible person is not clarified in the branch.
How to verify the setup
Acceptance for this feature: Run trials option by option, check the branch direction and interaction status in the run record, confirm that each option corresponds to one branch, that the selection result variable has been passed to subsequent nodes, and check the values of variables and nodeId in the record.
Business test: Draft one according to the template and complete one handover, see whether missing items are blocked, and only hand it to the next step for sign-off after the fields are complete, the responsible person is clear, and the version and date are consistent.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and avoid still taking the default branch after selecting an option.
- Trigger the user selection node once, view the node status and interaction status in the run record, and confirm that the process continues downward after the interaction is completed.