What this category's data looks like
This page centers on student awards, grants, loans, and hardship determination materials, covering three core material types: the family economic hardship determination form, the scholarship/grant application form, and the loan receipt. These materials are typically submitted by students, preliminarily reviewed by counselors, and re-reviewed by the department/school, and are updated by academic year or batch. Field characteristics center on name, student ID, household size, income, hardship level, application amount, loan contract number, signature, and date. When entering the conversation logs and auditing feature, the three material types each play different roles: the determination form is used to substantiate the hardship level, the application form is used to verify the award/grant program and amount, and the loan receipt is used to confirm disbursement and receipt. During circulation, materials often show the same record with mismatched names, quantities, and dates across two materials, unsynchronized versions, and missing signatures or receipts. The conversation record interface pulls by application and session dimensions, returning a message list and total record count, providing session evidence for handover, but it does not replace the business ledger.
Configuration and implementation checks
This step is executed by the conversation record interface (by application and session dimensions), outputting a session message list and total record count, including role and reference information. The handover-ready deployment status and operation records are then completed by manual or external systems. The interface only retrieves session evidence and does not write to the business ledger.
| Object | Check | Verification action |
|---|---|---|
| Application and session identifiers | Consistent with the actual application and actual session | Check the source of chatId and dataId in the request parameters, and confirm they correspond to the interface session |
| Pagination parameters | Record count matches the total | Pull two pages consecutively and compare total with the offset, confirming response code of 200 and that the list length matches total |
| Role field | message roles correspond to the original conversation | Look at the order of the two role types in the returned list, and sample one record to check the role and reference in the value field |
| Family economic hardship determination form | Fields, dates, and signature are complete | Check name, student ID, hardship level, and signature date, and compare with the application form for consistency in names, quantities, and dates |
Three common errors
- Symptom: The same record has mismatched names, quantities, and dates between the determination form and the application form. Cause: The two forms are filled out separately, no cross-check is done, and versions are not synchronized.
- Symptom: The loan receipt is missing or unsigned, making the disbursement status impossible to confirm. Cause: The receipt was not archived with the batch, and items were missed during handover.
- Symptom: The interface returns empty but there is a session in the interface. Cause: The sources of the application and session identifiers are inconsistent, or the pagination offset does not start from zero.
How to verify the setup
Feature acceptance: Page through by total record count to retrieve everything, sample one record to check the role, reference information, and time, confirm that _id, dataId and value are queryable, and that the status code is 200 and total matches the list length.
Business testing: Check item by item once according to the handover sheet, see which record item is missing, and focus on checking the fields, dates, and signatures of the determination form, application form, and loan receipt.
- Pull pages by application and session dimensions, record total and offset, and pull two pages consecutively to compare the total with the list length.
- Sample one record and open
value, check the role, reference information, and elapsed-time fields, and confirm that the reference count and reference content budget are recorded separately.