Multi-Turn Conversation and Prompts for Vocational Training Subsidy Applications: Handle Questions and Collect Missing Information

Training Subsidies: review conversation for question intake. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page focuses on Q&A acceptance and missing-item follow-up for vocational training subsidy applications, with materials drawn from three categories: training class filing records, attendance records, and completion assessment forms. Class filing records include the institution name, course name, class start date, student roster, and filing receipt; attendance records register student names, attendance dates, and signatures on a daily basis; completion assessment forms state the assessment subjects, scores, assessment dates, and assessor signatures. The three material categories play different roles at acceptance: filing is used to confirm the fact of class opening and the scope of personnel, attendance is used to verify presence and class hours, and assessment forms are used to determine completion results. The update rhythm advances by class session: filing before class starts, attendance during training, and archiving of assessment forms after completion. Field characteristics are concentrated in four categories: names, quantities, dates, and signatures. The same student name, course quantity, class start date, or completion date often appears with different spellings or formats across two materials. When versions are not synchronized, receipts and signatures are missing, and missing items must first be identified before follow-up questions are asked to complete them.

Configuration and implementation checks

This part is executed by the memory turn count and prompt configuration in the application settings, and outputs the historical message range and answer constraints to reference. The acceptance records and the follow-up questions to be completed are then handled by the model, while the external entry point and authorization are handled by the publishing service and file permissions. The memory turn count controls how many previous dialogue turns can be referenced at most when answering. If the value is too small, the preceding text cannot be used; if it is too large, irrelevant content is brought in and consumption increases.

ObjectCheckVerification action
Training class filing recordsCheck whether the fields, dates, and signatures of the institution name, course name, class start date, student roster, and filing receipt are completeCheck the memory turn count value in the application settings, run a trial with two consecutive questions, and observe whether the second turn can carry forward the references from the first turn
Attendance recordsCheck whether student names, attendance dates, signatures, and class hour quantities are consistent with the filing rosterCompare the usage records of two runs to confirm that consumption changes with the turn count adjustment, and check the historical range in messages
Completion assessment formsCheck the assessment subjects, scores, assessment dates, and assessor signatures, and confirm that they do not conflict with the dates in the attendance recordsUse chatId to locate the same session and check whether variables bring in the fields required for missing-item follow-up
Acceptance records and follow-up questions to be completedMissing items are identified and followed up, answers are based on materials, and fields are complete before transfer to the handlerAsk a question missing key information, see whether it first follows up before answering, and record the follow-up questions to be completed

Three common errors

  • Phenomenon: The same student name or course quantity does not match between the filing and attendance materials. Cause: Name spelling and quantity definitions are not unified at entry, and asking follow-up questions before answering can reduce misjudgment.
  • Phenomenon: The class start date or completion date is inconsistent between two materials. Cause: Versions are not synchronized, and an old filing record and a new assessment form coexist, so each item must be checked against the material dates.
  • Phenomenon: The filing receipt or assessor signature is missing, but the answer still gives a conclusion. Cause: Missing items are not identified and followed up, and the process enters the handling stage with incomplete material evidence.

How to verify the setup

This feature acceptance: ask two consecutive follow-up questions and see whether the second question carries forward the references from the first question; combine messages and chatId to check the referenced historical message range, and confirm that the missing-item fields brought in by variables are consistent with the follow-up questions.

Business test: ask a question missing key information, see whether it first follows up before answering, and check whether the acceptance records and follow-up questions to be completed are transferred to the handler.

  • Check the current memory turn count value in the application settings, match it with the preceding text range required by the question, and run a trial with two consecutive questions.
  • Compare the usage records of two runs to confirm that consumption changes with the turn count adjustment, and check that the opening message is not treated as preceding text.