What this category's data looks like
This category's data covers three types of materials: business cooperation agreements, advertising review forms, and distribution cooperation materials. A business cooperation agreement contains the partner name, cooperation term, revenue-sharing ratio, and signature and seal dates; an advertising review form contains the advertiser, issue, page placement, review opinion, and signature; a distribution cooperation material contains the distribution channel, quantity, start and end dates, and receipt. The materials come from the editorial department, advertising department, and distribution department, and are updated by issue or monthly. When entering the HTTP interface and external system functions, each of the three types of materials serves as a source of request body fields: the agreement provides the partner and term, the advertising review form provides the issue and page placement, and the distribution cooperation material provides the channel and quantity. The field characteristics are that the four categories of name, quantity, date, and signature must be aligned item by item with external system records, and the version number and reference relationships must be maintained in sync as content changes.
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 version ledger and change records are completed by subsequent nodes parsing the response, or by the external system handling it as agreed. The request URL, path parameters, request headers, and request body can all use variables placeholders, and authentication information is placed in Authorization as required by the external system.
| Object | Check | Verification action |
|---|---|---|
| Business cooperation agreement | The partner name, cooperation term, revenue-sharing ratio, and signature and seal dates must be consistent with external system records | In the request preview, view the fully rendered URL and request body, and check the agreement fields against the variables sources |
| Advertising review form | The advertiser, issue, page placement, review opinion, and signature must be aligned with the issue records | Use a sample request to compare the returned responseData, and check the issue and page placement fields |
| Distribution cooperation material | The distribution channel, quantity, start and end dates, and receipt must be aligned with the agreement records | Check the request header names and value sources, and confirm that Authorization is passed in as required by the external system |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are in sync | After changing one piece of content, check whether the version number and references are updated in sync, and record the array item count and the tokens of the reference text |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the business cooperation agreement and the distribution cooperation material. Cause: The two materials are maintained separately, without using the current version as the single source of truth.
- Symptom: The content has been changed, but the version number and references are not in sync. Cause: The change only landed in a single material and did not trigger an update of the version ledger.
- Symptom: The advertising review form is missing a signature or receipt. Cause: The review opinion was not filled back in, and the request body field was empty, causing the external system to receive an empty field.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against a sample; confirm that the value sources of variables and Authorization are traceable.
Business test: change one piece of content and see whether the version number and references are updated in sync.
- In the variables panel, check the source of each placeholder and confirm that the
variablesin the request URL, path parameters, request headers, and request body can all be resolved into actual values. - Use a sample request to compare the returned
responseData, check that the fields are consistent with the external interface agreement, and record the array item count and the tokens of the reference text.