What the documents look like
Retail checkout and loyalty materials centre on price and member entitlement, and they do not cover short-shelf-life stock handling. The documents that move through a handover are promotion price tags, member points rules, the checkout daily report, and exception refund slips. These materials come from the POS system, the member CRM, the payment platform, and the price tag system, and the brief gives their update frequency as daily or per shift.
Two features of this category shape the handover task. First, materials sit at different processing stages at the moment of transfer. A refund slip left by the previous shift may still be pending review, and a price tag the next shift sees may still carry the old price. Second, price and entitlement carry effective ranges. A promotion price tag has a start date and an end date, and a points rule has a validity period. The interactive forms step has to pass these staged materials to later nodes without treating a pending review as a completed refund, and without treating a promotion validity period as a supply period.
Constraints at the interactive forms step
The form input node is a user interaction node. When it triggers, the conversation enters an interaction state, the workflow state is recorded, and execution waits until the user completes the interaction. After the user submits the required information, the node collects the submitted form values and passes them to later nodes. The node does not carry a business database function of its own. Field validation, business approval, write-back, and bulk operations need to be implemented in an external system or in later nodes.
The user selection node is also a user interaction node. It triggers the interaction state, records the workflow state, and waits for the user. When the user makes a choice, the node evaluates that choice and executes the branch for yes. It is not a personnel directory and not a business data selector. The documented behaviour covers the interaction wait, the recorded state, and the hidden dialogue box. No control switch, submission count, or automatic judgement is documented for these nodes, so none is asserted here.
Hypothetical paper exercise sample. The source text supplied for comparison reads: "Promotion price tag P-0715, applicable store M-03, effective date 15 July 2025, end date 20 July 2025; member points rule V2, one point per 1 yuan spent, points valid until 31 December 2025; exception refund slip R-0231, status pending review, application date 16 July 2025." The draft sentence to be judged reads: "Refund R-0231 is complete, the points have been reversed, and price tag P-0715 has been executed at the new price." The question is whether that draft sentence is consistent with the source text.
Configuration and implementation checks
| Configuration item | Setting or check for this page | Relation to the sample |
|---|---|---|
| Form input node | Triggers the interaction state and records the workflow state | Collects the handover material fields |
| Required field check | List the subject, object, and status fields this task cannot omit | Check P-0715, V2, and R-0231 |
| User selection node | Executes a branch from the user choice; not a business data selector | Selects the handover type or the downstream path |
| Interaction state wait | Waits for the user to complete the interaction before continuing | Remains waiting before the handover request is submitted |
| Downstream division of work | Field validation, approval, and write-back are implemented in an external system as needed | Refund review status needs separate system confirmation |
Hypothetical starting point for this exercise: set the required fields to "document number, status, date range", because in the source text these three kinds of information determine the handover judgement, and a field-by-field comparison against the source text makes a missing field observable. This starting point is used for this paper check and is not an official default value.
Three common errors
- Treating refund slip R-0231, which is pending review, as a completed refund. The input is the source text status "pending review"; the comparison is the draft sentence "refund is complete"; the observable result is that the draft sentence and the source text status field do not agree.
- Ignoring the end date of 20 July 2025 on price tag P-0715 and still executing the effective price at a handover on 21 July 2025. The input is the source text end date; the comparison is the handover date; the observable result is that the handover date falls outside the effective range.
- Treating the branch result of the user selection node as a passed business approval. The input is the node executing the yes branch; the comparison is the absence of any approval record in the source text; the observable result is that approval evidence is missing and the status remains to be verified.
How to verify the setup
- Input the hypothetical sample source text and the draft sentence, then compare "R-0231 status pending review" with "refund is complete". If the two share the same subject and the same field and their values are mutually exclusive, the draft sentence is judged unsupported.
- Input the end date of 20 July 2025 on price tag P-0715 and the handover date of 21 July 2025, then compare the order of the two dates. If the handover date is later than the end date, the price tag falls outside its effective range.
- Input the record of the user selection node executing the yes branch and the absence of an approval field in the source text, then compare whether approval evidence exists. If the source text does not state an approval status, record the matter as to be verified and do not judge it approved.
These checks compare the same subject, the same period, and the same field. A contradiction requires one field with explicitly mutually exclusive values. A status that is not stated, or evidence that covers only a related stage, is recorded as unsupported or to be verified. A pending review does not by itself show that an operating permission is absent. Retrieval and similarity scoring do not perform permission or entity isolation, and a form collects values rather than granting authorization.