Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

intent: a BPM task form cannot show the document's lines - the approver of an invoice signs a total

Open
#7,907 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
backend

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Java
Stars
278
Forks
97
Avg merge
19h 30m
Merged PRs (30d)
242

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-dirigible/dirigible

All issues in eclipse-dirigible/dirigible

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.