What this category's data looks like
Enterprise new employee onboarding training involves three types of foundational materials: the onboarding training plan, the course sign-in sheet, and the job description. The training plan comes from the HR department and is updated by batch; its fields include course name, date, instructor, and participant list. The sign-in sheet is generated on site and archived by session; its fields include name, department, sign-in time, and signature. The job description is maintained by the hiring department and iterated by job version; its fields include job title, responsibility items, reporting relationships, and handover confirmation. When the three types of materials enter the workflow, their roles differ: the training plan provides the course and date baseline, the sign-in sheet provides attendance facts, and the job description provides the job and responsibility boundaries. Materials often show mismatches in names, quantities, and dates for the same record across two materials, unsynchronized versions, and missing signatures or receipts. The update cadence is triggered by batch and job version, and the field characteristics require clear responsible parties and consistent versions and dates before entering the drafting and handover stage.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "issuable material drafts and handover records" are completed by subsequent nodes continuing execution according to the branches. When a node is triggered, the conversation enters an interaction state and records the workflow state; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | Course name, date, instructor, and participant list match the sign-in sheet item by item, and the responsible party is clear | Check the options and branch connections one by one in the node, reference variables to record the selection result, and view the node status in the run record |
| Course sign-in sheet | Name, department, sign-in time, and signature match the training plan participant list, and receipts are complete | Trigger one interaction, check the branch direction and sign-in record fields, and when signatures or receipts are missing, subsequent nodes intercept it |
| Job description | Job title, responsibility items, reporting relationships, and handover confirmation match the training plan job, and the version date is synchronized | Reference the variable corresponding to nodeId in a subsequent node and run a trial once, and check whether the version and date are consistent |
| Handover record | The handover parties, scope of responsibility, date, and signature match the job description, and it must not be issued when the version is not synchronized | Draft one according to the template and complete one handover, and check whether missing items are blocked |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the training plan and the sign-in sheet. Cause: The two materials are maintained separately, and the fields are not checked item by item within the node.
- Symptom: The job description version is not synchronized, and the handover record still references the old version of responsibilities. Cause: The version and date are not checked together during branch selection.
- Symptom: The sign-in sheet lacks a signature or receipt, but the material still enters the next step. Cause: The interaction state record does not intercept missing items, and the branch continues execution directly.
How to verify the setup
Acceptance of this feature: run trials option by option, check the branch direction and interaction state in the run record, and confirm that variables and nodeId references take effect in subsequent nodes.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, ensuring that each option corresponds to one branch.
- Trigger one interaction, view the node status in the run record, and confirm that the selection result variable has been passed to subsequent nodes.