What this category's data looks like
This category's data looks like this: Enterprise new employee onboarding training involves three types of materials: onboarding training plans, course sign-in sheets, and job descriptions. Onboarding training plans are issued by the training department by batch, and include course name, class hours, date, and a signature field for the person in charge; course sign-in sheets are collected by on-site organizers by session, and include trainee name, department, sign-in time, and receipt signature; job descriptions are maintained by the hiring department by position, and include position name, responsibility items, appointment date, and approval signature. The three types of materials update at different rhythms: plans update by batch, sign-in sheets update by session, and descriptions update when positions are adjusted. When materials enter workflow orchestration, the plan serves as the main object, while the sign-in sheet and description serve as comparison materials, used to verify whether the name, quantity, date, and signature of the same record are consistent, and to locate discrepant fields.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The "discrepancy list" is completed by subsequent nodes continuing execution according to the branch. When the user selection 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 | The same course name, number of class hours, and training date are consistent between the plan and the sign-in sheet; the signature field for the person in charge has a signature | Compare course name, number of class hours, and training date one by one; check the signature field; check options and branch connections one by one in the node, and use variables to record the selection result |
| Course sign-in sheet | The same trainee name, department, and sign-in time are consistent between the sign-in sheet and the plan; receipt signatures are complete | Compare trainee name, department, and sign-in time by session; check receipt signatures; trigger a user selection node once, view the node status in the run record, and use nodeId to locate the node |
| Job description | The same position name, number of responsibility items, and appointment date are consistent between the description and the plan; approval signatures are complete | Compare position name, number of responsibility items, and appointment date position by position; check approval signatures; reference the selection result variable in subsequent nodes and run a trial once to confirm the branch direction |
Three common errors
- Phenomenon: The course name, number of class hours, and training date of the same record do not match between the plan and the sign-in sheet. Cause: The two materials are maintained by different roles, update at different rhythms, and lack a field-by-field comparison step.
- Phenomenon: The version of the job description is not synchronized, and the number of responsibility items is inconsistent with the position description in the plan. Cause: After the hiring department adjusts the position, it does not write back to the plan, and the workflow does not trigger version verification according to the branch.
- Phenomenon: The sign-in sheet lacks a receipt signature or the plan lacks the signature of the person in charge, and the discrepancy list cannot be closed. Cause: The signature step is not included in the verification action, and after the interaction is completed, the process stops and does not continue downward.
How to verify the setup
How to verify the setup: Functional acceptance: run trials option by option, and check the branch direction and interaction status in the run record; confirm that each option corresponds to one branch, check options and branch connections one by one in the node, and use variables and nodeId to locate the selection result variable and node status.
Business test: Use one real record to find fields inconsistent with the ledger, compare the name, quantity, date, and signature in the onboarding training plan, course sign-in sheet, and job description, record the discrepancy list, and submit it to the reviewer for confirmation and write-back.
- Compare the course name, number of class hours, and training date of the onboarding training plan and course sign-in sheet one by one, mark inconsistent fields, and record the discrepancy list.
- Compare the position name, number of responsibility items, and appointment date of the job description and onboarding training plan position by position, check signatures and receipts, and after triggering the user selection node, check the branch direction.