You are viewing limited content. For full access, please sign in.

Question

Question

quick fields assign token value process not assigning token

asked on December 8, 2014

I have a zone OCR reading a set portion of the page and then pattern matching on information in that area to assign token values. OCR is reading the information correctly and when I test each pattern matching it shows the correct value I want. Yet when I run the session it is like the pattern matching can't read the OCR area.

0 0

Replies

replied on December 8, 2014

Dumb question, but have you double checked what your pattern match is pointing to? I've caught myself pointing at the wrong thing and tearing my hair out until a third party pointed out my pattern match is set to the wrong stuff. 

 

One thing that gets me is that if my zone OCR is set to page 2, my pattern match needs to be set to page 2 as well

0 0
replied on December 8, 2014

Yes it is pointing to the same page.

0 0
replied on December 8, 2014

Have you made sure it's matching part of the area? I'm taling testing using a single letter or number. 

 

I've seen some wonkiness with pattern matching if it goes over a line break. I've been able to pattern match successfully over a line break when testing by cutting and pasting it into the test area and having it NOT work when it runs. To get around this I sometimes export the whole zone to a field and having workflow deal with it. You just end up needing very large fields, and if you are running it in agent you need to put a limiter on the field to make sure it doesn't go too long to fit. I usually use the pattern (?s).{0,499} to trim it (if needed) to a field with a limit of 500. The (?s) changes the . to match either \n or \r as well. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.