What the documents look like
This category runs on price and membership benefit records. Promotion price tags, membership point rules, checkout daily reports and abnormal refund slips form the daily document set. Data arrives from the POS system, the membership CRM, the payment platform and the price tag system, with updates on a daily or per-shift basis. Short-shelf-life inventory is outside this scope.
For product information and selection questions, these materials play two roles. Price tags and point rules are rule texts used for retrieval and comparison. Daily reports and abnormal refund slips are result records used for human reconciliation. Workflow routing has to connect the two roles to different nodes. A result record does not serve as a rule basis, and a rule text does not serve as proof that an action was carried out.
Constraints at the workflow routing step
The form input node enters an interaction state when triggered, records the workflow state, collects required information, and passes the submitted values to later nodes after the user submits. The user selection node also enters an interaction state, records the workflow state, and executes the corresponding "yes" branch after the user makes a choice. In both cases the dialog box is hidden during interaction.
The constraint follows from what these nodes actually do. They collect values and route branches. They do not constitute price approval, refund authorization or point adjustment execution. Retrieval results carry no permission or entity isolation duty, and a relevance score does not act as a filter for store, member or authorization scope. Order writes, document backfill and external status synchronization require a separate business interface or a later process. The nodes do not perform those actions themselves.
Hypothetical paper exercise: A store checkout supervisor submits a promotion price tag reconciliation record. The source text reads: "At this store, from 1 June 2024 to 7 June 2024, member-price product A is 9.9 yuan per item, and the regular price is 12.9 yuan per item; this price tag takes effect on 1 June." A separate membership point rule source text reads: "Members earn 1 point per 1 yuan spent; points are credited on the day after the purchase." The draft sentence to be assessed is: "Product A was settled at 9.9 yuan on 3 June, and points were credited the same day." The subject is the store and member, the object is product A, the period is 3 June, and the fields are settlement price and point crediting time. The price tag source supports settlement at 9.9 yuan on 3 June, since that date falls inside the stated effective range. The point rule states next-day crediting, while the draft says same-day crediting, which conflicts with the source. This is a paper comparison only; no settlement or point operation was executed.
Configuration and implementation checks
| Configuration item | Relevant setting or check on this page | Correspondence with the sample |
|---|---|---|
| Form input node | Enters interaction state when triggered, collects required information, passes values to later nodes | Collects store, product, date and field name |
| User selection node | Executes the corresponding "yes" branch after the user makes a choice | Selects either price tag check or point rule check |
| Interaction state check | Recorded state is behavior of the interaction node; dialog box is hidden | Confirms no business action occurs during the wait |
| Output handoff check | Passes collected information explicitly to a later retrieval or judgment node | Passes the sample source text and draft sentence into the comparison node |
| External action division | Order writes, document backfill and external synchronization connect to separate interfaces | The sample triggers no settlement or point crediting |
| Retrieval scope check | Verifies identifiers and excludes joint association across vector model libraries | Price tag library and point rule library are checked separately |
Three common errors
- Treating the date and product values collected by the form input node as a confirmed settlement basis. In the sample, "3 June" and "product A" are collected values only; the effective range in the price tag source is the comparison basis, and the two are not interchangeable.
- Treating the "yes" branch of the user selection node as price approval or refund authorization. In the sample, selecting "check point rule" only determines the later comparison path; it does not constitute authorization for a point adjustment.
- Treating a retrieval relevance score as a store or member permission filter. In the sample, retrieval results from the price tag library and the point rule library do not distinguish store authorization; permission judgment requires a separate business interface.
How to verify the setup
- Input the sample price tag source text and the draft sentence, then compare the draft's "settled at 9.9 yuan on 3 June" against the source effective range "1 June to 7 June". The expected observation is that the date falls inside the effective range and the field is supported; if the date falls outside the range, record it as unsupported.
- Input the sample point rule source text and the draft sentence, then compare "credited the same day" against the source wording "credited on the day after the purchase". The expected observation is that the same field carries mutually exclusive values, which is judged a contradiction; if the source does not state a crediting time, record it as pending verification.
- Input a paper empty result [] together with the downstream design, and check whether the downstream has a branch that handles empty input. The expected observation is that the downstream explicitly handles empty input; if no such branch exists, record it as a gap, without claiming that a rule retrieval necessarily returns [].