What this category's data looks like
In the enrollment consultation conversion scenario for training institutions, the external entry points and authorization scope depend on three types of materials: enrollment brochures, consultation records, and trial class schedules. Enrollment brochures contain course names, class types, start dates, fee descriptions, and signature fields; consultation records contain visit dates, key communication points, intention levels, and receipt signatures; trial class schedules contain trial class times, instructors, venues, and confirmation receipts. After the three types of materials enter the workflow, their roles differ: enrollment brochures provide externally visible course and date fields, consultation records provide the basis for determining identity and visibility scope, and trial class schedules provide the time and signature fields required for subsequent nodes to continue execution. The material sources are exports from the enrollment system and summaries of offline registration forms. The update cadence is a unified refresh before each enrollment period, consultation records are appended daily, and trial class schedules are adjusted weekly. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. The same record is prone to mismatches in names, quantities, and dates across two materials, versions not being synchronized, and missing signatures or receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Externally available entry points and authorization scope" are 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 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 externally visible course names, class types, start dates, and signature fields are consistent with the consultation records | Check the options and branch connections one by one in the node, reference variables to view the brochure fields; compare the names, quantities, and dates in the consultation records |
| Consultation record | Whether the visitor's identity matches the visibility scope, and whether unauthorized content is invisible | Trigger a user selection once, and view the node status and branch direction corresponding to nodeId in the run records |
| Trial class schedule | Whether the trial class time, instructor, venue, and receipt signature are complete and the version is synchronized | Reference the selection result variables in a subsequent node and run a trial once, checking the trial class schedule fields and signature receipt |
| Authorization scope | Whether the external entry points and authorization scope are limited to the corresponding identity according to the branch | Access once with a restricted identity, check whether the visibility scope matches the settings, and ensure unauthorized content is invisible |
Three common errors
- Symptom: The course names, quantities, and dates of the same consultation record do not match between the enrollment brochure and the trial class schedule. Cause: The two materials are maintained separately, without field-level comparison and synchronization.
- Symptom: The enrollment brochure version is not synchronized, and the external entry point still displays the old class types and old dates. Cause: The update cadence is not unified, and old versions are not recalled or marked as invalid.
- Symptom: The trial class schedule lacks a signature or receipt, and the consultation record lacks confirmation. Cause: Signature fields are missed when summarizing offline registration forms, and receipts do not enter the workflow together with the materials.
How to verify the setup
Feature acceptance: Run a trial for each option one by one, check the branch direction and interaction status in the run records, confirm that each option corresponds to one branch, and that the selection result variables have been passed to subsequent nodes.
Business test: Access once with a restricted identity, see whether the visibility scope matches the settings, and ensure unauthorized content is invisible.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and view the node status of
nodeIdin the run records. - Reference the selection result
variablesin a subsequent node and run a trial once, checking whether the names, quantities, dates, and signatures of the enrollment brochure, consultation records, and trial class schedule are consistent.