What the documents look like
Retail checkout and loyalty operations revolve around price and member benefit records. The working material comes from POS systems, member CRM platforms, payment platforms and shelf-label systems. The documents handled day to day are promotional shelf labels, member point rules, cashier daily reports and abnormal refund slips. The people involved are store cashier supervisors, CRM operations staff and finance auditors. When these records are mishandled, the consequences show up as price complaints, cash discrepancies and member benefit disputes. These materials are updated daily or per shift, and handover work requires checking the authorization state of each item rather than treating a retrieval result or a completed form as proof that an action has been authorized or carried out.
Constraints at the upgrades step
Upgrades require checking the current version against the target version and the matching upgrade notes, and they do not allow inferring current behavior from old configuration names. AIPROXY_API_ENDPOINT and AIPROXY_API_TOKEN are shared App/Admin variables. From V4.17.0 onward AI Proxy is a required dependency, and a missing endpoint or token causes startup validation to fail. When an upgrade includes a manually triggered script, the operator confirms that old instances have fully stopped and old task leases have expired before running it. Completing a script is not the same as uninterrupted business operation, and recovery capability has to be verified in the operator's own environment. Retrieval and similarity scores do not carry permission or entity isolation duties, and a value collected in a form is not business verification or completed authorization.
Hypothetical paper exercise sample: a store cashier supervisor intends to write in a handover sheet that "the promotional shelf labels for this round are in effect, member points follow the new rules, and all abnormal refund slips have been handled." The source material to compare against reads: "Promotional shelf-label change order number QD-0417, status is pending review, effective date not filled; member point rule revision draft V2, status: draft, approver field blank; three abnormal refund slips with statuses submitted, pending recheck and closed." The sentence under review is the handover wording above. In this sample, pending review is not in effect, draft is not approved, and submitted plus pending recheck are not fully handled.
Configuration and implementation checks
The table below lists only settings or implementation checks that the official documentation describes and that relate to this page's upgrade and handover review. Where a value appears, it is a hypothetical starting point for this exercise with a stated reason, not an official default.
| Configuration item | Hypothetical starting point and reason | Comparison and check method |
|---|---|---|
| AIPROXYAPIENDPOINT | Service root address such as http://aiproxy:3000, without appending /v1 | Compare character by character with the actual AI Proxy listening address in the deployment template |
| AIPROXYAPITOKEN | Administrator token, non-empty | Compare with the AI Proxy server-side configuration and confirm it matches and is non-empty |
| AGENTSANDBOXOPENSANDBOXVOLUMENAME_PREFIX | Carry over the pre-upgrade VM_VOLUME_NAME_PREFIX value | Compare the value before and after upgrade and confirm it is unchanged |
| PROTOKEN with PROURL | When PROURL is configured, PROTOKEN is required and at least 32 characters | Compare with the pro/admin side configuration and confirm consistency |
| SYNC_INDEX | Hypothetical starting point true, used to create missing indexes at startup | Compare with the actual index state in the operator's own environment; when disabled, indexes are maintained manually |
| Upgrade script preconditions | Hypothetical starting point of all old instances stopped and old task leases expired | Compare with the actual cluster instance and lease state before deciding to run |
Three common errors
- Treating pending review as in effect. Input is the source text "Promotional shelf-label change order number QD-0417, status is pending review, effective date not filled"; the comparison object is the draft sentence "the promotional shelf labels for this round are in effect"; the observable result is that the status field and the draft sentence disagree, so the draft sentence is not supported.
- Treating draft as approved. Input is "member point rule revision draft V2, status: draft, approver field blank"; the comparison object is the draft sentence "member points follow the new rules"; the observable result is that the approver field is blank and the status is draft, so the draft sentence is not supported.
- Treating submitted and pending recheck as fully handled. Input is three abnormal refund slips with statuses "submitted, pending recheck, closed"; the comparison object is the draft sentence "all abnormal refund slips have been handled"; the observable result is that non-closed statuses are present, so the draft sentence is not supported.
How to verify the setup
- For the promotional shelf-label draft sentence: input the QD-0417 status and effective date fields from the source text, compare the draft wording "in effect" against those fields, and the sentence is satisfied only when the status is in effect and the effective date is filled and falls within the handover period. The current sample does not satisfy this.
- For the member point draft sentence: input the status and approver field of revision draft V2, compare the draft wording "follow the new rules" against the approval state, and the sentence is satisfied only when the status is approved and the approver field is non-empty. The current sample does not satisfy this.
- For the abnormal refund draft sentence: input the status fields of the three slips, compare the draft wording "all handled" against each slip status, and the sentence is satisfied only when all three are closed. The current sample contains submitted and pending recheck, so it does not satisfy this.
All of the above judgments remain paper comparisons. No deployment, upgrade, approval or refund action has been performed, and missing fields remain unsupported or pending verification.