What this category's data looks like
This category's data looks like this: pre-departure training and overseas safety reminders involve three types of materials: pre-departure training courseware, safety reminder checklists, and accommodation contact sheets. Courseware is updated by training session and contains the course name, teaching date, and signature field; checklists are adjusted by destination risk level and contain reminder items, effective date, and receipt field; contact sheets are synchronized with accommodation confirmation and contain accommodation name, number of rooms, check-in date, and responsible person's signature. When these three types of materials enter multi-turn dialogue and prompt configuration, the courseware and checklist serve as the source of answer constraints, and the contact sheet serves as the object of field verification. The name, quantity, and date of the same record in the courseware and checklist must be consistent, the version and date must be synchronized, and signatures and receipts must not be missing. After materials are drafted according to the template, they enter the handover record and are signed for by the next stage.
Configuration and implementation checks
Configuration and implementation checks: this stage is executed by the memory turns and prompt configuration in the application settings, and outputs the reference range of historical messages and answer constraints. The "issuable material drafts and handover records" are then completed by the model. Memory turns control how many previous turns of dialogue can be referenced at most when answering; if the value is too small, the preceding text cannot be used, and if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | The name, quantity, and date of the same record in the courseware and checklist must be consistent; the version and date are synchronized; the signature field is complete | Check whether the same course name, number of people, and date in the courseware and checklist are consistent, and inspect the version number and signature field; use messages to record the referential continuity of two rounds of follow-up questions |
| Safety reminder checklist | Reminder items and effective date must correspond to the courseware and contact sheet; the receipt field must not be missing | Compare the accommodation name, check-in date, and number of rooms in the checklist and contact sheet; check the signature in the receipt field; use chatId to associate multiple rounds of verification in the same session |
| Accommodation contact sheet | Accommodation name, number of rooms, check-in date, and responsible person's signature must be consistent with the courseware and checklist | Verify the fields of the contact sheet against the courseware and checklist item by item; check the responsible person's signature and date; use variables to mark fields to be supplemented |
| Memory turns | Matches the range of preceding text required by the question; during continuous follow-up questions, the second round can correctly carry forward the reference from the first round | Check the current value in the application settings; run a trial with two consecutive rounds of questions and compare the usage records of the two runs |
Three common errors
- Phenomenon: the same accommodation name is written differently in the contact sheet and checklist, and the number of rooms and check-in date also do not match. Cause: the two materials are updated separately, without field-level comparison and version synchronization.
- Phenomenon: the courseware has been updated to a new version, but the checklist still references the old version's reminder items and effective date. Cause: the version was not synchronized, and there is a lack of a unified version and date verification step.
- Phenomenon: the responsible person's signature or receipt field in the handover record is empty, but the materials are still circulated. Cause: signatures and receipts were not checked before issuance, and missing items were not blocked.
How to verify the setup
How to verify the setup: acceptance for this feature: with two consecutive rounds of follow-up questions, see whether the second question carries forward the reference from the first question. The first question gives the course name and date, and the second question uses a reference to ask about the quantity and signature of the same record, and check whether the answer follows the preceding text; at the same time, verify the recording range of the three identifiers messages, chatId, and variables in the session.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- In the application settings, check the current value of memory turns, run a trial with two consecutive rounds of questions, and confirm that the second round can correctly carry forward the reference from the first round.
- Draft the courseware, checklist, and contact sheet according to the template, compare the name, quantity, and date of the same record item by item, check the version, signature, and receipt, complete one handover, and record the missing-item interception situation.