What this category's data looks like
This category's data covers the progress records and statistical verification of enterprise independent skill talent evaluation, and is built around three types of materials: the enterprise evaluation filing form, the evaluation specification, and the candidate roster. The filing form provides the evaluation entity and filing number, the evaluation specification defines the assessment modules and pass criteria, and the roster carries candidate identity and batch information. The materials are collected by batch by the enterprise evaluation management department, the update rhythm is synchronized with the application cycle, and the field characteristics are concentrated in names, quantities, dates, and signature columns. When entering this function, the three types of materials participate in the call in the form of request body fields, path parameters, and request header authentication information respectively: the filing form fields are used to verify the evaluation entity, the evaluation specification fields are used to verify the assessment criteria, and the roster fields are used to verify candidate records. The progress table and statistical criteria description are parsed from the response by subsequent nodes, or an external system handles them by agreement to complete the next step; the materials themselves are not written directly to the database.
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 "progress table and statistical criteria description" are parsed from the response by subsequent nodes, or an external system handles them by agreement to complete the next step. The HTTP module sends a request to the target address; variables can be used as placeholders in all three places: path parameters, request body, and request headers. The variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | The filing number, evaluation entity name, and filing date correspond item by item with the evaluation specification and roster in the request body fields, and the signature column and receipt are complete | Check the variables source in the variable panel, and use the request preview to compare the filing form fields with the request body fields |
| Evaluation specification | The assessment modules, pass criteria, and statistical criteria are traceable in the returned fields, and the version number is synchronized with the current batch | Check the criteria fields in responseData against the evaluation specification text, and check for exceptions where the version is not synchronized |
| Candidate roster | The candidate names, quantities, and batch dates are consistent with the filing form and evaluation specification in the returned fields, and entries missing signatures or receipts are marked separately | Use one sample request to compare the response, and check the source of the Authorization request header value and the roster fields |
Three common errors
- Symptom: the name or quantity of the same candidate does not match between two materials. Cause: the filing form and roster were collected at different times, the fields were not aligned to the same batch criteria, and the returned fields directly reuse old values.
- Symptom: the evaluation specification version is not synchronized, and the returned fields are still counted according to the old modules. Cause: the request body fields reference historical variables and were not replaced when the specification was updated, causing the totals to be inconsistent with the current batch.
- Symptom: entries missing signatures or receipts are mixed into the statistical totals. Cause: the path parameters were not filtered by signature status, the returned fields did not mark exceptions, and subsequent nodes cannot exclude them during parsing.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that the record count and statistical count in responseData match.
Business test: use one week of records to verify the totals, see whether the criteria and exceptions are clearly stated, and check the value sources of variables and Authorization.
- In the request preview, view the complete rendered address and check that the path parameter placeholder variables can be resolved into actual values.
- Check the request header names and value sources, and use one sample request to compare the returned fields with the external interface agreement.