I'm using FlexiCapture 12 Distributed for Invoices.
My project has a multi-page FlexiLayout linked to a document definition FORGHIERI_DDT and I want to process a document composed by:
pages 1-4 data pages of layout FORGHIERI_DDT
pages 5 footer of layout FORGHIERI_DDT
pages 6-7 annex
If I don't use a classifier, the system detects the right layout and the Verification Station shows this while the Processing Station log is this where it's clear that the system tests all layouts until it find the right one.
If I use a classifier, the system detect the right layout for the first page but doesn't apply it to the other pages and the Verification Station shows this while the Processing Station log is this where the system classifies all pages right as FORGHIERI layout but it matches only the first one, skipping the others.
At line 15 of Processing Station log the you can read "The page has been classified as a page from another document". What does it mean ? Is this the problem ?
Thanks in advance
Comments
9 comments
I looked for information in ABBYY manuals and web but I didn't find anything.
Does anyone know what mean "The page has been classified as a page from another document" in processing station log and what is caused by?
Thanks to everyone can help me.
I don't understand what's the problem.
If I don't use the classifier, the system detects the right layout and matches all pages.
If I use the classifier, the system detects the right layout for all pages but matches only the first one.
My doubt is that the classifier doesn't work well.
Anyone is using, with success, the classifier (Flexilayout project) with semi-structured and multi-pages document ?
Hello,
Could you please send us the project to reproduce the issue?
Yes, thank you very much, I'll prepare it.
Hello,
Thank you for the provided project.
We cannot reproduce your issue: documents (with classifier and without classifier) are processed identically. But we have a lot of errors related with ToolsLib.dll that need specific path for proper using. Could you please rebuild your project without the dll or send us detailed description how we should customize it?
I'm sorry.
I rebuild the project.
Hi Ekaterina,
I think Your inbox is full.
Hello,
Yes, it was. Sorry. I have cleaned it.
Hello,
Unfortunately, we still cannot operate the project, because there are still missing paths and we get a lot of exceptions when trying to run the project on our side.
Is it possible for you to test the exported project operability by exporting and archiving the project, re-opening it on the different machine and looking if any errors related to the missing paths or components are shown? If they appear, then some refactoring and rewriting will be needed to ensure that the exported project will be able to run on our side and demonstrate the original issue to us.
We apologize that this situation lasts so long, but without the working project we cannot tell anything.
In general, if you are interested in faster resolution of this issue, it better should be addressed to your regional support. Of course, the same preparation work will be needed so that the project can run in the different environment.
Please sign in to leave a comment.