BIG Grooper : A Powerful Document Processing Tool With Some UI Caveats

Search for a command to run...

No comments yet. Be the first to comment.
1.Introdiction to .NET Memory Management When a .NET application runs, memory is primarily divided into two areas: Stack Heap Local variables and method calls are handled by the Stack.Objects crea
python -m venv .venv source .venv/bin/activate pip install -r requirements.txt But now, a new tool called uv makes this entire process seamless. That changes with uv, a new ultra-fast Python package manager and runtime by Astral (creators of Ruff). ...
Introduction In the past month, I’ve been exploring BIS Grooper, a powerful data capture and document processing platform designed to automate information extraction from various file formats. My goal was simple — to understand how businesses streaml...

Build intelligent apps by combining .NET with AI power! 📌 Why Use AI in .NET? With frameworks like ML.NET, Azure Cognitive Services, and OpenAI APIs, .NET developers can easily integrate AI features such as:✅ Text generation✅ Sentiment analysis✅ Ima...
Has Blog
6 posts
From Code to Intelligence – .NET & AI Developer
When it comes to intelligent document processing, it is one of the most capable platforms I’ve used. It’s built to handle large-scale document ingestion, extraction, classification, and validation with impressive accuracy. Whether you’re parsing structured forms, messy handwritten notes, or mixed document sets, BIS delivers exceptional automation potential.
I’ve been working with Grooper for a while now, and I’ve grown to appreciate its strengths:
Robust Document Parsing — Handles multi-page, mixed document types in a single batch.
Powerful Extraction Tools — From regex-based lookups to advanced classification, it supports complex scenarios.
Flexible Workflow — You can automate almost every step from ingestion to export.
While BIS Grooper is excellent for backend document processing, I’ve noticed some limitations when it comes to front-end UI customizations in the Review Panel — especially for enhancing reviewer experience.
Sometimes, I need to show a logo inside the Review Panel regardless of whether that image is part of the scanned document.
For example, if I’m processing invoices for Company A, I might want to always display Company A’s logo in the Review Panel for branding consistency, reviewer context, or visual guidance — even if the uploaded document doesn’t contain the logo.
Currently, BIS has no direct option to insert a custom static or dynamic image into the Review Panel layout. Whether the image is stored in a file path, a database field, or a lookup table, the Review Panel can only display text-based fields.
BIS does offer features like secondary content types that can help conditionally display certain sections, but in practice, this isn’t always a fully complete solution — especially for more advanced scenarios.
In many document workflows, a section should only be visible if BIS finds relevant data from a lookup source (database, XML, API, etc.). If no data is found, the section should be completely hidden from the reviewer.
Example:
While processing an insurance claim, BIS checks an XML lookup for the customer’s policy number.
If a match is found, the “Policy Details” section appears in the Review Panel, pre-filled with the retrieved information.
If no match exists, the section is hidden entirely — keeping the interface clean and focused.
While secondary content types can partially achieve this, they often fall short when the visibility needs to be dynamically driven by lookup results during review. A more robust, real-time solution would give BIS the flexibility needed for complex, data-driven review workflows.
BIS already provides a very useful feature where a dropdown list can be populated from a database or XML lookup. This is excellent for selecting a single value (e.g., choosing a product code, customer ID, or location) from a defined source.
However, in many real-world workflows, it’s not enough to see just one list of values — sometimes we need to show multiple rows of related data returned by the lookup.
Example scenario:
The reviewer enters a customer ID in the Review Panel.
BIS queries the lookup database and finds three past invoices for that customer.
Instead of only showing the customer’s name in a dropdown, the Review Panel should be able to display a table with multiple rows (invoice number, date, amount, status, etc.) for quick context.
Currently, there’s no built-in way to render this kind of multi-row, multi-column data from a lookup source directly in the Review Panel. This limits the ability to give reviewers richer context without switching to an external system.
A feature to show lookup results as a grid or list view inside the Review Panel — rather than just a dropdown — would make BIS even more powerful for complex review workflows.
If we set these UI limitations aside, BIS remains an incredibly powerful platform for document processing. Its extraction accuracy, flexible workflows, and ability to integrate with diverse data sources make it a top choice for large-scale automation. For complex, high-volume environments, BIS consistently delivers speed, reliability, and intelligent handling of even the messiest document sets. In short — the backend power is rock solid, even if the Review Panel could use a few upgrades.