What this category's data looks like
Enterprise new employee onboarding training involves three types of materials: onboarding training plans, course sign-in sheets, and job descriptions. The onboarding training plan contains the course name, date, instructor, and participant list; the course sign-in sheet contains name, department, sign-in time, and signature column; the job description contains the job title, responsibilities, qualification requirements, effective date, and approval signature. The materials come from the human resources department and the hiring department, and the update cadence changes with job adjustments, course changes, or batch rollovers. When entering this function, the onboarding training plan provides the course and date fields as request body input, the course sign-in sheet provides the personnel and signature fields for receipt verification, and the job description provides the job and effective date for version comparison. The fields of the three types of materials cross-reference each other, and the version numbers and reference relationships must stay in sync.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "version ledger and change records" are parsed from the response by subsequent nodes, or handled by an external system as agreed to complete the rest. The HTTP node does not replace the external system in writing to the database or approving.
| Object | Check | Verification action |
|---|---|---|
| Onboarding training plan | The course name, date, and participant list are consistent across the three materials, and the version number points to the current version | Check the course name and date in the plan, compare them item by item with the sign-in sheet and job description, and confirm the placeholder sources in the variable panel |
| Course sign-in sheet | The name, department, and sign-in time match, and the signature or receipt is not missing | Use one sample request to compare the returned fields, and check whether the sign-in records and the plan participant list have the same names and the same count |
| Job description | The job title, effective date, and approval signature are complete, and the old version is traceable | View the fully rendered address in the request preview, and check whether the returned version number and references are in sync |
| Request address and path parameters | The placeholder variables can be resolved into actual values | View the fully rendered address in the request preview, and confirm that the variables values come from the output of preceding nodes |
Three common errors
- Symptom: The name and date of the same record do not match between the onboarding training plan and the course sign-in sheet. Cause: The two materials are maintained separately, without cross-checking against the same version number.
- Symptom: The job description has been updated, but the training plan that references it still points to the old version. Cause: The version was not synchronized, and the reference relationship was not refreshed together with the change records.
- Symptom: The sign-in sheet is missing a signature or receipt, and the external system receives empty fields. Cause: The request body fields are inconsistent with the external interface agreement, or the source of the
Authorizationvalue was not checked.
How to verify the setup
This function's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that the version number and reference fields in responseData are in sync, and that the Authorization and variables values are traceable.
Business test: change one piece of content, and see whether the version number and references are updated in sync
- In the variable panel, check the source of each placeholder, and confirm whether it comes from a global variable, system variable, or the output of a preceding node
- Use one sample request to compare the response, check the request header names and value sources, and verify that the request body fields are consistent with the external interface agreement