What this category's data looks like
Enterprise new employee onboarding training materials usually include three types: onboarding training plans, course sign-in sheets, and job descriptions. Onboarding training plans are released by the human resources department in batches, recording the course name, class hours, instructor, participation scope, and effective date; course sign-in sheets are collected by mentors or training specialists after each course, containing the trainee's name, position, sign-in date, and personal signature; job descriptions are maintained by the hiring department, containing the job title, responsibility items, qualification requirements, reporting relationships, and version number. The update cadence of the materials is inconsistent: plans are adjusted with batches, sign-in sheets are generated per session, and descriptions are revised with organizational changes. When entering this function, the three types of materials serve as basis sources respectively: the plan provides the course and date baseline, the sign-in sheet provides attendance and signature evidence, and the description provides job responsibilities and reporting relationships. Field characteristics are concentrated in names, quantities, dates, signatures, and version numbers, and must be checked item by item against the original text.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Basis items that can refer back to the original text" are completed by subsequent nodes continuing execution according to the branch. When a node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | Whether the course name, class hours, effective date, and participation scope can be matched verbatim against the original text, and whether the version is current | Check the options and branch connections one by one in the node, run a trial and then view the node status in the run record, and confirm the plan version number and effective date |
| Course sign-in sheet | Whether the trainee's name, position, sign-in date, and signature are complete, and whether the names and quantities in the same record are consistent with the plan | Reference the selection result variable variables in subsequent nodes and run a trial, and check whether the signature column and receipt of the sign-in sheet have missing items |
| Job description | Whether the job title, responsibility items, reporting relationships, and version number are cross-consistent with the plan and sign-in sheet | Check the node status corresponding to nodeId in the run record, and compare the description version number with the current version |
| User selection node | Whether each option corresponds to an independent branch, and whether execution continues downward after the interaction is completed | Trigger an interaction once, view the branch direction and interaction status record, and confirm that the default branch was not taken and the process did not stop |
Three common errors
- Phenomenon: The same trainee's name or position title does not match across two materials. Cause: Sign-in sheets are collected in handwriting, plans are imported in batches, and names were not uniformly checked.
- Phenomenon: The course quantity or class hours do not match across two materials. Cause: After the plan was adjusted, the sign-in sheet was not updated synchronously, and the version was not synchronized, causing item misalignment.
- Phenomenon: The sign-in sheet lacks a signature or receipt and cannot refer back to the original text. Cause: The collection step did not verify the signature column item by item, and the materials did not undergo a completeness check before entering the workflow.
How to verify the setup
This function's acceptance: run trials option by option, check the branch directions and interaction status in the run record, and confirm that each option corresponds to one branch and that execution continues downward after the interaction is completed; reference variables and nodeId in subsequent nodes, and check whether the status record is complete.
Business test: ask a basis question spanning materials, and see whether the answer gives a traceable source, whether the basis comes from the institution’s materials, whether the version is current, and whether the items can be matched against the original text.
- Check the options and branch connections one by one in the node, trigger an interaction once and then view the node status in the run record, and confirm that the default branch was not taken and the process did not stop.
- Reference the selection result variable in subsequent nodes and run a trial once, and compare whether the names, quantities, dates, and signatures of the onboarding training plan, course sign-in sheet, and job description are consistent.