A screen flow that ends refused shows the refusal with Close only, but keeps the screen's input fields visible and editable under it — on a refused end, show the message alone (hotcrm#2194 R3-D2) #13342

维护者速读

• 事由： 屏幕流程以「拒绝」结束时，弹窗显示拒绝原因和「关闭」，但下面仍留着可编辑的输入框，用户可以改一些不会被提交的字段。
• 要做： 拒绝结束时只显示消息。这是平台渲染，任何应用的拒绝结束都一样。
• 完成标准： 拒绝结束的弹窗里没有输入框。

Filing gate ③ a task the maintainer set: the maintainer's ruling on objectstack-ai/hotcrm#2194, recorded there at 6354968262 (the director seat, posting from the maintainer's account): 「25251 B hotcrm B」, 2026-10-23T01:05:47Z. That is letter B for all three rounds, exactly as the seat recommended, and it adopts R3-D2. Filed by the repo:hotcrm seat 1 (os-elon-musk, session session_014xanhPEmGTMTfVH4UokwJT) under objectstack-ai/hotcrm#2194's After the ruling. ⛔ Not a claim.

Grade: triage's. The seat suggests priority:p3: an adopted suggestion with a measured cost on an existing surface, no wrong data and no contract change.

Reader (who acts): objectui triage routes and grades it. The landing below is the seat's reading of origin/main; paths under src/ are HotCRM's (objectstack-ai/hotcrm).

Governing text

• The ruling above. Per [Decision] Which of the 33 UI and UX suggestions from the 2026-10-20 browser passes to adopt (seat: adopt 23, fold 4 into open cards, defer 6) hotcrm#2194's own governing text, this item is an adopted suggestion through filing gate ②, not a defect card, and a platform or console landing is changed there, never re-implemented in HotCRM: 「平台相关的功能，应该尽量先改平台。」 (maintainer, 2026-10-18, ledger 6245607810).

Why (measured)

• Page / persona: any screen flow whose run ends outcome: 'refused': in HotCRM, Enroll Members' end_refused and refuse_not_open, and Generate Quote's refuse_held.
• Now: the refusal dialog shows the message with Close only, but keeps the screen's input fields visible under it, so the user can edit fields that nothing will submit.
• Evidence: measured on @objectstack/* 18.0.0 (console objectui 616df6598b42, Chromium 1440×900) by the dev on campaign_enrollment: a closed or missing campaign ends the run with nobody enrolled and no message, because the decision check_campaign_open has no default edge (Studio flags it on every open) hotcrm#2121 (report 6308051861, PR fix(campaign): Enroll Members on a campaign that is not open, or gone, ends refused instead of claiming success hotcrm#2226, "a screen-flow refusal dialog keeps the screen's fields visible under the message with Close only"), and by the dev on Web-to-Case collects no way to reach the visitor: neither the form nor crm_case has an email or name, so the agent who gets the case cannot answer the customer hotcrm#2190 (PR fix(case): the public support form asks for the visitor's name and email, so a web case can be answered hotcrm#2225).

Landing

• The console's screen-flow runner (FlowRunner), on a run result whose status is refused.
• Serial: FlowRunner: a FLOW_FAILED envelope is rendered by the record-save rule — the author's errorMessage, then userMessage, then the declared inner refusal, then message (the console half of objectstack#24914 ruling B′) objectstack#25938 (open, blocked) changes how the same runner renders a FLOW_FAILED envelope. Same component; the claim reads it first.

Done when

• A run that ends refused shows its message (and Close) with no screen fields under it.
• A screen that is still waiting for input renders as today; a test for both.

Size: S.

Dedupe

Method: every open objectstack-ai/objectui issue (24) and every issue updated since 2026-10-19 (185, any state), listed through the repo-scoped issues endpoint (paged) at 2026-10-23T01:20Z and matched case-insensitively on their titles. Words: flowrunner, screen flow, refus. 2 open hits: objectstack-ai/objectstack#25938 (the same runner, FLOW_FAILED; serial, above) and #12331 (a list-toolbar script action). Neither is the refused end. New.

Generated by Claude Code