What this category's data looks like
Pre-departure training and overseas safety reminders belong to service delivery materials. The sources are the courseware team, the safety team, and the accommodation liaison role, and the update cadence rolls forward by batch and by pre-departure milestone. After entering deployment, operations, and application handover, the pre-departure training courseware, the safety reminder checklist, and the accommodation contact list each take on different roles: the courseware carries the training content and version identifier, the safety reminder checklist carries the items and effective date, and the accommodation contact list carries the contact person, address, and receipt signature. The field characteristics of the three types of materials are concentrated in names, quantities, dates, and signature receipts. During handover, they need to be aligned item by item with the deployment status and migration task records to avoid the same record having mismatched names, quantities, or dates across two materials, or a version not being synchronized, or a missing signature or receipt.
Configuration and implementation checks
This step is performed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image version, migration task records, and data row index status. The deployable status and operation records are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | The courseware version identifier and the effective date of the safety reminder checklist must be consistent, and signature receipts must be complete | Check the courseware version identifier against the version description, and check the safety reminder checklist date and signature receipts |
| Safety reminder checklist | The item names and quantities must be consistent with the corresponding records in the accommodation contact list, with no missing items | Compare the names, quantities, and dates of the safety reminder checklist and the accommodation contact list item by item |
| Accommodation contact list | The contact person, address, and receipt signature must correspond to the pre-departure training courseware batch | Check the signature receipts of the accommodation contact list, and spot-check the data row index status field |
| Images and migration records | The two images are the same target version, and the two migration scripts are executed in sequence | On the administrator version upgrade page, check the image version identifiers and the two migration task records |
Three common errors
- Symptom: the same record has mismatched names, quantities, or dates in the courseware and the safety reminder checklist. Cause: the two materials are updated separately and are not checked item by item against the handover form.
- Symptom: the service can start, but the data row status is still the old marker. Cause: the migration script was not executed or the execution order was reversed, and the index status was not synchronized.
- Symptom: the accommodation contact list is missing a signature or receipt. Cause: receipts were not collected according to the pre-departure milestone during handover, and the signature field was left blank.
How to verify the setup
This feature acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in sequence, and confirm that the data row index status has been updated.
Business test: check once item by item against the handover form to see which record is missing, focusing on comparing the names, quantities, dates, and signatures of the courseware, the safety reminder checklist, and the accommodation contact list.
- On the administrator version upgrade page, view the time and status of the two migration task records, and confirm that the second is triggered only after the first is completed.
- Spot-check one data row for the index status field, and check whether the
MONGODB_URI,PG_URL, andREDIS_URLconnection configurations are consistent with the deployment records.