integration: fiscal device bridge over ErpNet.FP (receipt print, receipt number read-back, Z-report, device-unavailable refusal)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the engine integration points for sale documents, scheduled jobs, and tenant or store configuration; the issue does not name specific files or tests. Then inspect how integrations handle external HTTP services and refusal errors. Done means simulator tests cover receipt printing and number read-back, the scheduled Z-report, and refusal when the device is disconnected.
Written by the indexing model from the issue text.
Description
Ask. A fiscal device bridge as an engine integration: printing a fiscal receipt on a certified cash register / fiscal printer from a sale document, reading the device's receipt number and date back onto the document, daily Z-report, with the device protocols provided by the open-source ErpNet.FP driver (Datecs, Daisy, Eltrade, Tremol; HTTP API) so the platform integrates one HTTP contract, not four serial protocols; configuration per store/tenant through a configuration group; a device-unavailable refusal path.
Why. Retail in Bulgaria (and most of the Balkans) requires a registered fiscal device for every sale; without the bridge a retail application cannot be used in a shop. The BusinessIntents retail solution needs it (catalog issue on fiscal receipts).
Acceptance. A sale prints a receipt on a Datecs device in the ErpNet.FP simulator, the receipt number lands on the document, the Z-report runs as a scheduled job, a disconnected device refuses the sale with a message; tests against the simulator.
- Dominant language
- Java
- Stars
- 278
- Forks
- 97
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 242
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from eclipse-dirigible/dirigible
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
eclipse-dirigible/dirigible#7958 ·
Maintainers usually reply within 1 day
-
intent: a create-from without fromStatus answers 200 on a missing or unknown source id (no 400/404)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
eclipse-dirigible/dirigible#7945 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
eclipse-dirigible/dirigible#7891 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
eclipse-dirigible/dirigible#6538 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
eclipse-dirigible/dirigible#4812 ·
Maintainers usually reply within 1 day
All issues in eclipse-dirigible/dirigible
Similar issues
-
bug/错误
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FCL-Team/FoldCraftLauncher#1951 ·
Maintainers usually reply within 4 days
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
quarkusio/quarkus-agent-mcp#296 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
commons-app/apps-android-commons#7072 ·
Maintainers usually reply within 1 day
-
enhancement web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
jenkinsci/jenkins#27583 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100