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

Question

Question

Bulk Scanning and Barcodes

Workflow Quick Fields Scanning
Updated January 7
asked on January 6

Our Tax department receives Tax Listing Forms from residents which are scanned in bulk. I've had a process in place that has a Quick Fields session separating the documents by barcode identification and takes the barcode number as an identifier.  A Workflow moves them and exports an image that can be uploaded to a third party Tax software.  This year, the barcode has changed and there are in fact, two versions of the form. On one, the barcode looks the same. On the other, there seem to be dashes separating numbers.  Is Quick Fields still the most efficient and fast way to separate the documents? I've had issues in the past with the barcode identification, depending on the quality of the image.  Plus, I'm more comfortable with Workflow.

Laserfiche 11, on premises. Thanks!

0 0

Answer

SELECTED ANSWER
replied on January 7

If all you're trying to do is remove the dashes, it is easy with a regular expression (as Kevin mentioned).  Something like this would do it:



For the Workflow condition, you can just add a conditional group with the "any" condition and allow the length to be either 22 or 25 digits.

3 0

Replies

replied on January 6

Quick Fields should still work just fine for this and would still be more practical for identifying first/last pages than using a workflow. What I would do is use regex to reformat the barcode output so that it is always in your expected format that you can use as an identifier. You haven't provided any examples, so that's about as much as I can tell you.

2 0
replied on January 6

Also, depending on the extent of differences with the form, you may find it useful to use Conditional processes, or even use two separate document classes.

And yes, Quick Fields is still going to be your best bet for the situation you described.

2 0
replied on January 7

I've attached two examples.  Barcode Sample1 is the original version and is 22 digits. This has been the standard for years. Barcode Sample2 is new and is 25 characters with the dashes.  Would reformatting the barcode be a complicated undertaking?  The Workflow does look for 22 digits as a condition for identifying valid documents.

Barcode Sample1.jpg
Barcode Sample2.jpg
Barcode Sample1.jpg (10.23 KB)
Download
Barcode Sample2.jpg (15.85 KB)
Download
0 0
SELECTED ANSWER
replied on January 7

If all you're trying to do is remove the dashes, it is easy with a regular expression (as Kevin mentioned).  Something like this would do it:



For the Workflow condition, you can just add a conditional group with the "any" condition and allow the length to be either 22 or 25 digits.

3 0
replied on January 7

Exactly. I would add that, if the dashes are always in this position and the data is always numeric, the barcode identification regex would be:

^\d{22}$|^\d{10}\-\d{4}\-\d{4}\-\d{4}$

This allows the barcode value to either be 22 numbers or groups of 10, 4, 4, and 4 numbers separated by dashes. Here's a link that further explains what this is doing: https://regex101.com/r/i0G32b/1. You can modify this to match your exact identifying conditions if this is not accurate.

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

Sign in to reply to this post.

Details
Attachments
Related Posts
Loading ...