What this category's data looks like
New employee onboarding uses training plans, course attendance sheets and job descriptions. The training organizer maintains course modules, dates and responsible people; attendance sheets record participants, courses, sign-in times and signatures; job descriptions record duties, requirements and approval signatures. Update the set by onboarding batch and job changes. Use the plan as the main answer source, the attendance sheet to verify participation and acknowledgments, and the job description to check role-specific requirements. Access to the documents is configured at the published entry and permission layer.
Configuration and implementation checks
Conversation memory and prompt configuration determine the history and instructions supplied to the model. Publishing and permission settings determine the accessible entry and data scope. Configure and test access there, then inspect the materials actually used in the conversation.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | Course names, dates and responsible people correspond to the sign-in sheet and job description | Check the application setting and inspect historical messages through two consecutive questions |
| Course sign-in sheet | Attendees, courses, sign-in times and signatures correspond to the training batch | Compare the two runs and inspect whether the session identified by chatId includes irrelevant history |
| Job description | Job title, duties, qualifications and approval signatures agree with the training plan | Configure the access scope at the publishing entry and permission layer, then test with a restricted identity; use variables for business fields |
| Memory turns | The retained history matches the context needed by the question | Inspect the current value in the application settings |
Three common errors
- Symptom: the plan and sign-in sheet use different course names or dates. Compare their source versions and reporting definitions.
- Symptom: the job description lacks approval signatures or the sign-in sheet lacks acknowledgment. Complete the missing filing records.
- Symptom: the second question fails to refer to the first question correctly. Inspect the actual historical messages and prompt instructions; compare the inputs and usage of the two runs separately.
How to verify the setup
Ask two consecutive questions and inspect whether the second question refers back to the intended material. Check the messages actually supplied as history and the prompt instructions. Access the published entry with a restricted identity and compare the visible material with its configured access scope.
- Match the configured memory turns to the prior context needed by the question.
- Verify the published entry and its access scope using a restricted identity, separately from the conversation fields.