What this category's data looks like
In the enrollment consultation conversion scenario at training institutions, three types of materials—enrollment brochures, consultation records, and trial class schedules—respectively serve the roles of external commitments, process documentation, and visit confirmation. Enrollment brochure fields include course name, class type, start date, and fee basis; consultation record fields include consultation time, intention level, follow-up person, and receipt signature; trial class schedule fields include trial date, instructor, number of slots, and attendance signature. The three types of materials are updated by class batch, and dates and quantities flow among the brochure, consultation records, and trial schedules. When entering the deployment and upgrade stage, the brochure and consultation records serve as business-side references, and the trial schedule serves as the visit-side reference, used to check whether versions and records are synchronized; they themselves do not participate in mirroring and migration task processing.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), outputting the image version, migration task records, and data row index status. The handover-ready deployment status and operation records are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Primary service and commercial edition image versions | Both images are the same target version; check the version identifier against the version notes | View the version identifiers of both images in the deployment environment, and check whether the MONGODB_URI and PG_URL connection configurations are synchronized with the version |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired | View the task execution record on the administrator version upgrade page, and compare it with the old instance stop time and lease expiration time |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete | Compare the time and status of the two migration records to confirm that the latter was executed after the former was completed |
| Data row index status | After migration, it is a new index status system; sample one data row to check the status field | Sample one data row to check the status field, and check whether REDIS_URL and DB_MAX_LINK are consistent with the post-migration environment |
Three common errors
- Symptom: The service can start, but the data row status is still the old marker. Cause: The two migration scripts were not executed in order; the latter depends on the former being completed, and the old markers were not migrated uniformly.
- Symptom: The name, quantity, and date of the same record do not match between the enrollment brochure and the consultation record. Cause: The versions are not synchronized, and the brochure and consultation record each use fields from different batches.
- Symptom: The trial class schedule lacks an attendance signature or receipt. Cause: The handover form was not checked item by item, and the trial date and number of slots were not aligned between the two materials.
How to verify the setup
Acceptance for this feature: check the two image version identifiers, then check the execution records of the two migration scripts in order, and confirm that the image version identifiers are consistent with the migration task records.
Business test: check once item by item according to the handover form, see which record is missing, and focus on checking the fields, dates, and signatures of the brochure, consultation records, and trial schedule.
- On the administrator version upgrade page, view the execution records of the historical chunk training task migration and the knowledge base rebuild status migration, and compare the time and status.
- Sample one data row to check the index status field, and check whether the two image version identifiers are consistent with the version notes.