What this category's data looks like
This page focuses on enterprise independent skilled talent evaluation. The materials include the enterprise evaluation filing form, evaluation specifications, and candidate roster. The filing form records the evaluation agency, occupation name, and filing date; the evaluation specifications state the assessment method and scoring basis; the roster lists candidate names, identity information, and declared levels. The fields, dates, and signatures of the three materials must corroborate one another. When the materials enter the authorized access and external services function, the filing form determines the agencies and occupation scope that can be exposed externally, the evaluation specifications determine the assessment standards displayed externally, and the roster determines the candidate entries visible to visitors. The update cadence advances with evaluation batches; when new batches are added or personnel change, versions are refreshed synchronously, and old versions are retained for traceability. Common inconsistencies center on the same record having mismatched names, quantities, or dates across two materials, versions not being synchronized, or missing signatures or receipts.
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 "externally available entry points and authorization scope" are parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes via variables; authentication information is placed in the request headers according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Enterprise evaluation filing form | The agency name, occupation name, and filing date are consistent between the filing form and the evaluation specifications, and signatures and receipts are complete | Compare the agency and occupation fields in the two materials, and check the signature fields and receipt dates |
| Evaluation specifications | The assessment method, scoring basis, and version number correspond between the specifications and the roster; if the version is not synchronized, it is not visible | Check the specification version number against the version referenced in the roster, and check whether the date falls within the filing validity period |
| Candidate roster | Candidate names, quantities, and declared levels are consistent between the roster and the filing form appendix; if signatures are missing, it is not visible | Compare names and quantities item by item, and check whether the roster signatures and receipts are complete |
| Request body | The fields are consistent with the external interface agreement, and the field names returned by responseData match the agreement | Use a sample request to compare the returned fields, and check the source of the Authorization value |
Three common errors
- Symptom: The same candidate's name or quantity does not match between the two materials. Cause: The roster was updated without synchronizing the filing form appendix, so the version is not synchronized.
- Symptom: The request returns 401, and the external system denies access. Cause: The source of the
Authorizationvalue is incorrect, or the authentication information was not placed in the request headers according to the external system's requirements. - Symptom: The external system receives empty fields, and the returned fields do not match the agreement. Cause: The placeholder variables in the request body were not resolved to actual values, or the
responseDatafield names are inconsistent with the agreement.
How to verify the setup
Acceptance for this function: In the request preview, view the complete rendered address, check the status code and returned fields, and then compare the responseData result against a sample.
Business test: Access once with a restricted identity, check whether the visible scope matches the setting, and confirm that unauthorized entries are not visible.
- In the variables panel, check the source of each placeholder and confirm that
variablescan be traced to global variables, system variables, or outputs from preceding nodes. - Check the request header names and value sources, and confirm that
Authorizationis passed in according to the external system's requirements.