What this category's data looks like
The progress records and statistical verification for enterprise new employee onboarding training involve three types of materials: onboarding training plans, course sign-in sheets, and job descriptions. The onboarding training plan provides the course name, start date, and responsible position by batch; the course sign-in sheet records participants, sign-in time, and signature by session; the job description lists the position name, effective date, and confirmation signature by position. The materials come from the training organization and the hiring department, and are updated weekly or by batch, with the signed document or receipt as the authoritative version. The progress table and statistical scope description group the three types of materials under the same batch. The course sign-in sheet provides the actual attendance records, the onboarding training plan provides the expected attendance scope, and the job description provides the correspondence between positions and personnel, each playing the role of expected attendance, actual attendance, and attribution.
Configuration and implementation checks
This part is executed by the connection configuration of the deployment environment (server side), not by the capability of the model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is then completed by the deployment handover and subsequent business processing. The connection address is configured by environment variables. The main business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it will reuse the main database.
| Object | Check | Verification action |
|---|---|---|
| Main business database connection variable | Points to the main business database actually in use and is connectable; material fields and dates are based on the records in the database | In the deployment environment, check that the variable value matches the database address, and check the database pointed to by MONGODB_URI |
| Log database connection variable | Configured separately, or left empty to reuse the main database as described; the database written to by logs can be distinguished from the business database | Check whether the variable is set, check the database written to by logs, and confirm that it is not mixed with business data in the same place |
| Cache connection variable | The cache instance is connectable; it does not carry the fields and signatures of training materials | Connect once with a client, check the response, and check the instance pointed to by REDIS_URL |
| Vector database connection variable | Consistent with the vector database actually in use; when retrieval errors occur, check this first | Check the selected vector database and address against the deployment instructions, and check whether PG_URL is empty or points to the actual vector database |
Three common errors
- Symptom: The name, quantity, and date of the same attendance record do not match between the course sign-in sheet and the onboarding training plan. Cause: The two materials are updated separately and are not checked against the same batch scope.
- Symptom: The version of the job description is not synchronized, and the progress table still references the old position name. Cause: No receipt after the material update, and the statistical scope was not adjusted with the version.
- Symptom: The course sign-in sheet lacks a signature or receipt but is counted as actual attendance during statistics. Cause: The sign-in sheet was summarized before being fully collected, and exceptions were not stated in the header.
How to verify the setup
Acceptance of this function: Connect once to the main business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and check that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the deployment instructions.
Business test: Use one week of records to check the totals, see whether the scope and exceptions are clearly stated, and check whether the number of records matches the statistical count.
- Group the onboarding training plan, course sign-in sheet, and job description under the same batch by batch, and check the fields, dates, and signatures item by item.
- Write the statistical scope in the header of the progress table, indicate expected attendance, actual attendance, and exceptions, and record the material version and receipt status.