FlexiLayout: Unable to Match Labeled Field if Field is not present

  • 1.2K Views
  • Last Post 25 March 2019
  • Topic Is Solved
mentezam posted this 10 August 2017

Hi, I'm doing a proof-of-concept with ABBYY and FlexiLayout/Capture, so I'm a very new to these products.  Currently I'm stuck on trying to get FlexiLayout Studio to match/recognize a Labeled Field on an image that has a label (static text) but a blank/empty field.  The other labeled field have a field that has data (e.g. FirstName:  John Doe), but for couple of the label fields, they don't have a field (e.g. Address Line 2:  , so when I create a label field, FlexiLayout fails on the match and shows an 'orange' rectangle for the the labeled field.  

I've tried to set the "Search control" of the labeled field to "optional element" but it doesn't make a difference.

Is this Ok if it fails on the match?  Should I be doing something else for this scenario?

Order By: Standard | Newest | Votes
Ekaterina posted this 11 August 2017

Hello,

Labeled field has as well the same search options as other elements. If it's not so in your project, please send it to us for further investigation.

Orange rectangle means that null-hypothesis was formed (by the way it's available for optional/prohibited elements only, not for required), having the Quality penalty of 0.97. Usually the matching will go further, but if you have too many penalized elements in your hypotheses tree, it may result in non-matching of entire document. To avoid this you may use the 

Optional(1,0);

property in advanced pre-search relations (layout tries to match the element until the 0 quality, but if is isn't found, then no quality penalty is applied).

You may find more information in FLS11 Help file.

 

  • Liked by
  • mentezam
mentezam posted this 15 August 2017

Thank you very much for the info.  That fixed the problem. 

I was wondering, is writing Optional(1,0); in the advanced pre-search the same thing as setting the "Null hypothesis quality" field in the General tab to 1?  

Also, I noticed that nearly all the Samples projects that come with FlexiCapture do NOT use Labeled Fields to capture data.  The samples use one Static Text element for the label and another Character String element for the text/data field.  Should I also be using the same approach, especially considering that most of my fields are optional (might not be present)?  Not sure if using separate fields like the sample project would make matching easier.  Thanks again.

Ekaterina posted this 17 August 2017

Hello,

Yes, it is the same things. See the FlexiLayout language > Advanced pre-search functions > Controlling searches article in the FlexiLayoutStudio Help.

No, you shouldn’t. This is a matter of convenience.

Allan Rayer posted this 07 February 2019

Hello Ekaterina, 

I have created Flexilayout for an invoice, there is something called Policy number which should capture the number. It did capture in flexilayout and it is also captured in the blocked element and i'm satisfied that Policy number is picked up as it was encircled within green rectangle. I save the layout and export the afl file. 

Then I pass the same document as a batch in document definition and created document definition with the exported values including Policy number. Even after updating the .afl file in the DD, the policy number is blank when i test the DD and throws an error, 1 format error(s) required field not filled. My concern is that the field was matching in flexilayout quite good but in Document Definition it's not. 

-Allan Rayer

Attached Files

Allan Rayer posted this 11 February 2019

Hello Ekaterina, 

I have created Flexilayout for an invoice, there is something called Policy number which should capture the number. It did capture in flexilayout and it is also captured in the blocked element and i'm satisfied that Policy number is picked up as it was encircled within green rectangle. I save the layout and export the afl file. 

Then I pass the same document as a batch in document definition and created document definition with the exported values including Policy number. Even after updating the .afl file in the DD, the policy number is blank when i test the DD and throws an error, 1 format error(s) required field not filled. My concern is that the field was matching in flexilayout quite good but in Document Definition it's not. 

-Allan Rayer

Ekaterina posted this 25 March 2019

Hello,

Please try to recognize the image, that was not recognize in the FC, by the FLS program. Is the Policy number captured?      

Close