AutoStore: How to Fail a Job using Data Filter Validate

There may be instances when processing a document through AutoStore needs to fail in order to prevent the job from reaching other parts of the intended workflow. Let's consider documents that are captured from a multi-function device which contain barcodes on the pages.

The Barcode component can detect a barcode, and when one is found, it can (1) split the job, or (2) read the value. For either of these actions to be achieved, a barcode would need to be on the page.

Sounds simple enough, but what's tricky is how to know whether any given page should or should not actually have a barcode. In other words, under what condition should we know there is no barcode.

For example, perhaps a given job should have a barcode on every single page, maybe the job should have a certain number of pages with a barcode on it, or possibly a barcode value needs to be present on exactly page n.

Because a logical determination needs to be performed to make that decision, it sounds like this might actually be at the heart of the question. How to fail a job could vary, but let's take at a simple example where the job should have exactly 3 pages with a barcode.

A simple way to establish the job-fail condition would be to use the Data Filter. In it, we'll look at 2 different filters: The Equals To filter and the Validate filter.


For the Equals To filter, we could give it a name of "EqualsTo3", add the Barcode RRT for "Count of pages with barcode" to the "Input" field, and enter "3" in the "Equals To" field.


For the Validate filter, in the "Fail job if" field, we can add the Data Filter RRT we just created named "EqualsTo3", and in the "Message" field, we can enter the message we want to show in the Status Monitor, such as "The job does not have 3 barcode pages, so this job will fail."


When a job is run where the number of pages that have a barcode is not equal to the number we need, the job fails, and the Status Monitor indicates that failure. The AutoStore log is updated, the job is sent to the AutoStore task's Reject folder, and the job is failed.



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