What this category's data looks like
Progress records and statistical verification for social evaluation of vocational skill level certification revolve around three types of materials: the evaluation implementation plan, the candidate registration form, and the assessor dispatch form. The evaluation implementation plan provides the certification batch, occupational direction, and time schedule, and is the skeleton of the progress table; the candidate registration form provides the number of registrations, qualification review, and payment status, and is the source of the statistical figures; the assessor dispatch form records the dispatch date, assessor list, and signed receipt, and is the basis for exceptions and caliber explanations. Materials are updated by batch and archived successively within a weekly rhythm, and fields contain four types of characteristics: name, quantity, date, and signature. When the three types of materials enter this function, they respectively assume the roles of plan baseline, headcount ledger, and dispatch credential; the progress table and statistical caliber explanation must state in the header the source of each field and the exception handling method, and then enter the weekly or monthly report.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "progress table and statistical caliber explanation" is parsed from the response by subsequent nodes, or an external system handles it as agreed to complete the rest. The HTTP module sends a request to the target address; path parameters, request body, and request headers can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | Whether the fields, dates, and signatures match those in the candidate registration form and the assessor dispatch form | Check the batch name, occupational direction, and dates in the plan, compare them item by item with the registration form and dispatch form, and use variables to record the placeholder sources |
| Candidate registration form | Whether the name, quantity, and date of the same record are consistent across the plan and the dispatch form | Use one sample request to compare the response, check the number of registrations and qualification status, and inspect whether the fields in responseData are consistent with the header caliber |
| Assessor dispatch form | Whether the dispatch date, assessor list, and signed receipt are complete | Check the signatures and receipts of the dispatch form, confirm that the request header Authorization is passed in according to the external system's requirements, and list items missing signatures in the exception explanation |
| Request address and path parameters | Whether the placeholder variables can be resolved into actual values | View the rendered full address in the request preview, and confirm that the path parameters correspond to the plan batch |
Three common errors
- Symptom: the name and date of the same candidate do not match across the two materials. Cause: the registration form and the dispatch form are entered separately, and the versions are not synchronized, resulting in a discrepancy between the progress table and the statistical figures.
- Symptom: the assessor dispatch form is missing signatures or receipts. Cause: the dispatch process was archived before it was completed, unconfirmed records were included in the total during statistics, and the exceptions were not written into the caliber explanation.
- Symptom: the request returns 401 or the external system receives empty fields. Cause: the request header authentication information and request body fields were not passed in as agreed, and the variable placeholders were not resolved into actual values.
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, and confirm that the values of variables, Authorization, and responseData are traceable.
Business test: use one week of records to check the totals, see whether the caliber and exceptions are clearly stated, and confirm that the number of records matches the statistical figures.
- In the variable panel, check the source of each placeholder, and confirm that the variables in the three places—path parameters, request headers, and request body—can all be traced to global variables, system variables, or the output of preceding nodes.
- Use one sample request to compare the response, check that the fields received by the external system are consistent with the agreement, and list items with inconsistent names, quantities, dates, and signatures in the exception explanation.