What this category's data looks like
Vocational training subsidy application materials include training class filing, attendance records, and completion assessment forms; the fields, dates, and signatures of the three must be aligned item by item. Class filing contains the institution name, class number, start and end dates, and approval signature; attendance records contain the trainee name, date, and personal signature; completion assessment forms contain the assessment subject, score, assessment date, and assessor signature. The materials come from training institution declarations and process traces, and are updated in batches as class progress advances. For the same record, the name, number of people, and dates in the filing, attendance records, and assessment forms are often inconsistent, versions are not synchronized, or receipts are missing. When entering the authorized access and external services function, the class filing determines the visible scope and external entry point, while attendance records and completion assessment forms serve as the detail materials accessed under authorization, for subsequent nodes to parse the response or for external systems to process as agreed.
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 point and authorization scope are completed by subsequent nodes parsing the response, or by external systems processing as agreed.
| Object | Check | Verification action |
|---|---|---|
| Training class filing | Institution name, class number, start and end dates, and approval signature are consistent across the filing, attendance records, and assessment forms | In the request preview, view the complete rendered address, and verify the request header names and value sources |
| Attendance records | Trainee name, date, and personal signature match between attendance records and assessment forms | Use one sample request to compare the return, and verify the request body fields against the external interface agreement |
| Completion assessment form | Assessment subject, score, assessment date, and assessor signature are consistent across the assessment and filing | In the variables panel, verify the source of each placeholder, and trace global variables, system variables, or upstream node outputs |
| Request address and path parameters | Placeholder variables can resolve to actual values | Verify the value sources of variables and responseData, and confirm that Authorization is passed in according to the external system's requirements |
Three common errors
- Symptom: The same trainee's name or number of people does not match between the attendance records and the completion assessment form. Cause: The two materials are entered in different steps, no cross-check is performed, and versions are not synchronized.
- Symptom: The start and end dates of the class filing are inconsistent with the dates in the attendance records, causing misalignment in the external service display. Cause: After the filing is updated, it is not written back to the attendance records, and receipt confirmation is missing.
- Symptom: The request returns 401 or the external system receives empty fields. Cause: Authentication information is not passed in according to the external system's requirements, and placeholder variables are not resolved to actual values.
How to verify the setup
This function's acceptance: preview the rendered request, verify the status code and returned fields, then compare the result against one sample, and confirm that the value sources of Authorization, variables, and responseData are traceable.
Business test: access once with a restricted identity and see whether the visible scope matches the setting.
- In the variables panel, verify the source of each placeholder, and confirm that global variables, system variables, or upstream node outputs can resolve to actual values.
- Use one sample request to compare the return, verify that the request body fields are consistent with the external interface agreement, and check the request header names and value sources.