AutoStore: Planning Solid Barcode Workflows


Processing barcodes using AutoStore is something I get asked about frequently, and for what would appear to be a pretty simple image of bars and blocks, there's quite a bit worth talking about from a technical perspective. Notwithstanding, actual workflow requirements are key.

When building any document barcode process, and considering even the simplest of jobs, there are three main categories of what is actually being processed which deserve to be examined:
  • Batch
  • Document
  • Page

Generally speaking, a batch consists of many documents, and a document is made of of one or more pages. Obviously, we can break these items down into even smaller pieces, but these are the basics.

With respect to the actual barcode value in the job, there are the actions which can then be taken:
  • Split
  • Keep
  • Extract

Knowing how barcodes can be handled, the following 3 questions will help take us to creating the most solid AutoStore process process.

What's The Goal?

Barcodes can assist with splitting a batch, the page with the barcode can be kept or discarded, and its value can be obtained as metadata. Digging deeper, the workflow process drives the actions that need to be taken. Now, it comes down to these questions...

What needs to be done with the barcode?
  • Split the document batch?
  • Keep the barcode page?
  • Extract the barcode value?

Split the Document Batch?

Taking multiple documents in a single scan is often referred to as "scanning a batch" or a "batch-scan". When it comes to handling a batch, it is often necessary to take the job into a separate AutoStore task that does nothing more than to split the batch into individual documents.

In this step, its important to keep in mind that the barcode needs to remain with the document in order for the next task to be able to process it independently from the other documents. Commonly, a barcode cover page is usually where each document is the split, so it's often the document's first page.

Keeping The Barocde Page?

In a separate task, the individual documents are now handled as separate documents. Here, the barcode component can handle extracting the barcode value, or determining whether or not to remove the page with the barcode.

Extract the Barcode Value?

To extract the value, the barcode needed to remain on the document when the batch was split. There is an option in the Barcode process component in the Advanced tab which may need to be enabled to Generate RRTs for the barcodes from separator pages.

Keeping the barcode page and extracting the barcode value can usually remain functions within a single AutoStore task, but depending on the workflow, it may be best to split these up into two separate tasks.

In closing

It is good practice to create a plan when constructing any AutoStore process. One of mistakes often made is jumping straight into the AutoStore Process Designer without taking this crucial step. It's like showing up at a construction site with tools, ready to build, but no blueprint.

A great process will accelerate great results. When planning a barcode process in AutoStore, keeping these questions in mind will help provide clarity in how to determine the actual effort needed to achieve the desired result.

Cheers!

Comments

Post a Comment

Popular posts from this blog

VBScript: Ensure Backslash Folder Path

Image
To preface what could be regarded as a very small thing, I am reminded of a common turn of phrase concerning the amount of perspiration that should be afforded to the "stuff" belonging to a particular size-category, and pretty sure there was a book written about that topic. Not to come across as disagreeable, but rather to invite a little balance based on my own general observations over time, an increase in cost with things such as time, money, even relationships, can be avoided when the "small stuff" is given the regard that it deserves. One of these tiny details has to do with string variables that reference folder paths within a script. There are times when it is important that a defined directory for a particular folder should and must always end with a backslash. As an example: folderPath = "C:\Example"   Of course, it really is not very difficult to manually enter that backslash into the path. folderPath = "C:\Example\"
Read more

AutoStore: Create a Custom RRT

Image
Have you ever needed to dynamically create a custom RRT for an AutoStore process? In my previous post AutoCapture Default Date , I described my very first AutoStore script where the value of an  Invoice Date  field in an AutoCapture Vendor Invoices  form was assigned a default value of the day prior from the current date. This Invoice Date  needs to be part of the file name, however its format contains slash (/) characters that cannot be part of the file name. So, we'll use the AutoStore VB/JScript process component to create a new RRT that's more friendly. To do so, we'll look at how to do the following: Bring the existing Invoice Date  value into the script Reformat the Invoice Date  to a Windows-friendly file name Output the reformatted Invoice Date to a new custom RRT After adding the VB/JScript process component in between the capture component and the Send to Folder route component of the configuration file, we open the AutoCapture component to conf
Read more

AutoStore: Workflow Loop Example

Image
Regardless of the programming language, a looping-statement is a common declaration for iterating through collections of things, such as the items of an array, records selected from a database, elements within an XML file, or the files inside a directory. A recent AutoStore challenge was presented where a script was used to fetch data in a process that returned either one or many items. This was the easy part. However, each return record needed to be specific to an individual Route based on one of those items returned. Example Example1@email.com Example1/URL Example2@email.com Example2/URL Example3@email.com Example3/URL Although the captured document being processed would be common for all in the return, the recipient belonging to one of these unique records should not be aware of  nor  receive any of the information that would belong to a different recipient. Because an unknown number of return records would be expected, this presents a challenge due to the fa
Read more