What this category's data looks like
This page addresses the pre-departure training and overseas safety reminder category; materials come from pre-departure training courseware, safety reminder checklists, and accommodation contact sheets. Courseware is updated by batch, safety reminder checklists are adjusted according to destination risk, and accommodation contact sheets are returned by overseas liaisons. Field characteristics center on names, quantities, dates, and signatures: courseware names and checklist names must be consistent, accommodation quantities and contact sheet row counts must be consistent, dates must fall within the same batch, and signatures or receipts must be complete. When materials enter the conversation log and audit function, courseware and checklists serve as reminder content sources, accommodation contact sheets serve as verification objects, and the three together support the progress table and statistical scope description. The update cadence is aggregated weekly or monthly, and a total verification is completed before entering the weekly or monthly report.
Configuration and implementation checks
This step is executed by the conversation record interface (by application and session dimension), outputting the session message list and total record count, including role and reference information. The "progress table and statistical scope description" is then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | The courseware name, quantity, date, and signature must correspond item by item with the safety reminder checklist; the name and date of the same record in the two materials must be consistent | Pull pages by application and session dimension, verify that chatId matches the actual session, and sample one record to inspect role and reference information |
| Safety reminder checklist | The checklist item count, date, and receipt must be synchronized with the courseware batch; if the version is not synchronized, it must not enter the total | Pull two consecutive pages to check the total record count and advance the offset by the number of records retrieved, confirm response code of 200, and check that the record count matches the total |
| Accommodation contact sheet | The contact sheet row count, date, and signature must be consistent with the checklist quantity; rows missing signatures or receipts must be marked separately | Open one record to verify dataId and the reference field, and record the reference count separately by array length |
| Progress table and statistical scope description | The header must state the statistical scope and exceptions, and the record count must match the statistical count | Use one week of records to verify the total, and check whether the scope and exceptions are clearly stated |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the courseware and the checklist. Cause: The two materials are updated separately and are not aggregated by the same batch, resulting in discrepancies during totaling.
- Symptom: The accommodation contact sheet version is not synchronized, and the old version's row count is still included in the statistics. Cause: The returned file is not marked with version and date, and signatures or receipts are not compared during verification.
- Symptom: The interface returns empty but sessions appear in the interface. Cause: Only the first page was retrieved or the application and session identifier sources are inconsistent, and record ownership was not verified according to
value.
How to verify the setup
This function's acceptance: page through all records according to the total record count total, sample one record to verify role, reference information, and time, confirm response code of 200, and record the reference count separately by array length.
Business test: use one week of records to verify the total, and check whether the scope and exceptions are clearly stated.
- Pull two consecutive pages to compare the total and offset, and confirm that the record count matches the total record count.
- Open one record to verify the role, reference, and elapsed time fields, and confirm that message roles correspond to the original conversation.