What this category's data looks like
The filing materials for enterprise self-directed skilled talent evaluation mainly consist of three types: the enterprise evaluation filing form, the evaluation specifications, and the candidate roster. The filing form records the evaluation entity, occupation and level, time and place, and the signature of the person in charge; the evaluation specifications state the assessment method, scoring and review rules; the roster lists candidate names, ID numbers, declared levels, and batches. These three types of materials are filed before the evaluation, leave a trail during the evaluation, and are archived after the evaluation, with the update cadence advancing along with the batches. When entering the exception tracing and manual review function, the filing form provides the evaluation matters and responsible entity, the evaluation specifications provide the basis for determining exceptions, and the roster provides candidate identity and declaration information. Together, the three support tracing exception records back to the source materials and forming review conclusions for the person in charge to handle.
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 "exception list and review conclusions" are parsed from the response by subsequent nodes, or handled and completed by an external system according to the agreement. The request URL and path parameters, request headers, and request body can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | Fields, dates, and signatures must match the evaluation specifications and roster | Verify the evaluation occupation, level, batch date, and signature in the filing form, and compare them item by item with the evaluation specifications and roster |
| Evaluation specifications | Exception determination clauses and review rules must be traceable to specific records | Verify the assessment method, scoring, and review clauses in the evaluation specifications, and confirm that exception records can cite the corresponding clauses |
| Candidate roster | Names, ID numbers, declared levels, and batches must be consistent with the filing form | Verify the names, quantities, and dates in the roster and filing form, and check whether versions are synchronized and receipts are complete |
| HTTP request | Placeholder variables in path parameters, request headers, and request body can be resolved into actual values | View the fully rendered URL in the request preview, check the Authorization request header and the source of variables, and compare the returned fields in responseData |
Three common errors
- Symptom: the same candidate's name or declared level does not match between the roster and the filing form. Cause: the two materials are entered in different steps, no cross-check is performed, and versions are not synchronized.
- Symptom: after the evaluation specifications are updated, exception determination still cites old clauses. Cause: the specification version is not synchronized, and the review conclusion lacks support from the corresponding clauses.
- Symptom: exception records cannot be traced back to the source materials, and the review conclusion has no signature or receipt. Cause: the filing form lacks a signature, and the external system does not return the processing result as agreed.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against one sample; confirm that all three placeholders Authorization, variables, and responseData can be traced to their sources.
Business test: create one exception record and see whether it can be traced back to the source materials.
- In the variables panel, check the source of each placeholder and confirm that the request header names and value sources meet the external system's requirements.
- Use one sample request to compare the returned fields and check whether the request body fields are consistent with the external interface agreement.