intent: a BPM task form cannot show the document's lines - the approver of an invoice signs a total
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reading the FormIntent definition and its rendering path, then compare them with the document page's items panel, which the issue names as the rendering reference. Add support for a read-only composition-child items table using the requested fields; done means invoice task forms show their lines under the header fields without row actions.
由索引模型根据 Issue 内容生成。
描述
What happens
forms: (FormIntent: name, forEntity, description, fields, editable, actions) lists header fields of forEntity and one-hop cross-model fields (Customer.email, #7093). There is no way to show the composition children of the document on a task form. The Approve / Issue / Confirm tasks of a sales invoice therefore show number, customer and total only: the approver approves an amount without seeing what is billed (BusinessIntents base-sales-invoices#27, end-user pass on sta; still true on v14.88.0 and v14.90.0 - FormIntent is unchanged).
Ask
A read-only items table on a task form, e.g.
forms:
- { name: ApproveSalesInvoice, forEntity: SalesInvoice, fields: [number, date, Customer, total, Status],
items: { entity: SalesInvoiceItem, fields: [name, quantity, price, vatRate, total] }, actions: [approve, reject] }
rendered under the header fields with the same column rendering as the document page's items panel (read-only, no row actions). items.entity must be a composition child of forEntity; the fields are that child's own (a one-hop like Product.name would be a bonus).
Filed from BusinessIntents base-sales-invoices#27 item 5 (pre-train wave 2026-10-17). Item 4 of the same issue (the credit-hold form shows the limit and the exposure) is done in the module with a one-hop Customer.creditLimit and a stored exposure column, so this ask is only about the lines.
- 主要语言
- Java
- 星标
- 278
- 派生
- 97
- 平均合并
- 16 小时 46 分钟
- 30 天内合并 PR
- 265
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
eclipse-dirigible/dirigible 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 80/100
eclipse-dirigible/dirigible#7958 ·
维护者通常 1 天内回复
-
intent: a create-from without fromStatus answers 200 on a missing or unknown source id (no 400/404)未关闭
难度 2/5 1-3 小时 新手友好度 78/100
eclipse-dirigible/dirigible#7945 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
eclipse-dirigible/dirigible#7891 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
eclipse-dirigible/dirigible#6538 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
eclipse-dirigible/dirigible#4812 ·
维护者通常 1 天内回复
查看 eclipse-dirigible/dirigible 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
AllTheMods/AllTheModium#238 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
apache/stormcrawler#2264 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
commons-app/apps-android-commons#7115 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
objectionary/lints#1596 ·
维护者通常 2 天内回复