What this category's data looks like
Enterprise new-employee onboarding training involves three types of materials: the onboarding training plan, the course sign-in sheet, and the job description. The onboarding training plan is updated by the training department before each session begins, and its fields include course name, date, instructor, and participating positions; the course sign-in sheet is generated by on-site or online sign-in, and its fields include name, department, sign-in time, and signature; the job description is revised by the hiring department when a position changes, and its fields include position name, responsibilities, reporting relationships, and date. When the three types of materials enter the form input node, their roles differ: the onboarding training plan is used to determine selectable courses and the authorization scope, the course sign-in sheet is used to record actual participation and receipts, and the job description is used to define the content visible for a position. The materials have different version update rhythms: the plan by batch, the sign-in sheet by session, and the job description by position adjustment. Field names and date formats are often inconsistent, so they need to be aligned item by item at collection time.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, and it outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry point and authorization scope are then completed by subsequent nodes or manually. After the node is triggered, the conversation enters the interaction state and the workflow state is recorded. After the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | Whether the course name, date, and participating positions fields are consistent with the plan, and whether the position name in the job description can correspond | Check the field names one by one in the node configuration, confirm that they correspond one-to-one with the plan fields, and check the required markers |
| Course sign-in sheet | Whether name, department, sign-in time, and signature are complete, and whether the date matches the plan batch | Check the required settings one by one, and after a trial submission confirm that subsequent nodes can retrieve the sign-in field values |
| Job description | Whether the position name, responsibilities, and date are consistent with the participating positions in the plan, and whether the version is synchronized | Reference this field in a subsequent node and run a trial, and check that the retrieved field values are consistent with the job description |
| Form input node | Whether it can be submitted when required items are empty, whether subsequent nodes can retrieve the values after submission, and whether the conversation stays in the interaction state | Trigger once with formInput, and check the userSelect selection result and the field passing after submission |
Three common errors
- Symptom: The course name and date for the same record do not match between the onboarding training plan and the course sign-in sheet. Cause: The two materials are updated by different people according to different batches, and the fields are not aligned.
- Symptom: The job description version is not synchronized, and the position name is inconsistent with the participating positions in the plan. Cause: After a position adjustment, the job description was not revised in time, and the form still references the old version.
- Symptom: The course sign-in sheet lacks a signature or receipt, but it still proceeds to subsequent nodes after submission. Cause: The required marker does not cover the signature field, and the interaction node does not intercept empty values.
How to verify the setup
Acceptance of this feature: fill it out once and submit, check the field values retrieved by subsequent nodes, and confirm that formInput triggers the interaction state, and that the userSelect selection result is consistent with the submitted fields.
Business test: access once with a restricted identity, and see whether the visible scope matches the setting and whether unauthorized content is invisible.
- Check the field names and required markers one by one in the node configuration, and confirm that they correspond one-to-one with the fields of the onboarding training plan, course sign-in sheet, and job description.
- Reference the submitted fields in subsequent nodes and run a trial, and check whether it can be submitted when required items are empty and whether the conversation stays in the interaction state.