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. Business cooperation agreements record the partner name, cooperation term, revenue-sharing ratio, and signatures and dates of both parties; advertising review forms record the advertiser, issue period, layout position, reviewer signature, and receipt; distribution cooperation materials record the distribution channel, quantity, start and end dates, and signed receipt proof. The three types of materials are registered by business staff in batches, and the update cadence rolls with the cooperation cycle and issue periods. When the materials enter the conversation logs and audit feature, each serves as a source of evidence: agreements and review forms are used to check names and dates, distribution materials are used to check quantities and receipts, and conversation records provide the raw messages and reference information at the session level, so that exception tracing can pinpoint the specific communication step.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), which outputs the session message list and the total record count, including roles and reference information. The "exception list and review conclusion" is then completed by a human or an external system; the message list is not a version ledger of business materials.
| Object | Check | Verification action |
|---|---|---|
| Business cooperation agreement | Partner name, cooperation term, revenue-sharing ratio, signatures, and dates are consistent across the two materials | Compare the agreement and the advertising review form field by field for name, date, and signature; record missing signatures or receipts in the exception list |
| Advertising review form | Advertiser, issue period, layout position, reviewer signature, and receipt are complete | Check the issue period and quantity in the review form against the distribution cooperation materials; mark versions as unsynchronized when dates do not match |
| Distribution cooperation materials | Distribution channel, quantity, start and end dates, and signed receipt proof are traceable | Look up signed receipt proof by channel and batch; when the quantity does not match the agreement, fall back to the original records |
| Conversation record interface | The total record count matches the number of items after paginating through all pages, and roles and reference information are queryable | Paginate by chatId and value, and sample one record to check dataId, role, reference information, and time |
Three common errors
- Symptom: the same partner's name is written differently in the two materials. Cause: naming conventions were not unified at registration, versions were not synchronized, and subsequent comparisons cannot be aligned directly.
- Symptom: the distribution quantity does not match between the agreement and the distribution cooperation materials. Cause: after the quantity was updated by batch, only one side was changed while the other side still kept the old version.
- Symptom: the advertising review form is missing the reviewer signature or receipt. Cause: the review process was archived before it was completed, so there is no signature basis for exception tracing.
How to verify the setup
Feature acceptance: paginate through all pages by the total record count total; when the status code is 200, sample one record to check the role, reference information, and time, and record the reference count separately by array length.
Business test: create one exception record and see whether it can be traced back to the source material, confirming that the name, quantity, date, and signature can be traced back to the agreement, review form, or distribution material.
- Pull two pages in a row and compare the total count and offset to confirm that the number of records matches total, avoiding retrieving only the first page.
- Open one record and check the role, reference, and elapsed-time fields; budget the reference content by tokens and record the array count separately.