Files
hiveops-guide/backend/src/main/resources/content/transactions/journal-parsing/overview.md
T
johannes cc5765511c content(guide): customer-facing module guides across 13 SPAs (DRAFT, Refs #3)
62 plain-language audience:customer Overview guides, one per primary
user-facing module (analytics/aria/claims/dashboard/devices/incident/msp/
profile/recon/reports/transactions/vault + fleet), authored by a per-module
parallel pass grounded in each component's actual UI, mirroring the fleet.tasks
voice. Existing hand-made guides were skipped, not overwritten. Deployed to
guide.bcos.dev for review; all DRAFT.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-01 10:46:12 -04:00

1.6 KiB

module, title, tab, order, audience
module title tab order audience
transactions.journal-parsing Journal Parsing Rules Overview 10 customer

Controls how HiveIQ reads the journal files your ATMs upload and turns them into transactions. Use this screen when transactions look wrong or incomplete, or when you add ATMs from a new vendor.

📋 Parsing Rules

  1. The Journal Parsing Rules panel shows the active rules — transaction types, field patterns, and system events — grouped into sections like Version, Timestamp Pattern, Transaction Rules, and System Events.
  2. Click Edit Rules to change them, then Save & Apply to put them live (or Cancel to discard).
  3. Click Reload Rules to refresh from the current rule file without editing.

After saving or reloading, the version number updates so you can confirm the change took effect.

🏷️ Journal / Vendor Types

  1. The Journal / Vendor Types panel lists any vendor-specific rule sets you've defined.
  2. Assign a type to an ATM's journal files so those files use that vendor's custom rules.
  3. If no type is assigned, the default rules apply to every ATM.

If no vendor types are listed yet, you can add them in the rules file above.

🔄 Reparse Journals

  1. Use the Reparse Journals panel to re-process already-uploaded journal files with the current rules.
  2. Enter an ATM ID to reparse just that machine, or leave it blank to reparse all ATMs.
  3. Click the reparse button — HiveIQ tells you how many files were queued.

Reparsing deletes the existing transactions for those files and rebuilds them from the original journals. Use it after you change the rules so past data reflects the update.