-
Notifications
You must be signed in to change notification settings - Fork 1
Example Workflow
swayerloren edited this page Apr 13, 2026
·
1 revision
This is the simplest normal user flow.
- Launch the app.
- Drag an estimate PDF into the app or use the file picker.
- Confirm the file appears in the selected-file list.
- Choose an output folder.
- Click
Convert. - Watch the progress and status area.
- Review any warnings in the validation/error panel.
- Open the output folder and inspect the generated files.
For a successful run, the app should produce:
example.esxexample.esx.xmlexample.canonical.json
The success state should also show the generated path inside the UI.
Inspect the preview or *.canonical.json if:
- totals look wrong
- line items seem incomplete
- the PDF is heavily scanned
- a carrier packet mixes estimate pages with instructions or summaries
- the
.esx.xmllooks incomplete and you are not sure whether the issue is parsing or export
The app can accept more than one estimate PDF in the same run.
That is useful for:
- supplements
- revised scopes
- split packets that belong to the same estimate
The merge behavior is real, but it is still heuristic. Review merged output carefully if different PDFs disagree on totals or scope.
Main repository | Deep docs in docs_repo | Issues
docs_repo/ in the main repository is the authoritative deep technical source of truth.